I am attempting to deploy Kasperky Network Agents and Workstation to multiple domains and manage them from one Admin Kit (no slave kits).
My plan is to copy the Network Agent and Workstation packages to the remote domain's fileserver, then use a login script for devices on that LAN to pull the packages for installation.
I've worked out most of the issues (silent install, installing as admin, etc). My question is, do I have to to create separate installations for the Network Agent and the Workstation, or is there a method to install both of them from one package?
-e
QUOTE(thelettere @ 18.01.2009 11:43) 
I am attempting to deploy Kasperky Network Agents and Workstation to multiple domains and manage them from one Admin Kit (no slave kits).
My plan is to copy the Network Agent and Workstation packages to the remote domain's fileserver, then use a login script for devices on that LAN to pull the packages for installation.
I've worked out most of the issues (silent install, installing as admin, etc). My question is, do I have to to create separate installations for the Network Agent and the Workstation, or is there a method to install both of them from one package?
-e
My plan is to copy the Network Agent and Workstation packages to the remote domain's fileserver, then use a login script for devices on that LAN to pull the packages for installation.
I've worked out most of the issues (silent install, installing as admin, etc). My question is, do I have to to create separate installations for the Network Agent and the Workstation, or is there a method to install both of them from one package?
-e
We recommend for the version 6 to install Network Agent first and after that to create push task for Workstation installation. It is more reliable way to install applications and it works over WAN.
QUOTE(kulaga @ 19.01.2009 04:35)
We recommend for the version 6 to install Network Agent first and after that to create push task for Workstation installation. It is more reliable way to install applications and it works over WAN.
This is not practical for our situation. We are an MSP and looking at using Kaspersky to manage client sites. Some of these offices are 30+ users and we cannot push down a large client package over their T1 to 30+ clients. We have also decided against slave admin kits because of the added complexity. We would prefer to have a single management location with policies that instruct agents to download updates from the internet.
The only hitch we're trying to avoid right now is the initial installation of the packages. We would prefer to copy our package to a local server, then reference that package from local login scripts, hence my initial question.
It looks like it's possible, but I just wanted to see if maybe some others have been down this road before.
-e
QUOTE(thelettere @ 19.01.2009 20:46)
This is not practical for our situation. We are an MSP and looking at using Kaspersky to manage client sites. Some of these offices are 30+ users and we cannot push down a large client package over their T1 to 30+ clients. We have also decided against slave admin kits because of the added complexity. We would prefer to have a single management location with policies that instruct agents to download updates from the internet.
The only hitch we're trying to avoid right now is the initial installation of the packages. We would prefer to copy our package to a local server, then reference that package from local login scripts, hence my initial question.
It looks like it's possible, but I just wanted to see if maybe some others have been down this road before.
-e
The only hitch we're trying to avoid right now is the initial installation of the packages. We would prefer to copy our package to a local server, then reference that package from local login scripts, hence my initial question.
It looks like it's possible, but I just wanted to see if maybe some others have been down this road before.
-e
In case you installed Agents first and make one Update Agent for every site, client package will be downloaded once for all the clients on the site. In any case it is better solution because you'll need to update versions, etc.
QUOTE(kulaga @ 20.01.2009 06:34)
In case you installed Agents first and make one Update Agent for every site, client package will be downloaded once for all the clients on the site. In any case it is better solution because you'll need to updade versions, etc.
Kulaga,
Thank You! The Updating Agents functionality was just what I was looking for.
But leads to another question... does the Updating Agent pull down updates and workstation over the same 13000 port? These sites will not have access to smb shares on the admin kit.
-e
QUOTE(thelettere @ 20.01.2009 20:24)
Kulaga,
Thank You! The Updating Agents functionality was just what I was looking for.
But leads to another question... does the Updating Agent pull down updates and workstation over the same 13000 port? These sites will not have access to smb shares on the admin kit.
-e
Thank You! The Updating Agents functionality was just what I was looking for.
But leads to another question... does the Updating Agent pull down updates and workstation over the same 13000 port? These sites will not have access to smb shares on the admin kit.
-e
Yes, it will use the same 13000 port.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.