Share via

Taking MDM Servers Offline

  • Article

2/9/2009

You must remove your MDM Enrollment Servers and MDM Device Management Servers from any load balancer if used and ensure that MDM Enrollment Server and MDM Device Management Server are not receiving requests from managed devices, or from MDM Administrator Tools, until a specified time later in the upgrade process. Also, you must prevent MDM Device Management Server and MDM Enrollment Server services from interacting with MDM databases during the upgrade process. The following steps must be performed in order:

  • Take all servers that are running MDM Device Management Server offline from the load balancer, make sure that the operating system is running, and that they have Active Directory and database connectivity. Make sure that each server that is running MDM Device Management Server is unable to receive requests from MDM Administrator Tools or managed devices.
  • Take all servers that are running MDM Enrollment Server offline from the load balancer and make sure that they only have database connectivity. Make sure that each server that is running MDM Enrollment Server is unable to receive requests from MDM Administrator Tools or from devices.
  • On the MDM Enrollment Server, open the Services console and stop the SCMDM Enrollment Service service. Then change the startup type to Manual. Repeat this step for all MDM Enrollment Servers you plan to upgrade.
  • On the MDM Device Management Server open the Services console and stop the SCMDM ADGP Service, SCMDM GCM Service, and the SCMDM Wipe Service services. Then change the startup type for each to Manual. Repeat this step for all MDM Device Management Servers you plan to upgrade.

Important

Setting these services to manual will help ensure that MDM Enrollment Server and MDM Device Management Server do not communicate with the MDM databases during the upgrade process. When you upgrade both server roles in following steps, the setup installation will change these service startup types back to Automatic.

  • Windows Server Update Services (WSUS) must not be running during the upgrade process. This includes the Internet Information Services (IIS) Web site for WSUS and associated services. If it is running, WSUS will continue to serve package requests to managed devices while the MDM TEEDB database and SCMDM Software Distribution Service are not functioning during the upgrade. You may see errors such as the MDM Software Distribution Console reporting that packages that were installed already are still applicable for the device. To prevent WSUS activity during the upgrade process you must temporarily stop the WSUS IIS Web site, the SCMDM Software Distribution Service, and the WSUS Update Services service.

    • On the MDM Device Management Server open Internet Information Services (IIS) Manager and stop the WSUS Administration web site. Open the Services console and stop the services Update Services and SCMDM Software Distribution Service.

      Note

      You will be asked to restart these services at the end of the MDM Device Management Server upgrade. After the upgrade process is complete, you may see package failed errors in the MDM Software Distribution Console. If this is so, you must redeploy the failed package to managed device clients.