Export (0) Print
Expand All

Known Issues for Mobile Device Management

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

The following are known issues affecting Microsoft System Center Configuration Manager 2007 Mobile Device Management.

Smartphones running Windows Mobile 2003 use \Storage as the root folder for the mobile device file structure. Files distributed by Configuration Manager 2007 will appear in the \Storage\Temp folder on Windows Mobile 2003 clients. The \Storage folder is automatically added to the download folder by the mobile device client when distributing packages to Smartphones running Windows Mobile 2003.

Solution

In specifying Program properties or script behaviors for Smartphones running Windows Mobile 2003, the Configuration Manager 2007 administrator does not need to specify \Storage for the Download folder. The \Storage folder is automatically specified by Configuration Manager 2007 when distributing packages to Smartphones running Windows Mobile 2003.

If the mobile device is downloading files when a call is placed to the phone, the call will fail. This behavior is consistent with mobile devices with phone service. Outgoing calls behave normally. Distributing large packages using Configuration Manager 2007 may affect phone service availability.

Solution

Configuration Manager 2007 administrators should schedule distribution to mobile devices for nonpeak hours to avoid interrupting phone service for mobile device users.

When attempting to enroll a personal certificate, if the issuing certification authority (CA) requires manual approval or responds with "Pending" status, enrollment will fail. This can also occur if the CA authorization is delayed for any reason.

Solution

If enrollment fails because the CA is delayed or requires manual authorization, the enrollment process can be rerun by undocking the mobile device and then docking again. If the CA has generated a personal certificate in the interim, enrollment will finish normally.

In 2007, the start and end dates for daylight savings time were changed in North America. Because of this change, Microsoft System Center Configuration Manager 2007-managed Windows Mobile 5 and older Windows Mobile–based devices and Windows CE-based devices might fail to report inventory data and collected files until daylight savings time has been properly updated on the mobile device.

Solution

