Export (0) Print
Expand All

Mobile Device Clients Connected via ActiveSync or Mobile Device Center Might Have Problems Locating Distribution Points

Applies To: System Center Configuration Manager 2007, System Center Configuration Manager 2007 R2, System Center Configuration Manager 2007 R3, System Center Configuration Manager 2007 SP1, System Center Configuration Manager 2007 SP2

Microsoft System Center Configuration Manager 2007 mobile device clients connected via ActiveSync or Mobile Device Center receive a private IP address instead of an IP address reflecting the actual network location of the mobile device. The mobile device client then uses the private IP address when attempting to locate distribution points, which often causes the mobile device client to attempt to download content from an incorrect location. In certain scenarios, the mobile device client might not be able to locate a valid distribution point.

Configuration Manager 2007 includes new functionality that assists in resolving this issue. Creating and configuring a new registry key on the mobile device management point allows the Device Management Point to identify the private IP addresses and subsequently replace the private IP address with one parsed directly from the HTTP communications with the connected computer. The device management point uses the new IP address to identify valid distribution points.

Registry Keys to Replace IP Addresses

The following registry key values support replacing the IP address of the mobile device for 32-bit systems:

HKLM\Software\Microsoft\Sms\MP\ Device Management\Check for ActiveSync Devices
0 = Off: Disabled.  
1 = On: Check device client IP addresses against the ActiveSync Addresses list.
HKLM\Software\Microsoft\Sms\MP\ Device Management ActiveSync Addresses

The following registry key values support replacing the IP address of the mobile device for 64-bit systems:

HKLM\Software\Microsoft\Wow6432Node\Sms\MP\ Device Management\Check for ActiveSync Devices
0 = Off: Disabled.  
1 = On: Check device client IP addresses against the ActiveSync Addresses list.
HKLM\Software\Microsoft\Wow6432Node\Sms\MP\ Device Management ActiveSync Addresses

Use the following procedure to replace the private IP address of the mobile device with an address from the HTTP communications with the connected computer.

Procedures

To replace the private IP address of the mobile device with an address from the HTTP communications with the connected computer

  1. Create a new registry key, named Device Management, under HKLM\Software\Microsoft\Sms\MP\ for 32-bit systems, or under HKLM\Software\Microsoft\Wow6432Node\Sms\MP\ for 64-bit systems.

  2. Create a new value, named Check for ActiveSync Devices (type hexadecimal), under HKLM\Software\Microsoft\Sms\MP\Device Management (DWORD) for 32-bit Systems, or HKLM\Software\Microsoft\Wow6432Node\Sms\MP\ Device Management (DWORD) for 64-bit systems.

  3. Edit ActiveSync Devices, and set the value to 1 to enable checking for ActiveSync mobile devices.

  4. Create a new value, named ActiveSync Addresses (type multi-string), under HKLM\Software\Microsoft\Sms\MP\Device Management for 32-bit systems, or HKLM\Software\Microsoft\Wow6432Node\Sms\MP\ Device Management for 64-bit systems.

  5. Enter the list of ActiveSync addresses in your environment. For example, 192.168.55.101 is a possible ActiveSync address value.

See Also

For additional information, see Configuration Manager 2007 Information and Support.
To contact the documentation team, email SMSdocs@microsoft.com.
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft