These release notes address the most critical issues and information about this beta release of the Windows Server® 2008 R2 operating system. For additional issues, refer to Things to Know About This Beta Release of Windows Server 2008 R2 (http://go.microsoft.com/fwlink/?LinkID=139367). For information about important steps to take before installing this release, including issues that you may need to work around, refer to Installing This Beta Release of Windows Server 2008 R2 (http://go.microsoft.com/fwlink/?LinkID=139331). Both documents are available at the same locations as this document. Unless otherwise specified, these notes apply to all editions and installation options of Windows Server 2008 R2.
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.
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.
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 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:
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.
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.
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:
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:
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.