Release Notes for System Center 2012 R2 Configuration Manager SP1

When you upgrade a central administration site from System Center 2012 R2 Configuration Manager with no service pack (R2) to System Center 2012 R2 Configuration Manager SP1 (R2 SP1), and your hierarchy contains more than 10,000 package and program deployments, replication between sites can fail.

The following two conditions must exist for this issue to apply:

1. You upgrade a hierarchy that includes a central administration site and that runs System Center 2012 R2 Configuration Manager to System Center 2012 R2 Configuration Manager SP1 by installing System Center 2012 Configuration Manager SP2.

2. Your hierarchy contains more than 10,000 package and program deployments.

If this problem is present after a hierarchy upgrades, the Offer Manager process on each child primary site no longer updates the Offermgr.log file.

To prevent this problem before you upgrade: Before upgrading your R2 site to R2 SP1, install cumulative update 5 for System Center 2012 R2 Configuration Manager. (Although the updates contained in cumulative update 5 are included with R2 SP1, installing the update prior to upgrading prevents this upgrade issue.)

If you have upgraded and replication has failed: To confirm this issue is present, run the following SQL query on the database of the child primary site and look for a result where one or more threads of the SMS_OFFER_MANAGER is identified as stuck:

select 
s.program_name,
SUBSTRING(convert(nvarchar(max), t.text), req.statement_start_offset/2, req.statement_end_offset/2) as currentstatement
,t.text
,req.* 
from sys.dm_exec_sessions s
inner join sys.dm_exec_requests req on s.Session_id=req.session_id
cross apply sys.dm_exec_sql_text(sql_handle) t
where s.program_name='SMS_OFFER_MANAGER'

After you confirm that replication failures are due to the SMS_OFFER_MANAGER threads being stuck, do the following:

1. Use SQL Management Studio to stop all SMS_OFFER_MANAGER threads that are stuck.

2. On the child primary site server, open Task Manager and on the Processes tab, right-click on the smsexec.exe process and select End task. (Stopping the SMS Executive service does not resolve this issue).

3. After you stop smsexec.exe, you can either manually restart the service, or wait for Site Component Manager to automatically restart the service within a few minutes.

For more information about the upgrade paths that include System Center 2012 R2 Configuration Manager SP1, see About the versions of System Center 2012 Configuration Manager.

When you distribute content to pull-distribution points that were created using Configuration Manager Powershell cmdlets or the System Center 2012 R2 Configuration Manager SDK, a false warning message results that indicates the content is not available on source distribution points.

Workaround: Confirm that the content is present on the source distribution points. If the content is present, you can ignore the warning.

If the following two conditions are met, Configuration Manager might be unable to use fast channel communications to process messages to block or unblock email access, delaying these actions for several minutes:

• The Microsoft Intune connector is installed on the site server

• The Configuration Manager installation path on the site server includes one or more spaces. For example, the default path on the sites server contains three spaces: C:\Program Files\Microsoft Configuration Manager

To identify this condition, you can find the following error message logged in in %ConfigMgrInstallPath%\Logs\dmpdownloader.log when you install the Microsoft Intune connector or when the DMP downloader thread restarts:

ERROR: Failed to load assembly for message downloader. Exception: System.IO.DirectoryNotFoundException: Could not find a part of the path 'I:\Program%20Files\Microsoft%20Configuration%20Manager\bin\x64\MessageHandlerConfig.xml'.~~   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)~~   at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)~~   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy)~~   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize)~~   at System.Xml.XmlUrlResolver.GetEntity(Uri absoluteUri, String role, Type ofObjectToReturn)~~   at System.Xml.XmlTextReaderImpl.OpenUrlDelegate(Object xmlResolver)~~   at System.Threading.CompressedStack.runTryCode(Object userData)~~   at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)~~   at System.Threading.CompressedStack.Run(CompressedStack compressedStack, ContextCallback callback, Object state)~~   at System.Xml.XmlTextReaderImpl.OpenUrl()~~   at System.Xml.XmlTextReaderImpl.Read()~~   at System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace)~~   at System.Xml.XmlDocument.Load(XmlReader reader)~~   at System.Xml.XmlDocument.Load(String filename)~~   at Microsoft.ConfigurationManager.DmpConnector.MessageDownload.MessageDownloader.LoadMessageHandlers()

Workaround: Uninstall the Microsoft Intune connector from the site server, and then reinstall the connector on a remote computer to a location that does not include spaces in the path.

On Windows 10 client computers the listing for System Center Endpoint Protection under Programs and Features of the Control Panel is wrong (4.7.213.0 for example). The version number for Windows Defender, the endpoint protection program in Windows 10, does not appear.

Workaround: To view the version of Windows Defender, hover over Help and select About in Windows Defender or view the version in the Configuration Manager administration console.