An MDM device returns a "partial success" message because Exchange 2003 does not recognize the device

When a Microsoft System Center (MSC) Mobile Device Manager (MDM) device first tries to partner with Microsoft Exchange Server 2003, the Exchange server pushes policies and then queries for results. The MDM device returns a "partial success" message because Exchange 2003 does not recognize the MDM device. Exchange 2003 treats the attempt to partner as a failure and prevents the device from synchronizing with Exchange 2003.

After you install this hotfix, you must use the Active Directory Service Interfaces (ADSI) Edit tool to change the value of the msExchWirelessAdminEnable attribute on the Exchange server. To edit the msExchWirelessAdminEnable attribute, follow these steps:

1. Click Start, click Run, type adsiedit.msc, and then click OK.
2. In the ADSI Edit tool, expand Configuration Container, expand CN=Configuration,DC= DomainName ,DC=com, expand CN=Services, and then expand CN=Microsoft Exchange .
3. Click CN= Organization Name, and then expand CN=Global Settings.
4. Click CN= Outlook Mobile Access, and then click Properties.
5. Click msExchOmaAdminWirelessEnable in the Attribute list on the Attribute Editor tab, and then click Edit.
6. Add 128 (0x80) to the existing value, type the number in the Value field, and then click OK two times.
   Note If the existing value of the msExchOmaAdminWirelessEnable attribute is 0, you should input 128 (0x80) into the Value field. Otherwise, you should set the value of the msExchOmaAdminWirelessEnable attribute to the total number that is the sum of 128 (0x80) with the existing value of the msExchOmaAdminWirelessEnable attribute. For example, if the existing value of the msExchOmaAdminWirelessEnable attribute is 1, the new input number should be 129 (0x81). If the existing value of the msExchOmaAdminWirelessEnable attribute is 2, the new input number should be 130 (0x82).
7. Exit the ADSI edit tool.
8. Restart the IIS Admin service on all servers that are running Exchange Server in the site.

Hotfix information

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 the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

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, contact 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: Note 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.

Prerequisites

This hotfix requires Microsoft Exchange Server 2003 Service Pack 2 to be installed on the server because of file dependencies.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Restart requirement

You do not have to restart the computer after you apply this hotfix. However, the Internet Information Services (IIS) Admin Service and all dependent services are restarted automatically when you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.