• If you place the Active Directory® database and log files in the root directory of a disk other than the disk that contains %systemroot%, a Stop error will result. You will also receive a Stop error if you place these files on an Internet SCSI (iSCSI) drive that is not available as a boot device.
  
  To avoid this, ensure that the Active Directory database and log files are in a volume other than the root volume of a local, nonremovable drive.
  
  Some iSCSI devices incorrectly report that they are local drives even when they are not. If this occurs, contact the drive vendor to determine if the hardware can be configured as a boot device. If the hardware cannot be configured as a boot device, perform the following steps.
  
  

To move the Active Directory database and log files

1. Restart the computer and enter the Directory Services Restore Mode by pressing F8 while the computer starts.

2. Move the Active Directory database and log files to a subdirectory at least one level beneath the root directory of a local drive.

3. Use Regedit.exe to find this registry key: HKLM\System\CurrentControlSet\Services\NTDS\Parameters

4. Change the DSA Database File value to the new path from Step 2. For example, x:\ntds.

5. Change the DSA Working Directory value to the new path from Step 2. For example, x:\ntds\logs.

• If your Active Directory Federation Services (AD FS)–enabled Web server running Windows Server 2008 Beta 3 is currently configured to host a Windows NT® token-based application, Windows NT token-based applications may fail after the upgrade to the release candidate is complete because a registry key value is not preserved.
  
  If this occurs, and you expected the value UseS4u in the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ifssvc\Parameters\ to be set, use Regedit.exe to verify that it is present and has the expected value (0 or 1).
  
  
• If your Active Directory Federation Services (AD FS)–enabled Web server that is running a non-English version of Windows Server 2003 R2 is currently configured with the AD FS Windows NT token-based Web Agent for any application, you may receive AD FS errors on the authentication page and AD FS may appear disabled after the upgrade to this release candidate is complete.
  
  To correct this, do either one of the following:
  
  
  • Re-enable AD FS for each application that is AD FS–enabled.
    
    
  • Open the %windir%\System32\inetsrv\config\applicationHost.config file with Notepad and replace each instance of AD FS Windows Token-Based Agent Extension with the correct description in the language of the operating system.
    
    

The Microsoft® Customer Experience Improvement Program (CEIP) is turned on by default. If you do not want to participate in the CEIP, you can change the settings.

To change CEIP settings

1. In Control Panel, click System and Maintenance, and then click Problem Reports and Solutions.

2. In the Task list, click Change settings.

3. Change the settings.

For information about the CEIP and the data that is transmitted to Microsoft, see http://go.microsoft.com/fwlink?linkid=52095. For the CEIP privacy statement, see http://go.microsoft.com/fwlink?linkid=52097.

The following events from the Shell Hardware Detection service are not valid and can be safely ignored:

• Event 7011 A time-out (30000 milliseconds) was reached while waiting for a transaction response from the ShellHWDetection service.
  
  
• Event 263 The service 'ShellHWDetection' may not have unregistered for device event notifications before it was stopped.
  
  

Hyper-V™ is available in this release of Windows Server 2008. (This role was identified in Server Manager as Windows Server® virtualization in the previous release.) To install this role, the computer must meet specific hardware and software requirements. For example, it is available only on a full installation of Windows Server 2008 Enterprise, for the "en-us" locale. For more information about configuration, usage considerations, and known issues, see the release notes for Windows Server virtualization (http://go.microsoft.com/fwlink/?LinkID=98821). For links to other information, see the Windows Server 2008 TechCenter (http://go.microsoft.com/fwlink/?LinkID=48557).

If your computer is running Microsoft .NET Framework 3.5 and Internet Information Services (IIS) is configured to host XOML files and you then install this release of Windows Server 2008, the files may not load properly if the application pool is in Integrated Mode. When you attempt to load the file, you will receive HTTP error 404.17.

To correct this, use the WFServicesReg.exe /c command to install handlers for Integrated Mode. This command is in the %windir%\Microsoft.NET\Framework\v3.5\ directory.

Note

On computers running 64-bit versions of Windows Server 2008, the command is in the %windir%\Microsoft.NET\Framework64\v3.5 directory.

• After you have installed SQL Server® 2005 Service Pack 2 (SP2) Reporting Services on Windows Server 2008, you must manually configure Reporting Services. For detailed steps, see article 936302 in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkID=88894).
  
  
• If you have installed a named instance of a cluster running SQL Server 2005 SP2 on a computer running Windows Server 2008, connections to this named instance from computers running Windows Vista or Windows Server 2008 may fail.
  
  To avoid this, use a TCP port or pipe name in the connection string, or configure the firewall so that all client applications are exceptions.
  
  For more information, see article 936302 in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=88894).
  
  

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

