Release Notes for System Center 2012 Configuration Manager Service Pack 1
Updated: January 30, 2013
Applies To: System Center 2012 Configuration Manager SP1
To search these release notes, press Ctrl+F.
Read these release notes thoroughly before you install Microsoft System Center 2012 Configuration Manager Service Pack 1.
These release notes contain information that is required to successfully install System Center 2012 Configuration Manager Service Pack 1 (SP1). These release notes also contain information that is not available in the product documentation.
If there is a discrepancy between these release notes and other Configuration Manager documentation, the most recent version should be considered authoritative.
If you want to provide feedback, make a suggestion, or report an issue with System Center 2012 Configuration Manager SP1, use the Microsoft Connect site.
For supported configuration information, see Supported Configurations for Configuration Manager.
For documentation for System Center 2012 Configuration Manager SP1, see the Documentation Library for System Center 2012 Configuration Manager. If you have feedback about the documentation, send an email message to SMSDocs@Microsoft.com.
If you have installed a prerelease version of System Center 2012 Configuration Manager SP1, uninstall the prerelease version before you install System Center 2012 Configuration Manager SP1. We recommend that you also uninstall and reinstall the operating system after you uninstall earlier versions of Configuration Manager SP1 and before you install the release version of Configuration Manager SP1.
In addition, Configuration Manager does not support the import of objects between different versions of Configuration Manager.
If you have a release version of System Center 2012 Configuration Manager, you can upgrade this to System Center 2012 Configuration Manager SP1. For more information about the upgrade process and any interoperability considerations, see Planning to Upgrade System Center 2012 Configuration Manager and Interoperability between Different Versions of Configuration Manager.
Configuration Manager SP1 introduces several changes for deploying operating systems that are incompatible with earlier versions of Configuration Manager. For the best experience, we recommended that you delay operating system deployments until all site servers in your hierarchy are upgraded to Configuration Manager SP1. However, this is not always practical. For example, large hierarchies may require an extended time to upgrade all site servers. Therefore, review the interoperability considerations before you begin to deploy operating systems in a hierarchy that contains Configuration Manager SP1 sites and Configuration Manager sites without Service Pack 1. Those include the following:
Client installation package
When you install Configuration Manager SP1, the source for the default client installation package is automatically upgraded to the Configuration Manager SP1 version. All distribution points in the hierarchy are updated with this new client installation package, even if the distribution points are in sites that have not yet been upgraded to Configuration Manager SP1.
Clients that run Configuration Manager SP1 cannot be successfully assigned to sites that have not yet been upgraded to Configuration Manager SP1. If clients are mistakenly assigned in this scenario, site assignment is blocked at the management point.
When you upgrade the top-level site to Configuration Manager SP1, the default boot images (x86 and x64) are automatically updated to Windows ADK-based boot images, which use Windows PE 4. The files that are associated with the default boot images are updated with the Configuration Manager SP1 version of the files.
To prevent task sequences from failing, make sure that the version of the boot image corresponds to the version of the Configuration Manager client installation package that you configure in the task sequence. For example, a Windows AIK-based boot image that uses Windows PE 3 must correspond to the Configuration Manager with no service pack client installation package version. A Windows ADK-based boot image must correspond to the Configuration Manager SP1 client installation package version.
Avoid the use of dynamic media when your site hierarchy contains sites with different versions of Configuration Manager. Instead, use site-based media to contact a specific management point until all sites are upgraded to the same version of Configuration Manager.
You can import and use Windows AIK-based boot images only in a Configuration Manager site that does not have Service Pack 1 installed.
You can import and use Windows ADK-based boot images only in a Configuration Manager site that has Service Pack 1 installed.
Configuration Manager SP1 adds a deployment option to make task sequence deployments available to only media and PXE. This option is not recognized by Configuration Manager clients with no service pack. Therefore, those clients will still run any deployments that are configured to use this option as long as they are included in the collection that is targeted by the deployment. Avoid using this deployment option until you have upgraded all clients in your hierarchy to Configuration Manager SP1.
Failure to understand the implications of this interoperability consideration could result in data loss.
For more information, see Planning for Operating System Deployment Interoperability.
System Center 2012 Configuration Manager SP1 does not support an in-place upgrade from Configuration Manager 2007, but does support a side-by-side migration.
You can use System Center 2012 Configuration Manager SP1 to create migration jobs that migrate objects and content from Configuration Manager 2007 to System Center 2012 Configuration Manager SP1. Additionally, when you migrate Configuration Manager 2007 to System Center 2012 Configuration Manager SP1, you can upgrade a Configuration Manager 2007 distribution point to a System Center 2012 Configuration Manager SP1 distribution point. You can upgrade branch distribution points, distribution points on server shares, and standard distribution points from Configuration Manager 2007. You can also upgrade a Configuration Manager 2007 distribution point that is co-located on a secondary site server. This action uninstalls the secondary site and leaves the distribution point installed.
For information about migration, see the Migrating Hierarchies in System Center 2012 Configuration Manager guide.
The new wake-up proxy feature in Configuration Manager SP1 can help wake-up computers to perform management tasks. This feature lets those computers sleep or hibernate, which can help save costs. However, first evaluate this feature on an isolated and representative network infrastructure. Then, before you fully implement wake-up proxy, expand your test to use a group of computers on several subnets. Make sure that your testing includes all network configurations and network device types. If you have a separate team that is responsible for the network infrastructure and network services, notify and include this team during the testing period. For example, on a network that uses 802.1X network access control, wake-up proxy will not work and can disrupt the network service. In addition, wake-up proxy could cause some network monitoring tools to generate alerts when the tools detect the traffic to wake-up other computers. Review the information that is available about wake-up proxy to help you determine whether wake-up proxy is appropriate for your organization.
For more information about wake-up proxy, see the Planning How to Wake Up Clients section in the Planning for Communications in Configuration Manager topic.
This section provides the most up-to-date information about issues with System Center 2012 Configuration Manager SP1. These issues do not appear in the product documentation, and, in some cases, might contradict existing product documentation. Whenever it is possible, these issues will be addressed in later releases.
When you migrate a Configuration Manager 2007 configuration baseline to System Center 2012 Configuration Manager SP1, the hash of the configuration baseline digest is changed but the version number is not. Because the hash has changed, Configuration Manager queues a request to delete the existing configuration baseline and then downloads the modified configuration baseline. If the client computer or the client service (ccmexec) restarts before completing the delete request, the client does not download the new configuration baseline because the version number is the same as the one that currently exists.
In this scenario, you see error 87d00315 (The CI version info data is not available) on the Deployment tab in the Monitoring workspace.
WORKAROUND After the configuration baseline is migrated, modify it, which automatically increments the version number. For example, make a change to the description of the configuration baseline.
If the Configuration Manager SP1 client does not install on 64-bit computers, check to see whether the following error message is logged in the CCMSetup.log file:
Couldn't verify 'C:\WINDOWS\ccmsetup\MicrosoftPolicyPlatformSetup.msi' authenticode signature. Return code 0x800b0101
WORKAROUND Refer to the KB article 2801987.
When you enable a software update-based client deployment, the Configuration Manager client does not publish to the software update point. The following error is logged in the WCM.log file:
ERROR: Failed to publish sms client to WSUS, error = 0x80131622
WORKAROUND Download the following software update, and then install it on all site system servers that run the software update point site system role: Update for Windows Server Update Services (WSUS) 3.0 Service Pack 2 for x64-based Systems (KB2530678).
For more information about this software update, see System Center Update Publisher does not publish customized updates to a computer if WSUS 3.0 SP2 and the .NET Framework 4 are installed.
When a virtual application is deployed to a computer, the installation fails and the App-V client records Event 1008 in the Windows Applications and Services Logs, Microsoft-App-V-Client/Admin log file.
This error is typically caused when the same application has recently been uninstalled, and requires that the computer is restarted, because installation files are in use. Until the computer is restarted, you cannot reinstall the application.
WORKAROUND Restart the computer and then reinstall the application.
When you run the report named Roaming User Profiles Health Report, the report fails to run and displays the error Microsoft.Reporting.WinForms.ReportServerException.
WORKAROUND Perform the following procedure.
In the Configuration Manager console, right-click the report, Roaming User Profiles Health Report, and then click Edit.
In Report Builder, select DataSet0, and then click Edit.
In the Dataset Properties page, right-click the query and then click Select All.
Replace the query that you selected with the following query:
declare @UserSID as nvarchar(max) if(@UserName is NULL OR @UserName= '') set @UserSID = '' else set @UserSID = (select top 1 UserSID from fn_rbac_Users(@UserSIDs) where FullName = @UserName) declare @MachineID as int if(@Machine is NULL OR @Machine= '') set @MachineID = '' else set @MachineID = (select ResourceID from fn_rbac_R_System_Valid(@UserSIDs) where Netbios_Name0 = @Machine) select users.FullName as UserName, machines.Netbios_Name0 as DeviceName,case when st.HealthState = 1 then 'Warning' else 'Error' end as HealthState from fn_rbac_UserHealthProfileState(@UserSIDs) st join fn_rbac_Users(@UserSIDs) users on users.UserSID=st.UserSID join fn_rbac_R_System_Valid(@UserSIDs) machines on machines.ResourceID = st.ItemKey where users.UserSID = @UserSID and (machines.ResourceID = @MachineID or @Machine='') and st.HealthState = @HealthStateID
Click OK to close the Dataset Properties page, and then click OK to close the Define Query Parameters dialog box.
Close Report Builder and save your changes.
Run the report again.