Microsoft® Narrator does not read information from the command line properly. This issue may also affect non-Microsoft screen reader applications.

To correct this, always run the command prompt with administrative privileges.

In some circumstances, promoting a server to the domain controller role using Dcpromo.exe may fail. The operation fails and you will find Error 54 “Internal error: An Active Directory Domain Services error has occurred” in the Dcpromoui.log file.

If this occurs, rerun Dcpromo.exe.

BitLocker Drive Encryption is not supported on drives that use the Extended File Allocation Table (exFAT) file system. Use BitLocker Drive Encryption with drives formatted with FAT or FAT32 instead.

This issue affects full installations of Windows Server 2008 R2.

The watermark that should appear on the desktop and displays the product name, build timestamp, and “evaluation” status is not present.

To correct this, apply any desktop background.

This issue affects Windows Server 2008 R2 Enterprise, Windows Server 2008 R2 Enterprise without Hyper-V™, Windows Server 2008 R2 Datacenter, and Windows Server 2008 R2 Datacenter without Hyper-V.

Clients will not be able to communicate with a DirectAccess server using Teredo until Windows® Firewall is configured appropriately.

1. Click Start, click Administrative Tools, and then click Windows Firewall with Advanced Security.

2. In the left pane, click Inbound Rules.

3. Right-click File and Printer Sharing (Echo Request – ICMPv4-in) and select Enable Rule.

4. Right-click File and Printer Sharing (Echo Request – ICMPv6-in) and select Enable Rule.

5. In the left pane, click Outbound Rules.

6. Right-click File and Printer Sharing (Echo Request – ICMPv4-in) and select Enable Rule.

7. Right-click File and Printer Sharing (Echo Request – ICMPv6-in) and select Enable Rule.

8. Close the window.

This issue affects Windows Server 2008 R2 Standard, Windows Server 2008 R2 Enterprise, and Windows Server 2008 R2 Datacenter.

If you shut down a server that is a Failover Cluster node hosting a virtual machine, the virtual machine may not completely enter the saved state and will not subsequently resume in the correct state when you start it.

To avoid this, move any virtual machines hosted on a Failover Cluster node to other nodes before shutting down the node. Alternatively, you can manually shut down the virtual machine. You can do either of these actions either with the Failover Cluster Manager snap-in for Microsoft Management Console (MMC) or with Windows PowerShell™ cmdlets.

• If you migrate data between builds of Windows Server 2008 R2 that have File Server Resource Manager (FSRM) enabled, migration will fail. All FSRM report and classification jobs will fail and File Management tasks are not migrated.
  
  To avoid this, upgrade between Windows Server 2008 R2 builds. You should only migrate between servers running Windows Server 2008 or earlier to servers running Windows Server 2008 R2.
  
  If this has already occurred, uninstall FSRM and delete everything below the <sysvol>\System Volume Information\SRM directory. Then reinstall and reconfigure FSRM.
  
  
• If you run multiple report jobs (either scheduled or manual) in rapid succession (within about 10 minutes), the report service may unexpectedly quit.
  
  To avoid this, ensure that all report jobs are separated by at least 10 minutes. If this has already occurred, re-run the jobs.
  
  

• If you merge a differencing virtual hard disk (.vhd) to a parent virtual hard disk that is configured as read-only, the merge fails and the differencing virtual hard disk is deleted, with resulting loss of the data.
  
  To avoid this, ensure that the parent virtual hard disk is configured as a read/write disk before starting a merge operation.
  
  
• If you back up a virtual machine that is not connected to any virtual network, you will not be able to restore the virtual machine.
  
  To avoid this, review the virtual machine configuration and verify that all of the virtual network adapters are connected to a network.
  
  
