I have a server that I had to re-install Windows on. The corresponding server object in admin kit has not updated with the new information about the server, and so I am unable to manage the server....

Admin kit is ver 6.0.1710.

The server in question started as a windows 2000 server with KAV for Windows Servers ver 5.0.77. Admin kit was able to manage this server.

Then, for unrelated reasons, I had to rebuild the server. I upgraded the OS to Windows Server 2003 R2 Standard, and manually installed KAV for Windows Servers 6.0.3.837. I gave the server the same name and ip address as before. The admin kit still shows the server as having Windows 2000, and KAV 5, and is unable to manage the server. I have also tried opening UDP port 15000 on the host. I shouldn't have to open anything new on the admin kit server, because the admin kit is already communicating with and managing other Windows 2003 R2 servers just fine.

I have tried refreshing, and deleting and re-adding the server object from the group. I even manually uninstalled KAV 6 and then deployed it using the admin kit. The admin kit still will not update the information about this server. Forcing synchronization does not work either. It responds with "Cannot synchronize host settings now. Operation will be completed when host becomes available on the network." But, I know the server is on the network because I was able to deploy KAV 6 to it using the admin kit.

How do I update the host information in the admin kit so I can begin managing this server again?

Thanks,
Jason

fdt93, do you mean under Network: Domains in KAK can't find your server ?
Did you install network agent(NA) in the new server? KAK communicate through network agent to server/pc.
Please check.
If NA is installed, try klmover in the new server to KAK server.
My 2 Yen. Hope this helps

This problem is described in our knowledgebase. Please have a look at this article: http://support.kaspersky.com/ak6mp1/all?pa...p;qid=202902981

Hi guys, thanks for your replies. It turns out the Network Agent had not been installed. I deployed the network agent to the server, and it began communicating with the Admin Kit.