Microsoft System Center Configuration Manager 2007 mobile device management uses the device ID to identify managed mobile devices. All currently available consumer Pocket PC devices support a unique hardware ID that the Mobile Device Management Agent uses as the Microsoft System Center Configuration Manager 2007 unique identifier, and the mobile device management functionality works as designed.
Certain industrial mobile devices do not report a unique device ID, so multiple mobile devices share the Configuration Manager 2007 unique identifier, rendering the devices individually unmanageable by Configuration Manager 2007. The result is that only a single mobile device discovery data record (DDR) appears in the Configuration Manager 2007 Administrator console, even though multiple mobile devices are successfully communicating with the Configuration Manager 2007 device management point.
To remedy this, create a registry script or use another method to change two registry keys on the mobile device.
Use alternative Device Client registry settings to change DeviceID behavior. To do this, create a registry script or use other means to change two registry keys on the device as follows:
To change registry keys on mobile devices to provide unique device IDs
Using a registry editing tool or the registry configuration item, add a DWORD registry value SimDeviceID under the registry key: HKLM\Comm\ApplicationDownload\SimDeviceID.
Set the value to 0. SimDeviceID accepts one of the following values:
- Value 0 : Use Hardware ID. This is the
- Value 1 : Generate an ID based on random
- Value 2 : Generate ID from MAC address. If
this fails return ID "NO_MAC_ADDR_DEVICE"
- Value 3 : Generate ID from MAC address. If
this fails, generate an ID based on random numbers.
- Value 0 : Use Hardware ID. This is the default value.
Delete the registry value DeviceID from the registry key HKLM\Comm\ApplicationDownload.
The changes will not take effect until a soft reset is performed on the mobile device.
If the mobile device client is running and these changes are made, the mobile device client must be restarted via a soft reset in order for these changes to take effect.
|SimDeviceID value options 2 or 3 might leave the mobile device client agent unable to acquire a MAC address because mobile device networking components are still initializing. Values 2 and 3 are not recommended for resetting the DeviceID.|