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.