Update the mobile device for daylight savings time. For more information about how to update a mobile device to account for the new start and end dates for daylight savings time, see the daylight savings time Web page (http://go.microsoft.com/fwlink/?LinkId=91730).

If the Configuration Manager 2007 mobile device client attempts to install via ActiveSync or Mobile Device Center synchronization when the mobile device is transferring a large amount of data from the connected computer, the client installation will fail.

Solution

Resynchronize the mobile device with the computer when less data will be transferred between the two. If the mobile device client transfer and installation fails, use another mobile device client installation method.

If the mobile device client cannot communicate with the fallback status point, it will continue to unsuccessfully send all fallback status point messages to the fallback status point server.

Solution

To verify that the fallback status point is properly configured, use the client health reports and the hardware inventory extensions in the software developer kit to inventory the fallback status point name. Ensure that the fallback status point server is operating correctly and can be reached by the mobile device client. If necessary, update the mobile device client by correcting the FSPServerName value in the ClientSettings.ini file or in the DMCommonInstaller.ini file and redistributing it to the mobile device. For more information about client health reports, see How to Verify Mobile Device Client Health. For more information about configuring the mobile device client settings, see How to Edit the Mobile Device Client Configuration .ini File.

Uninstalling the mobile device client from the mobile device does not remove the shortcut from the mobile device home screen. The shortcut to the uninstalled application will be replaced by other applications as they are used.

Solution

No action is necessary. The shortcut will disappear from the home screen in the course of normal mobile device use.

Managed mobile devices running the System Management Server (SMS) 2003 Device Management Feature Pack (DMFP) client do not appear in Configuration Manager 2007 collections for Pocket PCs.

Solution

To add SMS 2003 DMFP Pocket PC clients running Windows Mobile 2003, add a membership rule containing the following query statement to the existing membership rules for Pocket PCs running Windows Mobile 2003:

select SMS_R_System.ResourceID,SMS_R_System.ResourceType,SMS_R_System.Name,SMS_R_System.SMSUniqueIdentifier,SMS_R_System.ResourceDomainORWorkgroup,SMS_R_System.Client from SMS_R_System inner join SMS_G_System_DEVICE_OS_INFORMATION on SMS_G_System_DEVICE_OS_INFORMATION.ResourceID = SMS_R_System.ResourceId inner join SMS_G_System_DEVICE_COMPUTER_SYSTEM on SMS_G_System_DEVICE_COMPUTER_SYSTEM.ResourceID = SMS_R_System.ResourceId where SMS_R_System.ResourceType = 5 and SMS_R_System.ClientType = 3 and SMS_G_System_DEVICE_OS_INFORMATION.MajorVersion = 4 and SMS_G_System_DEVICE_OS_INFORMATION.MinorVersion like '2%' and SMS_G_System_DEVICE_COMPUTER_SYSTEM.PlatformType = 'PocketPC'

To add SMS 2005 DMFP Pocket PC clients running Windows Mobile 2005, add a membership rule containing the following query statement to the existing membership rules for Pocket PCs running Windows Mobile 2005:

select SMS_R_System.ResourceID,SMS_R_System.ResourceType,SMS_R_System.Name,SMS_R_System.SMSUniqueIdentifier,SMS_R_System.ResourceDomainORWorkgroup,SMS_R_System.Client from SMS_R_System inner join SMS_G_System_DEVICE_OS_INFORMATION on SMS_G_System_DEVICE_OS_INFORMATION.ResourceID = SMS_R_System.ResourceId inner join SMS_G_System_DEVICE_COMPUTER_SYSTEM on SMS_G_System_DEVICE_COMPUTER_SYSTEM.ResourceID = SMS_R_System.ResourceId where SMS_R_System.ResourceType = 5 and SMS_R_System.ClientType = 3 and SMS_G_System_DEVICE_OS_INFORMATION.MajorVersion = 5 and SMS_G_System_DEVICE_OS_INFORMATION.MinorVersion <= 1 and SMS_G_System_DEVICE_COMPUTER_SYSTEM.PlatformType = 'PocketPC'

For more information about creating collections using queries, see How to Use Queries to Create Windows Mobile Device Collections.

If mobile device clients will communicate with an intranet-based device management point, it might be necessary to use the NetBIOS name when defining the device management point in the .ini configuration file during mobile device client setup. This allows the device management point to be resolved even if proxy settings are used for the mobile device to allow it to browse the Internet. Alternatively, set a rule on the proxy server to allow the mobile device to resolve the fully qualified domain name (FQDN) of the device management point on the intranet and also access Internet content.

In the advertisement properties for an advertisement to mobile device clients, when you change the package for an advertisement created previously, the package change will not take effect if you leave the General tab or select any option other than OK on the General tab.

Solution

After changing the package, click OK on the General tab and then reenter the advertisement to verify that the package change has taken place or to make any additional changes.

When you upgrade a System Management Server (SMS) 2003 site with the Device Management Feature Pack to Configuration Manager 2007 or when you upgrade the parent of an SMS 2003 with the Device Management Feature Pack, the default collections for All Windows Mobile Devices and All Windows Mobile Pocket PC 2003 Devices are upgraded to use the new membership selection queries included with Configuration Manager 2007. When this happens, all of the SMS 2003 Device Management Feature Pack clients are dropped from the collections due to a change in the query.

Solution

Before upgrading, in all SMS 2003 sites with the Device Management Feature Pack installed on them, create new collections with different names that use the same query as the default Device Management Feature Pack collections. Verify that all SMS 2003 mobile device clients are members of the collections before upgrading to Configuration Manager 2007. If you have a child site with the Device Management Feature Pack that will not upgrade to Configuration Manager 2007, you should also modify your advertisements to use the newly created collections. After the mobile device client is upgraded to Configuration Manager 2007, the mobile devices appear in the Configuration Manager 2007 default collections.

Some configuration items shipping in Configuration Manager 2007 will not function properly on Windows Mobile 6 platform mobile devices because of changes in the Configuration Service Providers shipped on Windows Mobile 6.

Unsupported configuration items on Windows Mobile 6 include the following:

  • Dial-up Networking configuration item.

  • WiFi configuration item does not support the WiFi connection to the Internet with ad hoc networking with shared authentication and encryption disabled.

The unsigned .cab file policy on Windows Mobile 5 and newer mobile devices can be managed using the Security Policy configuration item. When .cab files are distributed using Configuration Manager 2007, the prompt for unsigned .cab files is suppressed even if the client .cab signing policy is set to prompt. If a .cab file is installed by the user outside of Configuration Manager 2007, the .cab signing policy will function as expected.

Solution

Sign .cab files distributed by Configuration Manager 2007 for installation on mobile devices.

Error conditions reported by mobile device clients might be displayed using standard Windows error codes, without a description of the error. Or they might use error codes that are specific to Configuration Manager 2007.

Solution

Use the following references to find the error description associated with a specific error code displayed in the reports:

For more information, see Troubleshooting Mobile Device Management Using Custom Error Codes.

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