I was talking to one of our clients and they need support for deployment in their campus. He specifically outlined a scenario and was asking if Kaspersky is capable of implementing this. I need your feedbacks and instructions on how to do this implementation.
The scenario goes something like this:
"A user arrives at work and starts his new workstation up. He then either logs into the domain that the campus has or just logs in locally, but either method should be considered acceptable for deployment procedures. Let us assume that the workstation has already been given an IP address (e.g. 192.168.1.10) and domain group by the technical group.
He then calls up the Technical group and requests that his workstation be installed with Kaspersky Anti Virus. After the call, a Tech Support staff arrives at his workstation. The staff accesses the run command and inputs a syntax command to initiate the Kaspersky Network Agent silent installation from the Administration Server. The Server then proceeds to install the network agent to the workstation, and the staff then leaves the workstation as his job there is over.
After installing the network agent to the workstation, the Administration Server then recognizes the connection to the workstation and automatically adds the workstation to a group created by the administrator, depending on his own set of policies that he created prior to the deployment. In this case, he created a group in which all workstations with IP addresses from 192.168.1.1 to 192.168.1.50 to be automatically included to this group. So, after the
server recognizes the connection to the workstation with the IP 192.168.1.10, it includes that workstation to the preferred group as per the administrator's policy.
After the workstation has been added to the group, a group task automatically runs to silently install the anti-virus software with a set of pre-defined policies and settings created by the administrator to the workstation. After the installation, a prompt will be displayed in the user's workstation informing him that the installation of the software has been successful and that the workstation needs to do a restart. At this point, the installation is finished and the same procedure is repeated to a new workstation."
As you may have observed, they are implementing a "PULL" deployment instead of the "PUSH" deployment. They want this method to be automated and with minimal human interaction.
In addition to this inquiry, I have noticed also that when I usually deploy the Admin Kit, the workstations does not usually provide their IP addresses in the IP Address column. Can this be resolved?
Thanks for looking into this and I hope you maybe able to provide your info's and solutions as to how can I tackle this scenario.
Thanks and more power!
