Article ID: 976623 - View products that this article applies to.
This article describes the Microsoft System Center Mobile Device Manager 2008 issues that are fixed in this System Center Mobile Device Manager 2008 hotfix rollup package.
This rollup package resolves the following issues.
Consider the following scenario:
A pre-enrollment request for a user account fails when the common name (CN) of the user account contains a slash mark (/). Additionally, the following event is logged in the Enrollment log:
Event Type: Warning
When System Center Mobile Device Manager 2008 collects certificate details from Windows Mobile devices, some devices send the list of installed certificates two times. This behavior causes the connection to System Center Mobile Device Management Server to fail.
You may receive an exception in the microsoft.mobile.managementservices.common.servicedriverhost.exe application. Then, the following event is logged in the Application log:
Note "<Date>" represents the date that the event is logged.
Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 1000
Description: Faulting application microsoft.mobile.managementservices.common.servicedriverhost.exe, version 1.0.4050.0, stamp 4924b674, faulting module mscorwks.dll, version 2.0.50727.1433, stamp 471ed580, debug? 0, fault address 0x00000000001e565c.
"<Time>" represents the time that the event is logged.
"<Computer name>" represents the computer name.
Cause of issue 1
When the pre-enrollment record is created, the string that follows the comma in the display name is ignored unexpectedly. Therefore, a pre-enrollment record is associated with more than one Active Directory account when these accounts have the same surname.
Cause of issue 2
When you create a pre-enrollment record, the slash mark is not processed correctly.
Cause of issue 3
Mobile Device Management Server does not correctly handle mobile devices that send the list of installed certificates two times. Therefore, connections between Mobile Device Management Server and Windows Mobile devices fail.
Cause of issue 4
Mobile Device Management Server handles the exception that is mentioned in the "Issue 4" section incorrectly. Therefore, Mobile Device Management Server crashes when the exception occurs.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
PrerequisitesTo apply this hotfix, you must have System Center Mobile Device Manager 2008 installed.
Restart requirementYou do not have to restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace a previously released hotfix.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
Contact us for more help
Connect with Answer Desk for expert help.