The configuration loader provides access to configuration from the administration services database. The services drivers and Web services use this loader to access their configuration. This aspect contains the Configuration Loader objects that you can monitor in the Device Management Administration Service. These health monitors include the following detectors.
This condition occurs if MDM Device Management Server cannot communicate with the database server. This issue may occur if any of the following conditions are true:
A network connectivity issue is the most likely cause of this condition. To diagnose the database connection failure events, check the following:
Is the server connected to the corporate network or Intranet appropriately? Is there network connectivity between MDM Device Management Server and the database server?
To check network connectivity, ping the database server from MDM Device Management Server.
If the ping is successful, you will receive a reply similar to the following:
Reply from IP_address: bytes=32 time=3ms TTL=59 Reply from IP_address: bytes=32 time=20ms TTL=59 Reply from IP_address: bytes=32 time=3ms TTL=59 Reply from IP_address: bytes=32 time=6ms TTL=59
If you cannot successfully ping by IP address, the server might be offline, or there might be a network connectivity or firewall configuration issue.
Is SQL Server configured to accept connections?
Verify that the SQL Server Surface Area Configuration is set to allow TCP/IP connections if running on a separate computer from MDM Device Management Server, or Named Pipe connections if running on the same server.
You can verify the database server URI by using the SCPUtil.exe file in the System Center Mobile Device Manager 2008 Resource Kit at this Microsoft Web site: http://go.microsoft.com/fwlink/?LinkId=116260.
In Active Directory Users and Computers, on the View tab, select Advanced Features.
Open the SCMDM2008 Infrastructure Groups organizational unit (OU).
Right-click SCMDM2008DeviceManagementServers group, and then select Properties.
Verify that Device Management Server is listed on the Members tab.
Identify and resolve HTTPS communication issues if there are problems with the MDM Device Management Server and/or database server networking. Problems with HTTPS communications can affect proper MDM operations. Verify that you can access other security-enhanced sites, and that the server is connected to Active Directory.
Ping the server to determine if there is an issue with network connectivity, firewall configuration, or DNS host name resolution:
If the ping is successful, you will receive a reply similar to the following:
Reply from IP_address: bytes=32 time=3ms TTL=59
Reply from IP_address: bytes=32 time=20ms TTL=59
Reply from IP_address: bytes=32 time=3ms TTL=59
Reply from IP_address: bytes=32 time=6ms TTL=59
If you cannot ping the terminal server by IP address, this indicates a network connectivity or firewall configuration issue. To identify and resolve the issue, follow the steps in the "Troubleshooting Steps for Network Connectivity Issues" section later in this topic.
If you can ping the target computer by IP address but not by FQDN, this indicates an issue with DNS host name resolution. To identify and resolve this issue, perform the steps in the "Troubleshooting Steps for DNS Server Accessibility" section and, if needed, the "Troubleshooting Steps for Firewall Configuration Issues" section later in this topic.
Troubleshooting Steps for DNS Server Accessibility
To determine if the DNS servers are configured and accessible, do the following:
Also, if the DHCP Client service is stopped on the terminal server, then name resolution will not function correctly. For more information about identifying and resolving DNS issues, please visit http://go.microsoft.com/fwlink/?LinkId=115516.
Troubleshooting Steps for Firewall Configuration Issues
For problems with communication on the database server, ensure that there is no firewall between servers that blocks necessary ports. Microsoft SQL Server uses port 1433 (by default). To enhance security, you can control which ports are being used so that your firewall router can be configured to forward traffic only to these Transmission Control Protocol (TCP) ports. For more information, see the Firewall Settings topic in the MDM Planning Guide at this Microsoft Web site: http://go.microsoft.com/fwlink/?LinkId=117776.
You can use commands such as Telnet and Netstat to assist in verifying that the appropriate ports enable communication. You should also verify that your firewall configuration is not blocking ICMP replies, which would result in false positive responses. For information about Telnet, please visit http://go.microsoft.com/fwlink/?LinkID=48891. For information about Netstat, please visit http://go.microsoft.com/fwlink/?LinkID=48892.
In MDM, Microsoft SQL Server 2005 Standard Edition with Service Pack 2 is the supported and tested database management implementation. SQL Server Express Edition and Microsoft SQL Server 2008 are not supported for MDM. For more information about how to deploy SQL Server, see the SQL Server 2005 Readme and supporting documentation at this Microsoft Web site: http://go.microsoft.com/fwlink/?LinkId=105613.
The following requirements apply to all MDM servers: MDM Enrollment Server, MDM Device Management Server, and MDM Gateway Server.
Hardware |
Requirement |
Processor |
|
Memory |
4 gigabytes (GB) of RAM. You may have to increase this amount for servers that are running SQL Server. Refer to SQL Server documentation for more information. |
Disk Space |
100 gigabytes (GB) of free hard disk space for installation and data storage |
Network |
One network adapter for each server that is running SQL Server, MDM Enrollment Server, and MDM Device Management Server. Must be 100 Mb/s or faster. Two network adapters for each MDM Gateway Server. Must be 100 Mb/s or faster. |
You must set the domain in which you install MDM to Windows Server 2003 functional level. MDM does not support Windows 2000 mixed domain functional level or Windows Server 2008 domain functional level.
Windows
Each server role in MDM has specific software prerequisites for the installation. Make sure that you update all Windows Server® 2003 operating systems to include the most recent service packs, and that you configure the Windows-based operating system correctly before you start deployment.
To view administrator options to update Windows-based operating system servers to include the most recent updates, see the Microsoft Web page: http://go.microsoft.com/fwlink/?LinkId=106611. For more information about Microsoft security, see the Microsoft Security Web page: http://go.microsoft.com/fwlink/?LinkId=62649.
The MDM infrastructure described in this section assumes that all servers are using a clean installation of the Windows-based operating systems, applications, and services listed. All software versions listed show the minimum version required.
The MDM Best Practices Analyzer Tool helps you analyze a group of servers to determine if prerequisites for deploying MDM are met. The tool also lets you analyze servers post-deployment to verify settings such as port settings. To download MDM Best Practices Analyzer Tool, see the MDM Resource Kit Tools page at this Microsoft Web site: http://go.microsoft.com/fwlink/?LinkID=108953.
Role |
Operating system |
Applications and services |
SQL database server |
Windows Server 2003 with Service Pack 2 (SP2) |
|
MDM Device Management Server |
Windows Server 2003 Standard x64 Edition with SP2 |
|
MDM Enrollment Server |
Windows Server 2003 Standard x64 Edition with SP2 |
|
MDM Gateway Server |
Windows Server 2003 Standard x64 Edition with SP2 |
|
To set the database server URI and instance name, perform the following operations using SCPUtil.exe distributed with the MDM Resource Kit Tools . To download this utility, see the MDM Resource Kit Tools page at this Microsoft Web site: http://go.microsoft.com/fwlink/?LinkId=127030.
An alternative method for setting the database server URI and instance name is to check the MDM instance object under the System/SCMDM object (for example, CN=SCMDM,CN=<instance name>,CN=System,DC=contoso,DC=com).
Examine the keywords property to determine the current settings for the database URI and instance.
Add Computer Account to SCMDM Active Directory Groups
SCMDM Active Directory Groups are used to grant permissions to servers and services to perform MDM operations. If a computer account was removed from an SCMDM Active Directory Group, you may see permissions errors. To resolve this issue, follow these steps:
In Active Directory Users and Computers, on the View tab, select Advanced Features.
Open the SCMDM Infrastructure Groups organizational unit (OU).
Right-click the SCMDMDeviceManagementServers group, and then select Properties.
On the Members tab, select Add.
Select Account Types.
Select Computer Accounts, and then click OK.
Type the name of the computer account that you want to add to the SCMDMDeviceManagementServers group. You should add a computer only if there is a trusted MDM Device Management server on this computer. Do not add a computer to a group before running MDM Setup.
Click OK to close the dialog box.
Click OK again to close the dialog box.
You can repeat the above steps for other server groups (such as SCMDM EnrollmentServers) as necessary.
Target | Microsoft.SystemCenter.MobileDeviceManager.2008.1_1.AdminServiceCore.ClassType | ||
Parent Monitor | System.Health.ConfigurationState | ||
Category | StateCollection | ||
Enabled | True | ||
Alert Generate | True | ||
Alert Severity | MatchMonitorHealth | ||
Alert Priority | Normal | ||
Alert Auto Resolve | True | ||
Monitor Type | Microsoft.Windows.3SingleEventLog3StateUnitMonitorType | ||
Remotable | True | ||
Accessibility | Public | ||
Alert Message |
| ||
RunAs | Default |
<UnitMonitor ID="Microsoft.SystemCenter.MobileDeviceManager.2008.1_1.AdminServiceCore.ConfigurationLoader.MobileDeviceManager.NewDiagnoser.EventBased.UnitMonitor" Accessibility="Public" Enabled="onEssentialMonitoring" Target="Microsoft.SystemCenter.MobileDeviceManager.2008.1_1.AdminServiceCore.ClassType" ParentMonitorID="SystemHealth!System.Health.ConfigurationState" Remotable="true" Priority="Normal" TypeID="Windows!Microsoft.Windows.3SingleEventLog3StateUnitMonitorType" ConfirmDelivery="true">
<Category>StateCollection</Category>
<AlertSettings AlertMessage="Microsoft.SystemCenter.MobileDeviceManager.2008.1_1.AdminServiceCore.ConfigurationLoader.MobileDeviceManager.NewDiagnoser.EventBased.UnitMonitor.AlertMessage">
<AlertOnState>Warning</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>MatchMonitorHealth</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Data/Context/EventDescription$</AlertParameter1>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState ID="Success" MonitorTypeStateID="FirstEventRaised" HealthState="Success"/>
<OperationalState ID="Warning" MonitorTypeStateID="SecondEventRaised" HealthState="Warning"/>
<OperationalState ID="Error" MonitorTypeStateID="ThirdEventRaised" HealthState="Error"/>
</OperationalStates>
<Configuration>
<FirstComputerName>$Target/Host/Host/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</FirstComputerName>
<FirstLogName>Mobile Device Manager</FirstLogName>
<FirstExpression>
<And>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery>PublisherName</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>Device Manager</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery>EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>6001</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</And>
</FirstExpression>
<SecondComputerName>$Target/Host/Host/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</SecondComputerName>
<SecondLogName>Mobile Device Manager</SecondLogName>
<SecondExpression>
<And>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery>PublisherName</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>Device Manager</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery>EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>6104</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</And>
</SecondExpression>
<ThirdComputerName>$Target/Host/Host/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ThirdComputerName>
<ThirdLogName>Mobile Device Manager</ThirdLogName>
<ThirdExpression>
<And>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery>PublisherName</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>Device Manager</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery>EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>6201</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</And>
</ThirdExpression>
</Configuration>
</UnitMonitor>