• Live Migration or Quick Migration of a virtual machine between two nodes may fail unless the nodes are running on processors that support identical processor features.
  
  To check what processor a node is running, view the Processors item in Device Manager or use Regedit.exe to view the registry key HKEY_LOCAL_MACHINE\HARDWARE\DESCRIPTION\System\Central Processor\0.
  
  To get a list of reported processor features for the reported processor, refer to the appropriate vendor resources:
  
  
  • For AMD: (http://go.microsoft.com/fwlink/?LinkID=139368)
    
    
  • For Intel: (http://go.microsoft.com/fwlink/?LinkID=139369)
    
    

• If you attempt to print a PDF document from the browser using the Adobe Reader plug-in, the operation fails.
  
  To avoid this, save the PDF document to disk, and then open and print it using the stand-alone version of Adobe Reader, Adobe Acrobat, or any application capable of viewing and printing PDF files.
  
  
• Feeds (such as RSS or Atom) may not update properly in the background.
  
  To correct this, open a command prompt and run the following commands:
  
  msfeedssync disable
  
  for /f "tokens=3" %i in ('reg query hkcu\software\microsoft\feeds /v synctask') do schtasks /delete /tn "%i"(If you receive an error, you can safely ignore it and proceed to the next command.)
  
  reg delete hkcu\software\microsoft\feeds /v synctask
  
  msfeedssync enable
  
  You can then confirm that the issue has been fixed by running the following command and confirming a result of SUCCESS:
  
  for /f "tokens=3" %i in ('reg query hkcu\software\microsoft\feeds /v synctask') do schtasks /run /tn "%i"
  
  

When MP3 files are added (either manually or automatically) to either Windows Media Player or the Windows Media Center library, or if the file metadata is edited, several seconds of content may be permanently removed from the start of the file. This issue occurs when files contain thumbnails or other metadata of significant size before importing or editing them.

To avoid this, ensure that all MP3 files that can be accessed by a computer running Windows 7 (including those on removable media or shared network resources) are set to read-only. To do this, in Windows Explorer, find the files, right-click them, click the General tab, and then select the Read-only check box. Then back up all of the MP3 files prior to using Windows Media Player or Windows Media Center.

If some of your files have already been affected, you may be able to recover the data by using the Previous Versions feature. To do this, right-click the file name, click Properties, click the Previous Versions tab, and in the File Versions pane, select the most recent previous version.

• If you install a System Health Validator, you must restart the Network Policy Server service. Otherwise, no event or accounting logs will be available for the System Health Validator.
  
  
• In the Network Policy Server snap-in for MMC, if you view the Authentication/Accounting or Load Balancing properties of a Remote Radius Server template and then click OK, the snap-in will return an error and exit.
  
  To avoid this, create a new Remote Radius Server template and ensure that the Authentication/Accounting and Load Balancing settings are correct so that you can avoid editing them.
  
  

If you upgrade a server that has the Remote Desktop Services role installed to this beta release, the Remote Desktop Services Windows PowerShell cmdlets will return errors if you attempt to navigate to any path under RDS:\Workspace or RDS:\LicenseServer.

To correct this, start a command prompt that has administrative privileges and run both of the following commands:

Mofcomp %windir%\system32\tsallowm.mof

Mofcomp %windir%\system32\WBEM\TlsWmiProv.Mof

• Only 64-bit Connection Manager profiles are supported. These profiles will not work with 32-bit operating systems. To create a 32-bit profile on a 32-bit client computer, use the Connection Manager Administration Kit.
  
  
• Users connected through a virtual private network (VPN) that uses Internet Key Exchange version 2 will not be able to seamlessly switch the VPN connection from one network to another when they restart the computer. To correct this, the user should manually start the Routing and Remote Access (RRAS) Mobility Manager task before attempting to switch networks.
  
  
• The status of dial-up multilink VPN connections shown in the View All Networks window is not accurate. To check the status of dial-up multilink VPN connections, use the Network Connections control panel (Ncpa.cpl) instead.
  
  
• If you use international characters for authentication credentials in a username for Password Authentication Protocol (PAP), Challenge Handshake Authentication Protocol (CHAP), or Microsoft Challenge Handshake Authentication Protocol Version 2 (MS-CHAPv2), Network Policy Server (NPS) for Windows Server 2008 R2 is unable to authenticate the credentials. To avoid this issue, do not use international characters in a username for PAP, CHAP, or MS-CHAPv2. (Authentication works if you are using NPS for Windows Server 2008 R2).
  
  

This issue affects Server Core installations of Windows Web Server 2008 R2, Windows Server 2008 R2 Standard, Windows Server 2008 R2 Standard without Hyper-V, Windows Server 2008 R2 Enterprise, Windows Server 2008 R2 Enterprise without Hyper-V, Windows Server 2008 R2 Datacenter, and Windows Server 2008 R2 Datacenter without Hyper-V.

If you run applications that use managed code that communicates with the Internet with autoproxy detection, the operation will fail with an unhandled exception that mentions an error creating the Web proxy because Rasapi32.dll could not be found.

To correct this, open the Machine.config file (default location is C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG), locate the final closing </configuration> tag, and append the following:

<system.net> <defaultProxy> <proxy usesystemdefault="false" proxyaddress="<replace_with_proxy_address>" bypassonlocal="true" /> </defaultProxy> </system.net>

where <replace_with_proxy_address> is the address and port, if needed, of the proxy server used by the client application to access the .NET application. For example, proxyaddress="<http://proxyserver:80>".

If you upgrade to this beta release, any favorite iSCSI target connections are not retained and the configuration information is lost, so that disks connected with the iSCSI initiator are no longer accessible.

To avoid this, note the configuration of your iSCSI-connected disks before upgrading to this beta release, and then add the connections back to the iSCSI initiator when the upgrade is complete. If you use advanced connections with Challenge Handshake Authentication Protocol (CHAP) security, you should also note advanced setting information, including the CHAP secret.

If this has already occurred, reconnect to the iSCSI targets and mark them as favorite connections.

Allocation of child processes among the ideal nodes of Non-Uniform Memory Access (NUMA) nodes is not efficient, which results in performance degradation, increased latency, and cache misses, depending on the affected processes.

To correct this, edit the registry to change the inheritance of ideal NUMA nodes so that generated child processes are assigned the same IdealNode as their parent process. This setting is not system wide, but per-process.

1. Open Registry Editor (Regedit.exe).

2. Add the following registry key:

   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\<process_name>.exe

   where process_name is the name of the process you want to change the inheritance behavior for.

   Assign a DWORD value to this key with the name NodeOptions and data 0x00001000.

   Close Registry Editor and restart the computer.

The operating system will not prevent you from formatting the system partition. You will receive an error stating that the system partition cannot be formatted, but the operation will proceed anyway, with resulting data loss and the inability to boot the computer.

As you work with your operating system, ensure that you do not format the system partition. If this has already occurred, use the Windows Recovery Environment.

If you pause while sending data to a Remote Desktop Services session connected through Remote Desktop Gateway (RD Gateway) for longer than about 15 seconds, the connection may be dropped and you will receive an error stating “Your computer can't connect to the remote computer because an error occurred on the remote computer that you want to connect to.” You will also find a Timer_MinBytesPerSecond error logged in the file %windir%\system32\LogFiles\HTTPERR\httperr*.log.

To correct this, access the server running Terminal Services Gateway (TS Gateway) and set the HTTP.sys parameter Timer_MinBytesPerSecond to zero. You can do this using the user interface or with a script.

1. On the TS Gateway server, start the Internet Information Services (IIS) Manager.

2. In the Connections pane, click the server name. The Home pane for the server opens.

3. In the Management section of the Home pane, double-click Configuration Editor.

4. In the Section drop-down menu, open the system.applicationHost item and select the webLimits section.

5. Change the minBytesPerSecond value from the default of 240 to 0.

6. In the Actions pane, click Apply.

7. In the Connections pane, click the server name again. The Home pane for the server opens.

8. In the Actions pane, click Restart.

9. In a command prompt that has administrative privileges, type net start tsgateway and press ENTER.

1. Obtain the Appcmd script from (http://go.microsoft.com/fwlink/?LinkId=139380).

2. Use the Appcmd script to run this command:

   appcmd set config -section:webLimits /minBytesPerSecond:0

Systems which use XDDM drivers may completely stop responding in certain scenarios. The computer will not respond to CTRL+ALT+DELETE and you will have to cycle the power to restart the computer, with the attendant risk of loss of unsaved data.

Some activities which have been demonstrated to trigger this issue include, but are not limited to:

• Using Winsat.exe or using the Rate and improve your computer’s performance tool.
  
  
• Changing multimonitor configurations
  
  
• DVD or other video playback
  
  

To avoid this, do not use Windows XP Device Driver Model (XDDM) drivers, but find an appropriate Windows Display Driver Model (WDDM) driver instead. If your video chipset does not have a WDDM driver (such as the Intel 915), use a VGA driver or an graphics processing unit (GPU) that supports WDDM drivers.

If this issue occurs at setup, either avoid unattended setup or uninstall the XDDM driver and use a VGA driver until setup is complete.

Streaming Media Services technologies are not available in this beta release. This includes the Streaming Media Services server role.

You should not upgrade the operating system on a Windows Media server that is a critical component of your streaming network infrastructure.

This issue affects Server Core installations of Windows Server 2008 R2 Datacenter.

If you attempt to enable Windows PowerShell remoting using either Windows PowerShell cmdlets or the WS-Management provider, you will receive an error.

To avoid this, edit the registry by typing the following in the Windows PowerShell console:

remove-item HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\WSMAN\Plugin\Microsoft.PowerShell32

This document supports a preliminary release of a software product that may be changed substantially prior to final commercial release, and is the confidential and proprietary information of Microsoft Corporation. It is disclosed pursuant to a non-disclosure agreement between the recipient and Microsoft. This document is provided for informational purposes only and Microsoft makes no warranties, either express or implied, in this document. Information in this document, including URL and other Internet Web site references, is subject to change without notice. The entire risk of the use or the results from the use of this document remains with the user. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

© 2009 Microsoft Corporation. All rights reserved.

Microsoft, Windows, Windows Server, Windows Vista, Active Directory, Windows PowerShell, Windows Media, and Internet Explorer are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

All other trademarks are property of their respective owners.

1.0