I’ve recently moved Avast ADMN to a new server. The move appeared to go well. All the client PC’s at my main branch started communicating with the new server within 30 minutes or so. The issue lies with the PC’s at my branch office. Their avast.ini file still had the old server’s IP addreses. I started them all in save mode an changed the iP addrreses to the new server. However, they still do not show up in green in the ADMN. Does anyone have any ideas what the problem may be?
why didnt you use the commandline ??
aswchams xxx.xxx.xxx.xxx
where xxx is the IP of the new AMS server (possibly also works with DNS name)
How did you do it? Did you red manual, chapter about moving AMS?
It’s difficult to help without more precise information… (Information about your previous steps and about your infrastructure)
I moved Avast ADMN from a Windows 2003 server to windows 2008R2. I followed the admin guide. I installed ADMN and setup a SQL database on new server, moved certificate and license. I backed up the old database on old server and restored to new server. The clients started checking in with new server within 30 minutes or so at our main branch office. However, our satellite office PC’s were still not communicating with new server. I saw in other posts about editing the Avast.ini file in safe mode. Where it was only 10 PC’s, it wasn’t that big a deal to do it. However they still are not communicating with the new server.
Creating a login script or batch file to put in group policy with the ASWCHAMS.exe utility and the new ip address of the server. It should fix all of the computers without you even having to get out of your chair.
that’s what I’ll do then-thanks