After you install Remote Server Administration Tools for Windows® Media Services on a computer running Windows Vista Ultimate, Windows Vista Enterprise, or Windows Vista Business, the Windows Media Services snap-in in may not be able to access a remote server running the Streaming Media Services role in Windows Server 2008. You might receive error codes 0x80070005, 0x800706BA, or both.

To correct this, create access permissions for Remote Server Administration Tools and enable an exception for Windows Management Instrumentation (WMI) in Windows Firewall on the server.

To create access permissions

1. On the server, open Component Services. (Click Start, click Run, and then type dcomcnfg.)

2. In the Component Services console tree, under Component Services, right-click the local computer (My Computer), and then click Properties.

3. On the COM Security tab, in the Access Permissions area, click Edit Limits.

4. In the Access Permission dialog box, on the Security tab, click ANONYMOUS LOGON.

5. In the Permissions for ANONYMOUS LOGON area, make sure that the Allow Remote Access check box is selected.

To enable the firewall exception

1. On the server, open Windows Firewall. (Click Start, click Run, and type firewall.cpl.)

2. In Windows Firewall Settings, on the Exceptions tab, select the Windows Management Instrumentation (WMI) check box.

These issues only affect Windows Server 2008 Datacenter, Windows Server 2008 Enterprise, and Windows Server 2008 Standard.

• Upgrading from the RC0 version of Windows Server 2008 to this release candidate is not supported for computers with Universal Description, Discovery, and Integration (UDDI) Services installed. To avoid this, perform a clean installation of this release candidate.
  
  
• If you install this release candidate on a computer running Windows Server 2003 that has Internet Information Services (IIS) but not UDDI Services installed, subsequent installation of UDDI Services will succeed, but UDDI Services will not function.
  
  To avoid this, complete the installation of this release candidate, and then reinstall IIS 7.0 before attempting to install UDDI Services.
  
  

When you have upgraded domain controllers to this release of Windows Server 2008, any client computers that only support the Data Encryption Standard (DES) will not be able to establish a secure channel with Netlogon. As a result, installations and attempts to join the domain will fail, including Windows Deployment Services installations of Windows Vista, Windows XP, Windows Server 2003, Windows 2000, and Active Directory Migration Tool. In addition, non-Microsoft Server Message Block (SMB) and network-attached storage devices that do not support the Message-Digest algorithm 5 (MD5) standard will also fail to establish a secure channel.

To avoid this, upgrade all client computers and domain controllers to a Windows operating system that is not earlier than Windows 2000. Contact the vendor of any non-Microsoft SMB and network-attached storage devices to obtain a version that supports MD5.

If you must support DES, enable support for Windows NT 4.0 cryptography. When editing the Group Policy object, under Computer Configuration, navigate to Administrative Templates, and then navigate to and enable the Allow cryptography algorithms compatible with Windows NT 4.0 policy setting.

This issue affects Windows Server 2008 Standard, Windows Server 2008 Enterprise, and Windows Web Server 2008.

Starting with this release, Windows SharePoint® Services 3.0 is not included as a component or role in Windows Server 2008. A version of Windows SharePoint Services for use with this release candidate will be available as a separate download at a later date from the Microsoft Download Center.

If you have Windows SharePoint Services installed on Windows Server 2008, installation of this release candidate will be blocked. To successfully install this release candidate, uninstall the Windows SharePoint Services role first.

If you need to preserve Windows SharePoint Services data for later use, such as when the download of Windows SharePoint Services is available, perform a Windows SharePoint Services server farm backup prior to installing this release candidate.

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.

© 2007 Microsoft Corporation. All rights reserved.

Microsoft, MS-DOS, Visual Basic, Visual Studio, Windows, Windows NT, Windows Server, Windows Vista, and Active Directory 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.

2.0