Recovering from Server and Device Name Changes

  • Article

2/9/2009

In general, you should not change server names because doing so may cause MDM to experience unexpected errors that lead to malfunctioning or disruption of normal MDM operations. If you must change the names of servers or load balancing devices, then follow the guidance below.

Warning

Modifying the names of MDM Device Management Server and MDM Enrollment Server is not recommended nor supported. Doing so requires extensive changes to Active Directory, the certification authority, certificates on all Web sites, and SQL Server database tables.

For information about the naming conventions supported by MDM, see Best Practices in MDM Deployment.

SQL Server Name Changes

If you change the server name for SQL Server, then you should redirect MDM to the new server name by completing the following steps:

  1. Open adsiedit.msc, expand <domain name>, expand DC=<domain name>,DC=com, expand CN=System, and then expand CN=SCMDM.
  2. Right-click CN=<instance name>, and then select Properties.
  3. In the CN=<instance name> Properties dialog box, on the Attribute Editor tab, scroll down to select the keywords attribute, and then select Edit.
  4. In the Multi-valued String Editor dialog box, change the following values to reflect the new SQL Server and instance name if the default SQL Server instance is not used:
    • database = <database server name or database FQDN>
    • sqlinstance = <SQL Server instance name> if specified; else this value is blank
  5. In the Multi-valued String Editor dialog box, select OK.
  6. In the CN=<instance name> Properties dialog box, select OK.

For more information on modifying the Active Directory service connection point (SCP), see Modify an MDM Active Directory Service Connection Point.

Load Balancer Name Changes

If you change the name of the load balancer virtual IP address for MDM Device Management Server or MDM Enrollment Server, then complete the following steps to update the settings for MDM:

  1. Open adsiedit.msc, expand <domain name>, expand DC=<domain name>,DC=com, expand CN=System, and then expand CN=SCMDM.
  2. Right-click CN=<instance name>, and then select Properties.
  3. In the CN=<instance name> Properties dialog box, on the Attribute Editor tab, scroll down to select the keywords attribute, and then select Edit.
  4. In the Multi-valued String Editor dialog box, update the following values, or add them if they do not exist:
    • dmadminurl = <FQDN for MDM Device Management Server or load-balanced virtual IP address>:port (default port is 8446)
    • dmurl = https://<FQDN for MDM Device Management Server or load-balanced virtual IP address/MDM/TEE/Handler.ashx
    • enadminurl = <FQDN for MDM Enrollment Server or load-balanced virtual IP address>:port (default port is 8445)
    • enurl = https://<FQDN for the external, internet-facing MDM Enrollment Server URL>:port/EnrollmentServer/Service.asmx (default port is 443)
  5. In the Multi-valued String Editor dialog box, select OK.
  6. In the CN=<instance name> Properties dialog box, select OK.
  7. Update the certificates on all MDM Device Management Server and MDM Enrollment Server Web sites, following the steps described in Manual Certificate Procedures.