Version 6. Installed admin kit and database on new server, restored backup. Created global task to change clients to use new server. When I click Start task, it doesn't do anything, everything stays 'pending'. What am I missing? Also, probably related, I was able to push an installation to a new client successfully, but I can no longer sync with it and it is not getting updates. ?

Was the ssl-certificate included in the backup?
Did you run the task for changing Network Agent connection settings from the old or new Administration Kit?

I am having the exact same issue. Moved to a new server, and restored the settings from the backup. I can uninstall and install the network agent and the anti-virus, but when I try to run any other task, it just says "Pending".

I am not sure if I included the ssl cert in the backup, but in the backup file, I do see a "certinfo.dat" file, so I'm assuming it migrated to the new server.

Also, I did not un the task to change the Network Agent connection, but I did uninstall both the anti-virus and network agent form a machine, reinstalled both from the Admin Kit, but I end up with the same result. It won't push updates to the machine, as well as any other tasks I have set up. When I try and create the task to do this, it asks me for the location of the cert.

Any idea what I missed? Any idea how I can fix this, or should I just start over? I am in a very small organization, so other than being a pain, it is do-able.

Any help would be much appreciated.

Thank you in advance.

Please have a look, if the ip-address which is set in the configuration of the remote installation package for the network agent in the administration kit is the same as which is configured in the network configuration of the operating system, where the administration kit is installed.

If you still have problems, please provide klnagchk-report as described in the knowledgebase: http://support.kaspersky.com/ak6mp1/all?qid=208279222

You, my friend, are a genius.

Worked like a charm.

Thank you kindly......

--Russ

Changed server name to be consistent between agent package and task, then ran klmover on the new client, that fixed the client issue. As for updating all other clients to the new server, I have to run klmover on each client. We are small enough company so not a big deal. Does that task need to be run from the old server? Still don't know why it doesn't work from the new server.

The new server is only able to connect to 'his' network agents (or network agents connected to the new AK), because at this point network agents still try to connect to the 'old' administration kit. So NAs do not get / accept the task from the new AK.

The task to change the connection settings of the network agent has to be run from the old Administration Kit under all circumstances.

You could create a batch file with the corresponding klmover-command and roll out the batch file with the Administration Kit, if you like.

I suggest a quick script with HKLM\...\runonce\ and spread it via GPO. Cheers!

Yes, thank you, I guess that makes sense, not very intuitive at first though. Anyway, I appreciate the excellent support, wasn't use to that elsewhere. Now just waiting for version 8... ?