I'm sorry if this topic has already been posted, but I could not find the right solution to my problem.

I am running Kaspersky Administration Kit 6.0.1711 on Windows Server 2003 SP2. I have around 2500 client machines currently running NetAgent 6.0.1710 and KAV 6.0.3.837. My Default Policy is set so that it is password protected, anti-hacker is disabled, anti-spam is disabled ,and several other settings. Everything except protection is locked.

My problem is that many of my client machines are losing their connection to the admin kit and reverting to everything enabled and unlocked with no password. This is a real problem for our client backups, remote assistance, several enterprise applications, and users exiting KAV because there is no password set.

For example- I have a Windows XP SP2 computer that shows on the admin console as online, but the policy does not apply to it. When I run klnagchk the results come back ok. I have a Windows Vista SP1 computer that is turned on and on the network, but the admin console shows it as offline. The Default Policy is not applying to tit and when I run klnagchk I get the following results:



How can I fix this problem and keep it from returning? This is becoming a huge deal for us and until we can fix it it is conflicting with daily operations. Thanks for any help

The best way is to change the name to the IP-address from the server.

You can use klmover to change the address.

Server address is not specified.

Run klmover on the problem computer with command line

You can use klmover to change the address.
klmover -address <server_name_or_ip>

Thanks for the help.

Oh God, thank you for this post! I have the same problem with KAV WKS MP4 for a couple of months testing the new versions. All the clients installed the new Network Agent version fails to connect to the Admin Kit server because of the:
#1187 (0) Bad parameter "address"

see more here

I've set the correct NETBIOS name (not the IP address) of the Admin server in the Network Agent install package, but the problem persists. Now, finding this topic I can fix it manually. It's great! Thank you very much!
Is there any way to run this script as a task from remote ? I don't want to run this manually on clients if it's unneccesary. Please help me!

thank you guys!

regards

corvex

Is this way that ?
In the Admin Kit choosing Tasks for specific computers->Create new task->Task type: Kaspersky Admin Kit: Advanced: Change Kaspersky Administration Server in this section I set the correct server name. Creating this task it cannot be run on clients, in Admin Kit this task seems as an 'Applied task', it sits in the "queue" and nothing when I try to start it. In the process window it says: pending. Is this the right solution for my problem ?

If I got you right, you have clients, that cannot communicate with the administration kit. So how should administration kit tell the clients to switch to itself via his own tasks?

But you could write a batch-script with the correct command line parameters and deploy it with active directory group policies for example.

Delete all tasks associated with the defulat Network Agent package 8.0.20.48. Then delete the package itself.

Create a new Kaspersky Lab package with the netagent.kpd in c:/kav/administration kit/en/packages/network agent 8.0.2048

Deploy this new package. This will stop the 1186-1187 errors.

I've done this last week and there was nothing changed.
Anyway, I've already fixed them manually (locally).

thanks