Release Notes for System Center 2012 R2 Configuration Manager Preview
Applies To: System Center 2012 R2 Configuration Manager
To search these release notes, press Ctrl+F.
Read these release notes thoroughly before you install System Center 2012 R2 Configuration Manager Preview.
These release notes contain information that is required to successfully install System Center 2012 R2 Configuration Manager Preview and contain information that is not available in the product documentation. This prerelease version is not supported in a production environment and is for testing only.
If there is a discrepancy between these release notes and other Configuration Manager documentation, the most recent version should be considered authoritative.
This prerelease version supports all site system roles on Windows Server 2012 R2 Preview, and the System Center 2012 R2 Configuration Manager Preview client on Windows 8.1 Preview.
New mobile device capabilities require integration with the next release of Windows Intune, which is not available for System Center 2012 R2 Configuration Manager Preview.
For additional supported configuration information, see Supported Configurations for Configuration Manager.
This prerelease version does not support an upgrade from previous versions of System Center 2012 Configuration Manager. Install this prerelease version as a new installation of Configuration Manager.
In addition, Configuration Manager does not support the import of objects between different versions of Configuration Manager.
If you want to provide feedback, make a suggestion, or report an issue with System Center 2012 R2 Configuration Manager Preview, use the Microsoft Connect site.
The Documentation Library for System Center 2012 Configuration Manager is updated with some prerelease information for System Center 2012 R2 Configuration Manager. If you have feedback about the documentation, send an email message to SMSDocs@Microsoft.com.
Known Issues with System Center 2012 R2 Configuration Manager Preview
This section provides the most up-to-date information about issues with System Center 2012 R2 Configuration Manager Preview. These issues do not appear in the product documentation, and, in some cases, might contradict existing product documentation. Whenever possible, these issues will be addressed in later releases.
The Microsoft Pre-Release Software License Terms Contain an Incorrect Link to the System Center 2012 R2 Privacy Statement
Paragraph 3(a) within the Microsoft Pre-Release Software License Terms contains an incorrect link to the System Center 2012 R2 Privacy Statement.
WORKAROUND You can view the System Center 2012 R2 Privacy Statement by using the following URL: http://go.microsoft.com/?LinkID=9829374
Some PowerShell Cmdlets Require a 32-bit PowerShell Environment
Some Configuration Manager PowerShell cmdlets report an error when they are run from a 64-bit PowerShell environment. For example, the following cmdlets require access to 32-bit resources and must be run from a 32-bit environment:
When this error occurs, you might see the following messages in the PowerShell environment:
An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0x8007000B)
Could not find the ConfigMgr UI installation directory
Could not load file or assembly 'Microsoft.ConfigurationManagement, Version=22.214.171.124, Culture=neutral, ...'
WORKAROUND Start the 32-bit version of Windows PowerShell. Then, import the Configuration Manager PowerShell module. By default, the PowerShell module is installed with the Configuration Manager console. Import the module by typing the following two commands in the PowerShell command prompt:
cd 'C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\bin'
Client Source Files for Mac Computers Are Not on the Download Center
The documentation contains instructions to download the Mac OS X client installation files from the Download Center. The client source files for System Center 2012 R2 Configuration Manager Preview can be found from the following location: Microsoft System Center 2012 R2 Configuration Manager - Clients for Additional Operating Systems.
Reassigning an Internet-based Client Fails
If a client has been operating as an Internet-based client and you reassign the client to another site, this site reassignment does not work and the client becomes unmanaged.
WORKAROUND None. In this prerelease version, do not reassign an Internet-based client.
Some Mobile Device Configuration Item Settings Do Not work for iOS 6.0
The following settings will not work for iOS 6.0 mobile device configuration items:
Enter a password to access the application store
User to accept untrusted TLS certificates
The Fraud Warning Setting for the Browser Setting Group Does Not Work on Windows 8.1 Preview
If you create a mobile device configuration item, select the Browser setting group and configure Fraud warning to be Prohibited, this setting does not take effect on a device running Windows 8.1 Preview. In addition, reports in Configuration Manager incorrectly report as compliant for this setting if the computer runs Windows 8.1 Preview.
You can also configure this option by selecting Configure additional settings that are not in the default setting groups, add the Fraud Warning setting and configure this setting to be prohibited. This setting is configured as prohibited when Fraud warning is Equals and the following values is False, and Remediate noncompliant rules when supported is enabled.
Windows 8.1 Computers Cannot Connect to Vendor VPNs
If you deploy a VPN profile for Juniper Pulse, Dell SonicWALL Mobile Connect, F5 Edge Client, or Check Point Mobile VPN to a Windows 8.1 Preview client, the client will not be able to connect to these VPN solutions.
Incorrect Location Specified in the Policy Module Setup Wizard
The Certificate Registration Point Certificate page of the Configuration Manager Policy Module Setup wizard incorrectly says that the certificate file of the server authentication certificate is saved to the site system server that hosts the certificate registration point. The correct location is on the primary site server.
WORKAROUND If the certificate registration point is not installed on the same computer as the site server, locate the certificate file from the site server, as documented in Configuring Certificate Profiles in Configuration Manager.
User Certificate Enrollment by Using SCEP Certificate Profiles Fails
If you deploy user certificates by using a SCEP certificate profile, the certificate enrollment request fails.
WORKAROUND Create the following DWORD registry key with a value of 1 to the site system server that hosts the certificate registration point:
Trusted CA Certificates on Windows Devices Fail to Install to the User Certificate Store
If you deploy a trusted CA certificate profile to the User certificate store on Windows devices, the certificate does not install.
WORKAROUND Install trusted CA certificates to the Computer certificate store.
User Certificates Fail to Install for Low-Rights Users
If you deploy a SCEP certificate profile to a user on a Windows-based computer and that user is not a local administrator on that device, the user certificate will not install.
Retiring a Windows Device Does Not Remove User Certificates
If you retire a Windows device by using the Configuration Manager console, user certificates on the device are not removed if they were enrolled by using a SCEP settings certificate profile. Any computer certificates are removed.
Windows 8.1 ADK does not support Windows Server 2008
The Windows Assessment and Deployment Kit (ADK) for Windows 8.1 Preview does not support the installation of the required components (Deployment Tools, Windows PE, and the User State Migration Tool) on computers running Windows Server 2008 SP2.
WORKAROUND Upgrade the Configuration Manager servers running the site server and the SMS Provider so that they run at least Windows Server 2008 R2, and then install the Windows 8.1 ADK
Virtual Hard Disk Creation Fails on an Edition of Windows Server 2012 R2 That Has a Double-byte Character Set
If you run the System Center 2012 R2 Configuration Manager console on a localized edition of Windows Server 2012 R2 with a double-byte character set, such as Chinese or Japanese, you cannot create a virtual hard disk (VHD). The DeployToVhd.log displays errors similar to the following:
Failed to run: PowerShell.exe Set-ExecutionPolicy RemoteSigned -Scope Process -Force; Import-Module Hyper-V; Add-VMHardDiskDrive -VMName '20130610-160418-AUJG8F55XUIDH5BP' Path 'C:\Users\ADMINI~1.R29\AppData\Local\Temp\20130610-160418-AUJG8F55XUIDH5BP.vhd'. Program returned 00000001
wmain failed; 0x80070001
WORKAROUND To create a virtual hard disk, run the Configuration Manager console on an operating system version of Windows Server 2012 R2 that does not use a double-byte characters set.
Error Microsoft.Reporting.WinForms.ReportServerException when you run any report
When the account that runs Reporting Services for reports does not have the default permissions for Windows Authorization Access Group, reports will not run and display the following error:
Microsoft.Reporting.WinForms.ReportServerException. The DefaultValue expression for the report parameter ‘UserSIDs’ contains an error: The user name or password is incorrect.
WORKAROUND Add the account that runs Reporting Services to the domain local security group Windows Authorization Access Group, and ensure that this group has the Read tokenGroupsGlobalAndUniversal permission set to Allow.
For additional resources, see Information and Support for Configuration Manager.
Tip: Use this query to find online documentation in the TechNet Library for System Center 2012 Configuration Manager. For instructions and examples, see Search the Configuration Manager Documentation Library.