Can anyone explain the basics of how you would typically set up a Kaspersky network? Here is what I would initially think - followed by the issues I am seeing while reviewing the trial version of this software.

A "Master" server with the Administration Kit installed in it's own top-level group - this server pulls down all the updates from Kaspersky servers and pushes them to "secondary" or "Slave" servers - correct?

Multiple "Secondary" or "Slave" each in their own group containing their respective workstation clients. These Slave servers pull down definition updates from the Master server and push them to their clients. Would the slave servers push application updates as well? Do I need to install the Admin Toolkit on these Slave servers (along with SQL Express)?

In a nutshell - the above is how I figured the setup would be. Here are my issues so far:

1) Having trouble pushing the Server application to the second server in my topology. I get the agent on it remotely and when I push the application, the Admin Toolkit says it's installed successfully - but then the properties of the new server under protection says it's not installed. Rebooted several times...no dice. I got o the new server and the Kaspersky icon is running in the system tray.

2) I have no idea how to "create" a "Slave" server or what it's actual role is. When I try to make the newly installed server a "Slave" server, I get an error that "cannot make one's self a slave server". I point to the cert on the "Master" server during this part...is that where I am going wrong? This is what prompts my question whether the Admin Toolkit needs to be installed on a Slave server (that's where the cert comes from) and if so, that requires yet another installation of MSDE or SQL Express.

Sorry for the lame questions...things just don't seem straightforward and I sat on hold for tech support for 3 hours yesterday and nobody picked up...hence my posting questions here.

Any help is appreciated...thanks.

JB

OK...I'll keep it simpler and direct:


If I want to make a server a "Slave" server...do I need to install the Admin Console on it?

Hello,

a "Slave" server is an full Administration Server, with a database and an Administration Console and yes it is mandatory to install console on slave server.

About how to create hierarchy between Administration Servers, you can read this FAQ or documentation.

OK...I read all the FAQ - clears up some questions - thanks for that.

I am still unclear as far as the certificate you are asked to browse to when doing the Slave server setup. Am I browsing to the slave sever over the network and drilling down to it's Admin Console certificate? If I browse to the Master Server's Admin Console certificate - I eventually get the error (during setup) that I cannot make ones self a Slave Server.

That is because you choosed the wrong certificate. When you add the new slave server from the Administration Console of the master server, you have to select the certificate of the slave server, not the master.

You can't make an administration server a slave server of himself ! I don't know if I'm clear, but if you follow instructions then there shouldn't be any problem.

Read from page 59 of the Reference Book for further details about how to add a slave server.