I’ve made an .msi install package for deployment to PCs outside our firewall. The AMS address is set to the outside IP of the AMS. When the install finishes, it contacts the AMS, joins the root Computer Catalog, and the AMS address is overwritten by the value in the root catalog which in this case is the inside IP of the AMS. The remote clients can no longer communicate with the AMS.
I have found that I have to manually move the client to a sub-group (which has the correct IP) and on the client manually run aswchams.exe {public IP} to get the client to talk to the AMS again.
SO… If I can cause the install file to add the PC to the correct container, I can avoid those manual steps.
Any ideas?
Thanks