Everythings gone black

Avast Business Avast Endpoint Protection
1

Hi there, hope you guys can help me out with this.

I’ve been running The ADNM from my office for a couple of weeks now, got everything working the way i want it and decided to move it into it’s production location (which is on a different sub net) I didn’t think this would be an issue. I changed the EAS from a 192 sub net to a 10. Now all my clients have gone from green to black and i can’t communicate with them. I tried changing the EAS address in the group properties to the machine name and let dns pick it up but it hasn’t made any difference.

I don’t want to redeploy to all my clients again as this will mean another 300 reboots and another 300 unhappy faces.

Is there a painless way to resolve this?

Thanks in advance.

** I have moved this post into the business protection section from ADNM as i am using the AEA control panel **

Additionally, last night i added a second nic to the box and gave it the original IP when i was doing the testing This morning the AEA has now picked up all the systems on that sub net, but not on the other 3. I did read in another post that a solution was to run from a script ASWCHAMS.EXE and point the client systems to the new ip, but when i drill down in my install i don’t have this file.

Sorry if this is a bit disjointed, any help would be appreciated.

2

I have managed to resolve this issue, so just in-case someone suffers the same fault, this is what i had to do.

If you look in the avast5.ini file located on the client the config is pointing to (in my case the test ip address) of 192.168.40.44. This needs to point to the new server ip address of 10.0.0.221.

The server was returned to the original sub net and the primary nic card (the one with a DG) was set to the old ip address and the secondary to the new, also the computer catalog communication setting is pointing to the new ip address, this way the clients can connect and their configs are updated with the new ip.
Now when the server is on the correct sub net, the client systems are already looking for the correct ip.

I realize the easy way to do this is to re-deploy but it wasn’t a good option for me.