I will need to move Avast AEA Build 8.0.355 from a windows 2003 server to a Windows 2012 server. What is the best procedure to follow to accomplish this? The end result is that the client PCs are to be managed from this 2012 server. All clients are running the version 8.0149.
Thanks
The absolute easiest way is to give the new server the same IP as the old server it is replacing… If the 2k3 server is EOL. You can test policy with a lab desktop while the 2012 server on a different IP address, once satisfied things are working, give it the old server address and watch the clients connect.
The new server needs to have a different IP address.
Setup new server, build new client installer, re-deploy clients.
On the new server setup the Avast services again.
Then on the old server on the container propperties give the new IP address from the new server. Let them run together for a while so all clients get a chance to get the new policies. Then decommision the old server if all if moved.
If there are clients that dont function propperly, redeploy those.
Thats how i did it in the past, essential is to be able to have both machines running along sides for a period of time.
Years ago I remember restoring the database from the old server to the new server and changing the IP address in the console. At that time I was going from 2003 to 2003. Would the same not work from 2003-2012? Also using your method am I able to deploy the same license file to the new server or need to wait until the old server is decommissed?
The procedure described by @wpn is the best and simple method to change the AMS to a new server.
Using this method, will I need to manually recreate all my computer groups and all my file exclusions? Or does all this can transfered over to the new server automatically once I change the IP address in the container properties in the EAS of the old server?
Yes, with this method you have to reconfigure all your setups.
With this method you change the remote IP adress of the AES in all the clients, but not the groups or configurations.
Where is the SQL database?
The current SQL database is on the old server with the live AES. Looks like I’ll have lots to reconfigure manually using this method, this was why I thought perhaps a backup/restore of the database to the new server would save time.
Yes, you can follow this method and you can restore a SQL BackUp in the new server.
I’m in this same situation - and I have already set up my new server, but I don’t have access to my original. Am I able to just deploy new client installs overtop of the old ones that pointed to an old IP address, and the existing client installs will update and link back to the new server’s settings?
@brandtly
yeah that SHOULD work, you can test with 5 computers that are directly next to you or at least in walking distance 