Migrating clients to a new ERAS server

I'm following these instructions:
http://kb.eset.com/esetkb/index?pag...se&newguid=0500198034ee29a301267cbebf4c0079ac

but I'm not having any luck getting my ESS clients to pickup the changes I made to the update server and the remote administration settings so that my clients can point to the new ERAS server.

Anyone had success migrating clients to a new server?

Thanks,
Joe

 

We had the problem before, but for us the described way was ok.
We created a config file that includes changes for update- and era- server address.
Please check the port and authentication settings for update and remote administration on the old and new server.

After that we made it a bit smoother Our current era server has a DNS alias entry in our DNS server, called "nod32srv". The client configuration für update and remote now uses only this alias. So a server change is as simple as possible.
Only set the DNS alias to the new server and wait 24 hours (DNS lease time). You can force this be runing ipconfig /flushdns on the clients.

 

I like the DNS route better. I'm going to try that.

Thanks,
JJJ