Hi there,
We manage several clients running Kaspersky with separate admin kits on each site. These sites run a master admin kit with its own policies, tasks, and so on. Naturally, we are looking at centralizing KAV management from one admin kit. Now the question:

If you were in my shoes would you...
Have one central admin kit managing all client servers / workstations without an admin kit installed at each site? I proved this theory with my laptop and an external admin kit but it was sluggish at windows logon and I get the feeling Kaspersky wasn't intended to function this way.

Or

Have one central admin kit pushing out policies, tasks, updates and so on to many slave admin kits installed @ each site?

Experiences and ideas with both approaches are much appreciated.

Thank you guys, you do a great service by answering these questions ... let me know if I was unclear in any way and I will explain further.

Hi,

I would say that I rather prefer to have only 1 Administration Server to manage the entire network which is more practical to maintain. The only restriction is that your Administration Server should be reachable from outside of your network with a DNS name or a public IP address but on the other side it allows you to manage your client computers even when they are out of the corporate network.

It makes sense to have slaves administration server unless you want to delegate the deployment and maintenance to someone else on the remote site, otherwise it's better to have only 1 server.
And I don't know about your logon issue, it should not affect the startup time at all even if you have an external AdminKit.

How many sites?
How many workstations/servers at each site?
What capacity link to the different sites?