Thomas; Changing the IP Address of the MSP Server itself will have no impact on devices, since devices never access the MSP Server, per se.  It means that anyone accessing the MSP Console UI will need to change the URL they use unless they are accessing by DNS name.  Also, if using HTTPS, the certificate may need to change to avoid security warnings. Placing a Relay Server on the same box as the MSP Server is optional, and one of the downsides of doing so is that changing the IP Address of a Relay Server is not as easy as changing the IP Address of the MSP Server, since devices DO access the Relay Server, as does the MSP Server.  So, if you have the MSP Server and the Relay Server on the same box, then you will need to take some action to prevent problems. The Relay Server Object in MSP describes how to access the Relay Server from both the MSP Server (public information) and from the devices (private information).  The devices were configured to reach the Relay Server when they received the Settings based on that Relay Server Object.  So, BEFORE you change the IP Address of the Relay Server, you need to change the IP Address information in the Relay Server Object and push new Relay Server Settings to all the devices and make sure they have them.  Note that since you have not changed the Relay Server IP Address yet, once a device gets new Settings, it will be unable to access the Relay Server until the IP Address of the Relay Server itself is changed.  But you need to wait until all the devices have received the new Settings before changing the IP Address or they never will because once you change the Relay Server IP Address, they will be unable to contact it using the old Settings they have. To actually push out the new Relay Server Settings, you can use a step in an Install Package Step in a Bundle, with the Content - Relay Server option to include the Settings for a Relay Server as content to be deployed to the device.  Or, if you are using Sites, you can push the Site Bundle for the Site, which will include the Relay Server Settings, by using Content - Site as the Bundle deployed. If any devices do not get the new Relay Server Settings before the Relay Server IP Address is changed, then you will need to re-Stage those devices to get them configured, since MSP will lose its ability to push content to them since they have lost the ability to reach their configured Relay Server. Another approach that can be used is to configure the NIC on the Relay Server to have 2 IP Addresses, the old and the new.  Then, you can change the Relay Server Object to use the new Address and push it out to all the devices.  Since the Relay Server will respond to either address, devices will continue to check-in whether they have new Settings or old Settings.  Once all devices have the new Settings, you can retired the old IP Address. The above situations are one good reason why it is often a good idea to have a separate Relay Server.  If the Relay Server had been separate from the MSP Server, then the IP Address of the MSP Server could have been changed and no changes (aside from how Workstation PCs access the MSP Console UI) would have changed.