Export (0) Print
Expand All
27 out of 35 rated this helpful - Rate this topic

Release Notes: Important Issues in Windows Server 2012 R2 Preview

Published: June 24, 2013

Updated: June 24, 2013

Applies To: Windows Server 2012 R2



These release notes address the most critical issues and information about the Windows Server® 2012 R2 operating system. For information about by-design changes, new features, and fixes in this release, see documentation and announcements from the specific feature teams. For information about important steps to take before installing this release, including issues that you may need to work around, see “System Requirements and Installation Options for Windows Server 2012 R2 Preview,” a document available at the same location as this document. Unless otherwise specified, these notes apply to all editions and installation options of the Windows Server 2012 R2.

This document is continuously updated; as critical issues requiring a workaround are discovered, they are added.

  • This issue only affects checked builds of Windows Server 2012 and Windows® 8.1.

    During Setup, an application dialog box appears referencing application error 0xc0000420 in TabTip.exe. You can safely click OK and continue with Setup.

  • If you attempt to migrate an existing Windows Server 2008 R2 or earlier server that is running any of the following server roles or features to this release, migration will fail with a “DLL not found” exception:

    • DHCP Server

    • File and storage services (including File Server Resource Manager and associated tools, DFS Namespaces, iSCSI, and Server Message Block shares)

    • BranchCache for Network Files

    • Remote Access

    • Wow64

  • If you attempt to migrate an existing Windows Server 2012 server running the DHCP Server role to this release, migration will fail.

There is no workaround for either of the migration issues at this time; do not decommission affected older servers until migration can be accomplished.

  • If you attempt to run Sysprep.exe to create a WIM image more than one hour after the first user has logged on to the newly installed operating system, Sysprep.exe will fail. A scheduled maintenance task that recovers disk space by removing unused features is the cause.

    To avoid this, disable the maintenance task immediately after completing Setup. You can disable the task with this command:

    Schtasks.exe /change /disable /tn "\Microsoft\Windows\AppxDeploymentClient\Pre-staged app cleanup"

  • If you deploy an image using Microsoft Deployment Toolkit 2013 or Unattend.exe and include CopyProfile=true in the answer file, the deployment will fail with a “location is not available” error or each new login attempt will create a new temporary user account profile.

    To avoid this, do not use CopyProfile=true in the answer file. There is no other workaround at this time.

This issue only affects Windows Server 2012 R2 Essentials.

In the Russian-language version of this release, enabling quotas on server folders with the Essentials Dashboard is not functional. Instead, use Server Manager, install the File Server Resource Manager role and File Server Resource Manager Tools feature, and then set the folder quota with File Server Resource Manager.

You cannot log into Outlook Web App (OWA) from Internet Explorer 11. To avoid this, either delete the browser history or open an inPrivate session, and then log into OWA.

  • Services that use Transport Layer Security (TLS) to connect to domain controllers (such as Internet Explorer) will fail to connect.

    To avoid this, disable support for TLS session tickets by using Regedit32.exe (or a script or command) to set the value of the HKLM\System\CurrentControlSet\Control\SecurityProviders\SCHANNEL\EnableSessionTicket registry key to 0x0002.

    Alternately, you can configure the service to run as a domain user account or a group-managed service account.

  • RC4 is no longer enabled by default for TLS. Applications (such as Internet Explorer) might fail to connect if they depend on RC4. You can enable RC4 support by configuring these registry keys with the following REG command:

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers]

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\RC4 128/128]"Enabled"=dword:ffffffff

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\RC4 40/128]"Enabled"=dword:ffffffff

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\RC4 56/128]"Enabled"=dword:ffffffff

  • When credential delegation is disabled, it no longer caches credentials. If you enable the “Allow delegating default credentials” policy, users who are currently signed on will not have credentials cached. If they then use an application that delegates default credentials, the application will still prompt for credentials. After a user has either unlocked the desktop or signed off, applications will no longer prompt for credentials.

  • The Digest client does not cache credentials for domain members. Applications will prompt for credentials. You can enable caching in Digest clients with the following REG command:

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\WDigest\] “UseLogonCredential” =dword:1

If you use Server Manager to format an existing disk volume on a server that is not part of a failover cluster, Server Manager will unexpectedly stop or become unresponsive. To avoid this, delete the volume, and then recreate it using the New Volume wizard. Alternately, you can format the volume using Disk Management.

This issue affects Windows Server 2012 R2 Essentials and the Essentials Experience server role.

The integration module for Windows Azure Backup is not functional in this release. There is no workaround at this time.

This issue affects Windows Server 2012 R2 Essentials and the Essentials Experience server role.

Installation of the Windows Server Essentials Connector on a client computer will fail unless the client computer has access to the internet. Ensure that the client computer has internet access, or download the Windows Server Essentials Connector from MS Connect.

This document is provided “as-is”. Information and views expressed in this document, including URL and other Internet Web site references, may change without notice.

This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes.

©2013 Microsoft Corporation. All rights reserved.

Microsoft, Active Directory, Hyper-V, MS-DOS, Windows, Windows NT, Windows Server, and Windows Vista are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

This product contains graphics filter software; this software is based in part on the work of the Independent JPEG Group.

All other trademarks are property of their respective owners.

5.0

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

Show:
© 2014 Microsoft. All rights reserved.