Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

FIX: Mobile devices aren't listed in System Center Configuration Manager


View products that this article applies to.

Symptoms

In a Microsoft System Center Configuration Manager environment in which the Microsoft Exchange Server connector is configured for use with Microsoft Exchange Server 2013, mobile devices aren't listed as expected in the All Mobile Devices node of the administrator console. Additionally, errors that resemble the following are recorded in the EasDisc.log file on the Configuration Manager site server:

ERROR: [MANAGED] Invoking cmdlet Get-Recipient failed. Exception: System.Management.Automation.RemoteException: Cannot bind parameter 'Filter' to the target. Exception setting "Filter": "The value "$true" could not be converted to type System.Boolean….
STATMSG: ID=8817 SEV=W LEV=M SOURCE="SMS Server" COMP="SMS_EXCHANGE_CONNECTOR" …
ERROR: [MANAGED] Exception: Cannot bind parameter 'Filter' to the target. Exception setting "Filter": "The value "$true" could not be converted to type System.Boolean."
ERROR: Failed to check status of discovery thread of managed COM. error = Unknown error 0x80131501

Note
This log entry is truncated for readability.

This issue applies to the following versions of System Center Configuration Manager:
  • Microsoft System Center Configuration Manager version 1511
  • Microsoft System Center 2012 Configuration Manager Service Pack 2
  • Microsoft System Center 2012 R2 Configuration Manager Service Pack 1

↑ Back to the top


Resolution

Hotfix information for System Center Configuration Manager version 1511
This hotfix is available for installation in the Updates and Servicing node of the Configuration Manager console under the following condition:

  • The Exchange Server connector is installed and configured for use with an on-premises version of Microsoft Exchange Server.
Note This issue affects only on-premises versions of Exchange Server 2013. However, it is also applicable if Exchange Server 2010 on-premises is used with the connector.

If the service connection point is in offline mode, and if the Exchange Server connector is enabled after the update is imported, you have to follow these steps so that the update is listed in the Configuration Manager console:

  1. Close the Configuration Manager console.
  2. Delete the following file:
    <SMSROOT>\EasySetupPayload\offline\10BE05BB-BE45-4D65-8C3D-D12BAC995233.cab
  3. Re-import the update by using the service connection tool.

    For more information, see the following Microsoft TechNet article:

Prerequisites

To apply this hotfix, you must have System Center Configuration Manager version 1511 installed.

Restart information

You don't have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any 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 item in Control Panel.

System Center Configuration Manager version 1511
File nameFile versionFile sizeDateTimePlatform
Microsoft.configurationmanagement.exchangeconnector.dll5.0.8325.1102101,04024-Nov-201501:10x86

Hotfix information for System Center 2012 Configuration Manager and System Center 2012 R2 Configuration Manager
A supported hotfix is available from Microsoft Support. 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 aren't 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 don't qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, go to the following Microsoft website: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you don't see your language, it is because a hotfix isn't available for that language.

Prerequisites

To apply this hotfix, you must have Cumulative Update 2 for System Center 2012 Configuration Manager Service Pack 2 and System Center 2012 R2 Configuration Manager Service Pack 1.

Restart information

You don't have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any 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 item in Control Panel.

System Center 2012 Configuration Manager and System Center 2012 R2 Configuration Manager
File nameFile versionFile sizeDateTimePlatform
Microsoft.configurationmanagement.exchangeconnector.dll5.0.8239.130698,99205-Oct-201501:30x86

↑ Back to the top


Status

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

↑ Back to the top


References

See the following topics on the Microsoft Technet website for more information:


Learn about the terminology that Microsoft uses to describe software updates.

↑ Back to the top


Keywords: SCCM, kb, kbexpertiseinter, kbqfe, kbfix, kbautohotfix, ConfigMgrCB, kbhotfixserver

↑ Back to the top

Article Info
Article ID : 3122637
Revision : 3
Created on : 9/19/2017
Published on : 9/19/2017
Exists online : False
Views : 396