Installing this Beta Release of Windows Server 2008 R2

Contents

This document provides information about installing this beta release of the Windows Server® 2008 R2 operating system, including any known issues that you may need to work around before starting an installation. It also provides information that you can use to troubleshoot problems that may occur during the installation.

Setup works in several stages. You will be prompted for some basic information, and then Setup will copy files and restart the computer. Setup concludes by presenting a menu for Initial Configuration Tasks, which you can use to configure your server for your specific needs.

Preinstallation information

System requirements

The following are estimated system requirements for Windows Server 2008 R2. If your computer has less than the "minimum" requirements, you will not be able to install this product correctly. Actual requirements will vary based on your system configuration and the applications and features you install.

Processor

Processor performance depends not only on the clock frequency of the processor, but also on the number of processor cores and the size of the processor cache. The following are the processor requirements for this product:

Disk space requirements

The following are the approximate estimated disk space requirements for the system partition. Itanium-based and x64-based operating systems will vary from these estimates. Additional disk space may be required if you install the system over a network.

Minimum: 10 GB

Recommended: 40 GB or more

Note

Computers with more than 16 GB of RAM will require more disk space for paging, hibernation, and dump files.

Other requirements

DVD-ROM drive

Super VGA (800 x 600) or higher-resolution monitor

Keyboard and Microsoft® mouse (or other compatible pointing device)

Important information for x64-based operating systems

Ensure that you have updated and digitally signed kernel-mode drivers for x64-based versions of Windows Server 2008. (These include the 64-bit versions of Windows Server 2008 except for Windows Server 2008 for Itanium-Based Systems.)

If you install a Plug and Play device, you may receive a warning if the driver is not digitally signed. If you install an application that contains a driver that is not digitally signed, you will not receive an error during Setup. In both cases, Windows Server 2008 R2 will not load the unsigned driver.

If you are not sure whether the driver is digitally signed, or if you are unable to boot into your computer after the installation, use the following procedure to disable the driver signature requirement. This procedure enables your computer to start correctly, and the unsigned driver will load successfully.

Before you start Setup

Before you install this preliminary release of Windows Server 2008 R2, follow the steps in this section to prepare for the installation.

Disconnect UPS devices. If you have an uninterruptible power supply (UPS) connected to your destination computer, disconnect the serial cable before running Setup. Setup automatically attempts to detect devices that are connected to serial ports, and UPS equipment can cause issues with the detection process.

Back up your servers. Your backup should include all data and configuration information that is necessary for the computer to function. It is important to perform a backup of configuration information for servers, especially those that provide network infrastructure, such as Dynamic Host Configuration Protocol (DHCP) servers. When you perform the backup, be sure to include the boot and system partitions and the system state data. Another way to back up configuration information is to create a backup set for Automated System Recovery.

Disable your virus protection software. Virus protection software can interfere with installation. For example, it can make installation much slower by scanning every file that is copied locally to your computer.

Run the Windows Memory Diagnostic tool. You should run this tool to test the RAM on your computer. To use the Windows Memory Diagnostic tool, follow the instructions in the Windows Memory Diagnostic Users Guide (http://go.microsoft.com/fwlink/?LinkID=50362).

Provide mass storage drivers. If your manufacturer has supplied a separate driver file, save the file to a floppy disk, CD, DVD, or Universal Serial Bus (USB) flash drive in either the root directory of the media or in one of the following folders: amd64 for x64-based computers, i386 for 32-bit computers, or ia64 for Itanium-based computers. To provide the driver during Setup, on the disk selection page, click Load Driver (or press F6). You can browse to locate the driver or have Setup search the media.

Be aware that Windows Firewall is on by default. Server applications that must receive unsolicited inbound connections will fail until you create inbound firewall rules to allow them. Check with your application vendor to determine which ports and protocols are necessary for the application to run correctly.

To do this, use the following procedures. If you are performing an unattended installation, perform this step before you install the operating system. Otherwise, you will need to do this after you run Setup and before you install Active Directory Domain Services.

To prepare a forest

Log on to the schema master as a member of the Enterprise Admins, Schema Admins, or Domain Admins group.

Copy the contents of the \support\adprep folder (note the new location) from the Windows Server 2008 R2 installation DVD to the schema master role holder.

Open a Command Prompt window, navigate to the Adprep folder, and run adprep /forestprep.

If you plan to install a read-only domain controller (RODC), run adprep /rodcprep.

Allow the operation to complete and the changes to replicate before performing the next procedure.

To prepare a domain

Perform this procedure for each domain where you want to install a domain controller that runs Windows Server 2008 R2.

Log on to the infrastructure master as a member of the Domain Admins group.

Copy the contents of the \support\adprep folder (note the new location) from the installation DVD to the infrastructure master role holder.

Open a Command Prompt window, navigate to the Adprep folder, and run adprep /domainprep /gpprep.

Allow the operation to complete and the changes to replicate.

After completing these steps, you can add domain controllers that are running Windows Server 2008 R2 to the domains you have prepared.

The adprep command extends the schema, updates default security descriptors of selected objects, and adds new directory objects as required by some applications. For more information about adprep, see http://go.microsoft.com/fwlink/?linkid=50439.

Known issues

If you attempt to install this release from a device that this release does not include drivers for, installation will fail with the error “Windows could not collect information for <operating system image> since the specified file [install.wim] does not exist.”

To work around this, do any one of the following:

Install this release from a network.

Install this release from another bootable drive or storage controller that the release does include a driver for.

Configure the storage controller to use a driver that the release includes.

Add the driver for your existing device to a new Install.wim file and create a new installation image. Then install this release from there.

Boot the computer into one of the following operating systems, and start the installer for this release. Then, in the Install Windows pane of the setup wizard, click Load Driver and navigate to the correct driver for your device. Proceed with the remainder of the installation.

Windows XP with Service Pack 2 or Windows XP with Service Pack 3

Windows Server 2003 R2

Windows Vista or Windows Vista with Service Pack 1

Windows Server 2008

If the first component of the DNS name of your domain exceeds 15 characters, promotion of servers running Windows Server 2008 R2 to domain controllers will fail and computers running Windows Server 2008 R2 and Windows 7 will not be able to join the domain.

Existing domain controllers will still function correctly and both client and server computers that are running other operating systems can still join the domain.

There is no workaround at this time, other than to rename the domain with a name comprising fewer than 15 characters.

Copyright

This document supports a preliminary release of a software product that may be changed substantially prior to final commercial release.

Information in this document, including URL and other Internet Web site references, is subject to change without notice and is provided for informational purposes only. The entire risk of the use or results from the use of this document remains with the user, and Microsoft Corporation makes no warranties, either express or implied. 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.