Jump to content
Support_Mike

Admin Kit and Active Directory

Recommended Posts

DISCLAIMER: This question has not been thought out, researched, or really considered.

 

A customer has 100 workstations, all XP Pro SP2, all run KAV WKST 5.0.227. All need to be managed by the Admin Kit installed on one of his servers. Some of the workstations are not members of his Active Directory, but instead are stand-alone, peer-to-peer workstations. The Admin Kit is installed on a server that is using Active Directory. He is able to deploy to the non-ADS machines w/o error or problem. When he looks at non-ADS clients in the Admin Kit he sees that they are all "Out of Control", (I know what this means). Any reason why we cannot have non-ADS clients in an Admin Kit-managed logical network with ADS clients????

 

Mike

Share this post


Link to post
DISCLAIMER: This question has not been thought out, researched, or really considered.

 

A customer has 100 workstations, all XP Pro SP2, all run KAV WKST 5.0.227. All need to be managed by the Admin Kit installed on one of his servers. Some of the workstations are not members of his Active Directory, but instead are stand-alone, peer-to-peer workstations. The Admin Kit is installed on a server that is using Active Directory. He is able to deploy to the non-ADS machines w/o error or problem. When he looks at non-ADS clients in the Admin Kit he sees that they are all "Out of Control", (I know what this means). Any reason why we cannot have non-ADS clients in an Admin Kit-managed logical network with ADS clients????

 

Mike

 

The most probable reason is that non-ADS clients unable to resolve Admin Kit server name and connect to the Admin Kit server. Please run klnagchk.exe utility in the folder where Network Agent is installed and see the reasons.

Share this post


Link to post

Nice go kulaga! :) And here's some more considerations:

 

The network agent does a lookup for the Admin server with both DNS and IP lookup (including REVERSE!). If it can't find the admin server, you might want to 'wake up' the clients by creating a new task, called 'Change Kaspersky Administration Server', and send that one to the non-AD clients again.

 

Or you can do it 'quick-n-dirty' by inserting the Admin Server's DNS name and IP-address in the hosts file.

Share this post


Link to post

×
×
  • Create New...

Important Information

We use cookies to make your experience of our websites better. By using and further navigating this website you accept this. Detailed information about the use of cookies on this website is available by clicking on more information.