When you run Microsoft System Center 2012 R2 Configuration Manager Service Pack 1 or System Center 2012 Configuration Manager Service Pack 2 on a server, you may experience the following performance issue or race condition:
- Performance issue
After Conditional Access is enabled and deployed, and devices are enrolled and compliant with the compliance policies that are deployed, performance tests reveal up to a 10-minute delay to unblock devices so that they start to receive email messages. The unblocking of devices occurs when compliance messages are received through a fast channel. This processing had dependencies that caused delays.
This update removes the dependencies on data and obtains this data from the fast compliance messages instead. This provides significant improvement in unblocking time. The unblocking time after the fix is typically less than 1 minute.
- Race condition
If you set up on-premises Conditional Access during the Exchange Connector's full/delta sync, a race condition may occur in a rare scenario. This prevents the Conditional Access Policy from taking effect.
This issue occurs because hybrid conditional access may not be enabled during a full sync of the System Center Configuration Manager Exchange Connector. During the full sync, a shared SQL connection can sometimes prevent the Conditional Access Policy from writing against SQL.
This update locks the SQL connection during the enabling of Conditional Access.
This issue occurs because hybrid conditional access cannot be enabled during a full sync of the System Center Configuration Manager Exchange Connector. During the full sync, a shared SQL connection prevents the conditional access policy from writing against SQL.
Hotfix informationA 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, go to the following Microsoft website: 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.
PrerequisitesTo apply this hotfix, you must have one of the following installed:
- System Center 2012 R2 Configuration Manager Service Pack 1
- Cumulative Update 1 for System Center 2012 R2 Configuration Manager Service Pack 1
- System Center 2012 Configuration Manager Service Pack 2
- Cumulative Update 1 for System Center 2012 Configuration Manager Service Pack 2
Restart informationYou do not have to restart the computer after you apply this hotfix.
Note We recommend that you close Configuration Manager Administration Console before you install this hotfix package.
Hotfix replacement informationThis hotfix does not replace any previously released hotfix.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Article ID: 3079897 - Last Review: Aug 17, 2015 - Revision: 1
Microsoft System Center 2012 R2 Configuration Manager Service Pack 1, Microsoft System Center 2012 Configuration Manager Service Pack 2