With the basic concepts of Windows virtualization covered so far in this chapter, and the background on sizing and planning for server capacity and storage, this section now focuses on the installation of the Microsoft Hyper-V Server role on a Windows Server 2008 system.
Installing Windows Server 2008 as the Host Operating System
The first step is to install an x64 version of Windows 2008 with Hyper-V as the host operating system. The step-by-step guidance for the installation of the Windows operating system is covered in Chapter 3, "Installing Windows Server 2008 and Server Core." Typically, the installation of a Windows 2008 server to run the Virtualization role is a new clean server installation, so the section in Chapter 3, "Installing a Clean Version of Windows Server 2008 Operating System," is the section to follow for getting Windows 2008 set up for virtualization.
Running Server Manager to Add the Hyper-V Role
After the base image of Windows 2008 has been installed, some basic initial tasks should be completed as noted in Chapter 3. The basic tasks are as follows:
- Change the server name to be a name that you want the virtual server to be.
- Configure the server to have a static IP address.
- Join the server to an Active Directory domain (assuming the server will be part of a managed Active Directory environment with centralized administration).
- Run Windows Update to confirm that all patches and updates have been installed and applied to the server.
After these basic tasks have been completed, the next step is to install the server virtualization software on the server and then add in the Hyper-V role to the server system. Because Windows virtualization did not ship with Windows 2008 at the time of the Windows 2008 product release, the Hyper-V role software needs to first be downloaded from Microsoft and installed on the server system.
A beta version of the Hyper-V software is included on the original Windows 2008 disc, and Microsoft will make the full version of Hyper-V (and subsequent updates) available for download from www.microsoft.com/downloads.
If you want to evaluate Hyper-V prior to its formal release, the virtualization code can be installed from the Windows 2008 disc. Or check on the Microsoft download site for the latest production version of Hyper-V to be installed on a server that will be placed into production.
After the code (beta or release) of Hyper-V has been installed on the system, do the following to add the server role to the system:
- Make sure to be logged on to the server with local Administrator or Domain Admin privileges.
- Click Start and then click Run.
- In the Run dialog box, type in ServerManager.msc, and click OK. This will start the Server Manager console if it is not already running on the system.
- Right-click on Roles in the left pane of the console, and select Add Roles, as shown in Figure 37.1.
- On the Select Server Roles page, select the Microsoft Hyper-V Server role, and click Next.
- On the Hyper-V page read the notes and information about the role, then click Next.
- On the Create Virtual Networks page, select the LAN adapters you want to have shared with guest sessions. Click Next to continue.
- On the Confirm Installation Selections page, review the selections made, and then click Install.
- On the Installation Results page, review the results, and click Close.
- When prompted to restart the server, click Yes.
- After the server restarts, log on to the server with local Administrator or Domain Admin privileges.
- After logging on, the installation and configuration will continue for a few more moments. When complete, the Installation Results page will be displayed. Review the results in the page and confirm that the Windows Hyper-V role has been installed successfully. Click Close.
Figure 37.1 Adding a role to the Server Manager console.
Use the following table of contents to navigate to chapter excerpts
|ABOUT THE BOOK:|
|Windows Server 2008 Unleashed covers the planning, design, prototype testing, implementation, migration, administration and support of a Windows 2008 and Active Directory environment, based on more than three and a half years of early-adopter experience in full production environments. This book addresses not only what is new in Windows 2008 compared with previous versions of the Windows Server product, but also what is different and how the similarities and differences affect an organization's migration to Windows 2008. Chapters are dedicated to the migration process from Windows 2000/2003 to Windows 2008, how to properly use Group Policies in Windows 2008, and tips and tricks on managing and administering a Windows 2008 environment. Purchase the book from InformIT.|
|ABOUT THE AUTHORS:|
|Rand Morimoto has been in the computer industry for more than 30 years and has authored, co-authored or been a contributing writer for dozens of bestselling books on Windows 2003, Exchange 2007, security, BizTalk Server, and remote and mobile computing. Michael Noel has been involved in the computer industry for nearly two decades and has significant real-world experience with enterprise information technology environments. Michael has authored several major publications, such as SharePoint 2007 Unleashed and Exchange 2007 Unleashed Omar Droubi has been in the computer industry for more than 15 years, has co-authored one of Sams Publishing's bestselling books, Windows 2003 Unleashed, and has been a contributing writer and technical reviewer on several other books on Windows Server 2003 as well as Exchange 2000, 2003 and 2007. Ross Mistry is a seasoned veteran in Silicon Valley and has spent more than a decade in the computer industry. As a principal consultant and partner with Convergent Computing (CCO), he had the opportunity to work with Windows Server 2008 for three years before the product was released to the public. Chris Amaris is the chief technology officer and co-founder of CCO. He has more than 20 years' experience consulting for Fortune 500 companies, leading them in the selection, design, planning and implementation of complex information technology projects. Chris worked with Windows 2008 for three years before its release to the general public.|
This was first published in February 2008