Help - Search - Members
Full Version: Admin Kit 6 Setup
Kaspersky Lab Forum > English User Forum > Protection for Small and Medium Businesses
Balsa
Hello,

I am asking you for idea about installing Kaspersky Admin Kit 6 in network. We have a network with 300+ work stations and 40+ servers. The problem is that this is a network of small branches,and every branch is in another city. Connection between branch`s are somewhere 256Kb ,and somewhere up to 2Mb. But the most part of branch`s are connected with 256Kb link to central branch. We have installed KAV for Workstation on all machines, and when I wanted to put them on one Admin Kit server we have a problem with network throughput,because Admin Kit have numerous connections with all machines in network, that`s why our network was literally down for a time when Admin kit was working. Because that I shut down admin kit server.
Now I have one idea how to implement Admin Kit on this kind of network, just to see with you guys is this possible or someone of you have a better idea.

I planned to do it like this:

- To install in every branch one slave admin kit server, and to add computers from that branch to that server. So every branch will have one slave Admin Kit server, with work station from that branch where is Admin kit.

-To install and setup one master Admin kit server in central branch, and to add only slave servers to it. So when I want to make a policy for updating,scanning,deployment, etc... give a command to other slave servers from main master server, and this communication is only between servers, and will not effect on network. All other tasks are done by slave servers inside the branch,so network will not be overload.

What do you think about this ?? And is this possible? Or maybe someone have a better solution??....
Does someone have similar situation??

Thanks and regards.
phr3n1c
It's nearly the best practise wink.gif

I agree with your idea. Just add the clients of the HQ to the master administration kit and the clients and server of the braches to the slave administration kit. Then add the slave administration kits to the logical groups of the master adminkit. I would suggest to create for every branch (where a slave adminkit is installed) a group on the master where to connect the slaves.
Balsa
QUOTE(phr3n1c @ 6.03.2009 13:43) *
It's nearly the best practise wink.gif

I agree with your idea. Just add the clients of the HQ to the master administration kit and the clients and server of the braches to the slave administration kit. Then add the slave administration kits to the logical groups of the master adminkit. I would suggest to create for every branch (where a slave adminkit is installed) a group on the master where to connect the slaves.



Thanks!

That is exactly what I wanted to do. Sorry for my English,that is the reason why I can not explain this plan accurate as you smile.gif

Do you have any document or a case study for this kind of project???
phr3n1c
Your English is very good to understand so no need to sorry. wink.gif

I just have informations in german regarding this issue. But there is a knowledgebase entry which probably could help you: http://support.kaspersky.com/ak6mp1/implem...g?qid=204441745
Tybilly
Hello,

I think you'd better find a solution to your initial problem, you must be able to manage all your workstations from your central point.

Your network has been probably overloaded because of network discovery, that you can disable in the properties of your Administration Server.

You can optimize even more by changing the default synchronization period from 15 minutes to 30.

Of course, update task of KAV on branches having low bandwith must be performed from KL update server or with the help of an update agent.
Balsa
Thank you very much.

When I finish the project, I will give you the information how everything worked.

See you,and thanks again.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2009 Invision Power Services, Inc.