Hyper-V, like any other software product, should be configured after installation so that you can maximize the virtualization performance.
This chapter begins by exploring some of the Hyper-V terms and concepts needed to configure Hyper-V. We will also discuss the configuration of virtual networking, including how to configure your virtual and nonvirtual switches, the Virtual Network Manager, and the System Center Virtual Machine Manager (SCVMM).
Next you will learn how to configure Hyper-V remotely using Windows Server 2008 and Windows Vista. We will cover the Microsoft Windows Firewall and Remote Desktop Protocol (RDP). Finally, we will discuss Windows Management Instrumentation (WMI) and Windows Remote Management (WinRM), and you will learn how using these utilities can better help you configure and maintain your Hyper-V environment.
Managing and optimizing the Microsoft Hyper-V server
Configuring virtual networking for Microsoft Hyper-V
Configuring remote administration for Microsoft Hyper-V
Download the rest of this chapter excerpt
So let's begin by exploring some of the tools and techniques you need to configure the Hyper-V role properly.
Understanding the Configuration Tools and Techniques
It is always important to configure any application properly to allow that application to work at peak performance. Hyper-V is no different. By configuring Hyper-V, you are reducing the chances that any problems will occur down the road.
Configuring an application can be the most important and sometimes the most difficult task that you can complete. The time that you spend on the configuration now will be time that you save on fixing the application later.
Hyper-V has many variables that can you configure, from the virtual hard disk to the memory used for the virtual machine. First let's define some terms and concepts you should be familiar with.
Host Server (Parent Partition) The host server is the Windows Server 2008 machine that hosts the Hyper-V role and executes the Hyper-V virtual machines. The host server is also known as the parent partition.
Guest (Child Partition) These are the containers (virtual machines) that run the guest operating system. The virtual machines are referred to as the guest, or child, partition. These virtual machine systems can have operating systems running other than Microsoft. Virtual Hard Disk (VHD) When you're installing an OS onto a computer, you determine the size and location of the hard disk that you want to install the operating system on. A virtual hard disk (VHD) is the same for the virtual environment. When you install a guest system using Hyper-V, the VHD is the hard disk space you are using for that install.
VMBus The parent and the child partitions use a new high-speed communication protocol for Hyper-V hardware called VMBus. As you learned in Chapter 1, the Microsoft hypervisor handles the interaction between multiple virtual machines running on the same host. VMBus handles many of the hardware communications, such as disk, networking, video, and input/output communications.
Host Clustering To make Hyper-V more available on your network, you can install and run the clustering role on one or more Hyper-V servers. This type of clustering is called host clustering. An advantage of clustering is that if one of the servers goes down, the other servers in the cluster take up the extra load and continue to allow the cluster to run properly. (Hyper-V clustering is covered in full detail in Chapter 7, "Hyper-V and Failover Clusters.")
Operating System Partitioning When setting up Hyper-V, you normally create two partitions: the parent and the child partitions. The parent partition manages the memory and virtual devices; the child partitions are the virtual machines. You can have as many child partitions as needed, but your Hyper-V can have only one parent partition. The child partitions can contain both 32-bit and 64-bit operating systems loaded on the virtual machine.
Now that you have a few basic terms and concepts down, let's start our Hyper-V configuration with VHDs.
Understanding Virtual Hard Disks
There are two main types of virtual hard disks (VHDs): fixed-size or dynamic. When setting up either of these VHDs, you determine the size of the VHD, and that will represent how large the disk will appear to the virtual machines. The maximum size that you can choose for either VHD is 2,040GB.
Fixed-size VHDs have a set amount of hard disk space and that amount does not change. For example, if I designate 16GB to a fixed-size VHD, then the VHD will take up all 16GB on the hard disk immediately -- regardless of how much the system is actually using.
Dynamic VHDs only use the amount of space that is currently being used for the VHD. For example, if a dynamic VHD has 16GB allotted to it but it's only using 7GB, only 7GB will be used by the system. This is how you want to set up your VHD if hard drive space is limited on your server. However, the fixed-size VHD option offers better performance by eliminating the fragmentation associated with a growing file. Figure 3.1 shows the Choose Disk Type screen of the New Virtual Hard Disk wizard.
When setting up your VHD, there is a third option you can choose called differencing.
A differencing disk is configured in a parent-child relationship with another disk that is left intact. This approach allows you to change the operating system or data without affecting the parent disk.
Differencing can help Hyper-V by reducing hard drive space on a host server but can be difficult to manage due to the parent-child relationship. The parent-child relationship may also cause performance issues. Figure 3.2 shows the Configure Disk screen of the New Virtual Hard Disk wizard. Differencing disks will be discussed in further detail in Chapter 4, "Creating Virtual Machines."
You need to establish a default location for storing your VHDs (see Figure 3.3). Depending on your network and your hard drive setups, this can be a critical decision. Do you want to store your VHDs locally on the server, or on the network? Keep in mind that the host system has the ability to store VHD files on an accessible file system, internal hard drive, or a storage area network (SAN).
This setting will be your default location for all VHDs from this point on, but you have the ability to change the location of any VHD even after this setting is configured. Figure 3.4 shows the installation of a new VHD and the option to change the storage location of the VHD.
Exercise 3.1 shows you how to set the default VHD file location in the Hyper-V
EXERCISE 3 .1
Setting the default storage Location for VHDs
1. Choose Start > Administrative Tools > Hyper-V Manager.
2. In the Hyper-V Manager, click on your Computer Name, and then in the Actions pane, click Hyper-V Server Settings
3. In the Hyper-V Settings dialog box, click Virtual Hard Disks.
4. In the field "Specify the default folder to store virtual hard disk files," type the folder name, such as C:\sybex\VHd, and then click Apply.
5. In the Hyper-V Settings dialog box, click Virtual Machines.
6. In the field "Specify the default folder to store virtual machine files," type the folder name, such as C:\sybex\VM, and then click OK.
Using Pass-Through Disk Access
You may be familiar with Microsoft's earlier virtualization products, Windows Virtual Server and Virtual PC. Hyper-V, Microsoft's newest virtualization technology, has many new features in the area of virtual machine storage. One such feature is called pass-through disk access.
This feature allows Hyper-V to work without the use of VHDs. Virtual machines can access a file system directly through the use of pass-through disk access, thus eliminating the need for VHDs. VHDs are inaccessible to nonvirtualized systems due to the VHD formatting. Pass-through disk access helps solve this problem by allowing the virtual machine to directly access the writable file system. Another advantage is that there is no 2040GB limitation as with VHDs.
So here is another decision for you to make when setting up the Hyper-V storage system: do you use pass-through disk access or VHDs? You must decide whether it's more important that virtual machines and applications be able to access the disk directly or that you take advantage of the VHD features, such as VHD snapshots (discussed further in this section), differencing, or dynamic VHDs.
After you make your decision, you have to specify how you want to show your host disks to your guest machines. You have the ability to show your disks as either virtual ATA devices or virtual SCSI devices (see Figure 3.5). The disk type does not have to match the way you decide to show the disk to the guest. For example, a SCSI disk can be shown to the guest as an IDE disk and an IDE disk can be shown as a SCSI disk.
The requirements of the guest operating system determine how you will set the drive types. IDE hard drives are drives that the guest system can boot from, but with an IDE drive you can only have four virtual disks (two disks on two controllers). You can set up 256 SCSI virtual disks (64 disks on four controllers), but the system cannot boot up from the virtualized BIOS. If you need your guest systems to have more than four disks, you must use SCSI; if you need your guest systems to boot to the virtual disk, use IDE.
When setting up your disk types, you have the ability to use both IDE and SCSI at the same time. If needed, you can boot off the IDE drive and use the SCSI drives for storage or applications.
Configuring Virtual Machine Snapshots
A feature that has become common in the Microsoft Windows world is volume shadow copies. Creating backups of open files is a challenge that all IT personnel have dealt with in their careers. Typically, backup software can't back up files while they are open.
Microsoft includes the Shadow Copy feature with most of its newer operating systems. Before this feature was released, if you ran your Microsoft Exchange mail server 24 hours a day, you had to purchase a special component of your backup software to back up your open Exchange files. Now, you can use the Shadow Copy feature to "take a picture" of the open files and then copy the picture to a location for recoverability.
Using Hyper-V, you can enjoy the advantages of shadow copies with your virtual machines. Hyper-V allows you to set up virtual machine snapshots. Hyper-V takes a "snapshot" of your virtual machine and places that copy in a specified location. Using the dialog box shown in Figure 3.6 (see Exercise 3.2 for a step-by-step), you specify the default location for these snapshots.
Having virtual machine snapshots gives you a few very important benefits. You have a backup copy of the virtual machine in case of a crash or error, and can quickly recover from any major problems. Also, this feature allows you to make major configuration changes to the operating system (such as adding new software or running updates) without worry. If the installation causes any problems, you can just revert back to a previous snapshot.
Real World Scenario
Configuration Changes on Your servers
For all the years I've been in the IT field, one thing that has always amazed me about Microsoft is their patches and updates. I like Microsoft products and I rarely complain about how they work, but one thing that has always bothered me is their product testing. There have been multiple times where I have loaded a patch from Microsoft and had my computer crash. These days, I wait until a patch or update has been out a while to make sure the bugs are worked out before I load the patch or update onto my network computers.
Hyper-V and virtual machine snapshots can help in this situation. Having the ability to revert back to a snapshot if a patch or update causes a problem can solve these issues. Also, Hyper-V can help because, as mentioned in Chapters 1 and 2, you can use a Hyper-V virtual machine environment just for testing. This way, the patches won't be placed on a live server or workstation, and it gives you the advantage as an administrator to evaluate the update before taking it live.
Exercise 3.2 shows you how to set the default location for your snapshots. Keep in mind that once your snapshot is created, you can't change the folder location unless the snapshot is stopped.
Setting the default snapshot locations
1. Select Start > Administrative Tools > Hyper-V Manager.
2. In the Hyper-V Manager, click on your computer name in the console tree, and then in the Actions pane, click Hyper-V Server Settings.
3. In the Hyper-V Settings dialog box, click Snapshot File Location.
4. In the field "Specify the default folder to Virtual Machine Configuration files," type a folder name, such as C:\sybex\snapshot, and then click Apply.
Hyper-V allows you to manipulate a virtual hard disk offline using a command-line utility called VHDMount. By using VHDMount, you can work directly on an offline VHD and do maintenance without having to power on the virtual machine.
When you use VHDMount, an undo disk is automatically created by the system. This undo disk records any changes that are completed to the mounted drive. You can use the undo disk to accept or reject the changes.
Configuring Hyper-V Server Settings
We just finished setting up our default snapshot locations and our default VHD locations, but there are many other server changes that can help optimize your Hyper-V environment.
BIOS When setting up the BIOS for your Hyper-V server, the first thing you can specify is whether the numbers lock (Num Lock) is on or off by default when the Hyper-V server starts (see Figure 3.7).
You can also specify the Startup Order for the operating system. This is the order that your boot devices will be checked to start the operating system. You can boot from a CD, hard drive, network adapter, or a floppy disk.
Memory You need to have enough memory to handle the workload of the system and some extra for a buffer. A virtual machine only uses memory when it is either running or is paused. To configure the memory option, you must make sure the virtual machine is turned off.
Processors The number of physical processors you have on your machine determines the number of virtual processors you can set on the Hyper-V server (see Figure 3.8). Other processor configuration options are related to resource control and process functionality. Again, to configure these options, make sure the virtual machine is turned off.
Virtual Machine Reserve (Percentage) Here you specify how much of the hardware resources you want to reserve for Hyper-V. This setting will guarantee that the hardware that you reserve for Hyper-V will be available to the virtual machines.
Virtual Machine Limit (Percentage) This option allows you to define the total maximum amount of resources that the virtual machine can use. No matter how many virtual machines are running, this setting always applies.
Relative Weight This value specifies how resources will be allocated to the current virtual machine when more than one virtual machine is running. When multiple virtual machines are running at the same time, they are all competing for the use of the machine's hardware resources. The Relative Weight setting helps allocate these resources to the virtual machines.
Processor Functionality This option allows you to limit the processor functionality so that you can load an older operating system (such as Windows NT 4.0) on the virtual machine.
IDE Controller Here you specify your hard drive or DVD drive. You have the ability to add a controller at this screen. After the drive has been attached to one of your controllers, you can configure the hard drive to use either the virtual hard disk or the physical hard disk.
Hard Drive In this section you configure how the virtual hard disk is linked to the virtual machine. You can create, edit, remove, and inspect the VHD file (see Figure 3.9).
NOTE: The Network Adapter section of the server settings will be discussed later in the chapter, in the section "Configuring Virtual Networking."
COM Ports This setting allows you to set up a named pipe that enables the physical computer to communicate through the use of a virtual COM port. There are two COM (COM1 and COM2) ports that you can configure in Hyper-V.
Diskette Drive This setting allows you to set up a diskette drive in the Hyper-V environment.
Name Name is the first option that you can configure under the management section. This screen (see Figure 3.10) allows you to rename the server and also record notes about the virtual machine.
Integration Services This screen (Figure 3.11) allows you to choose which services in Hyper-V you would like to offer to the virtual machines. Table 3.1 lists some of these services.
TABLE 3.1 Integration Services Options
Operating System Shutdown - Allows an administrator to properly shut down a guest operating system by using the Virtualization Management Console
Time Synchronization - Ensures that the time is synchronized between the host system and the guest operating system
Heartbeat - Verifies that the guest operating system is working properly and is not currently locked up (hung up)
Backup (Volume Snapshot) - Helps create a backup or snapshot of the virtual machines
Automatic Start Action This screen (see Figure 3.12) allows you to configure how the virtual machine is going to react when the physical machine is started. When the machine starts, you can have the virtual machine either do nothing or automatically start if it was running when the service stopped, or you can always start the virtual machine automatically. You also have the ability to set an automatic start delay. A start delay can help reduce resource contention among virtual machines.
Automatic Stop Action This setting allows you to determine how the virtual machine will shut down when the physical machine shuts down. You can choose one of three options: Save The Virtual Machine State, Turn Off The Virtual Machine, or Shut Down The Guest Operating System.
Release Keys Release keys are the key combinations that release tasks. For example, pressing Ctrl+Alt+Delete starts the Task Manager or Windows Security box (logons), but that will not work in Hyper-V. To start the same tasks in Hyper-V, you need to press Ctrl+Alt+End. Table 3.2 shows you some of the Windows key combinations and what the corresponding Hyper-V key combinations are to start the same task.
TABLE 3.2 Key Combinations (download PDF for TABLE 3.2)
Setting these configuration settings will help you manage your virtual environment more efficiently. Next, let's take a look at setting role-based access control.
Using Authorization Manager
Authorization Manager allows you to integrate role-based access control into applications. This gives you the flexibility to assign application access to users based on their job functions. Since Hyper-V is a server role, you can use Authorization Manager to work with Hyper-V. For example, users in your domain who are not administrators can still be given permissions to create and modify virtual machines in your organization. You also have the ability to specify certain users to manage only certain virtual machines.
To set up Authorization Manager, you must first create an authorization store, where the role-based access permissions will reside. The permissions can be stored in any one of the following:
- Active Directory Domain Services (AD DS)
- Active Directory Lightweight Directory Services (AD LDS)
- SQL databases
- XML files
If you choose to use AD DS, the function level must be at the Windows Server 2003 level. Function levels are discussed in detail in MCTS: Windows Server 2008 Active Directory Configuration Study Guide by William Panek and James Chellis (Sybex, 2008).
Because Authorization Manager provides role-based access to Windows applications, any application that needs role-based authorization can use this tool. Authorization Manager gives you a centralized location to record all your assigned access and their corresponding application. After you have installed and configured Authorization Manager, you can use scripts to control how Authorization Manager works. These scripts, called authorization rules, allow you to configure specific control over the way access is given throughout your organization.
REAL WORLD SCENARIO
Depending on your network setup and how long you have been in the industry, you may have been in a situation where multiple applications have had multiple sets of permission or access. Years ago, there was no centralized application that showed you all your users and their corresponding role-based access to applications. You would have to go application to application and figure out which users had what access.
The problem becomes difficult when you have multiple administrators doing the same job. Now you may have different administrators assigning different access to multiple people. Also, if your IT department is like many around the world, your department almost never documents anything unless it's mandatory.
This is where Authorization Manager can be helpful. Authorization Manager gives you a centralized location for all administrators to record role-based application access.
Folks in the IT field often don't like to document IT issues or items. As a consultant and instructor, I have heard this many times: "I don't document; if they fire me, let them figure out their own network." I understand what many IT people are thinking, but it is important to document so that later you can go back and see what you did. You may fix an item and six months later come across the same item again; documenting what you did may save you many hours of work and frustration.
When setting up Authorization Manager's role-based application access, there are two
categories of roles that are specifically used:
User Authorization Roles These are roles set up through Authorization Manager that are based on the user's job function. You configure role-based access to users to allow them to perform their day-to-day tasks. For example, you might define an accountant role that would include the right to authorize transactions for the organization.
Computer Configuration Roles These are roles set up through Authorization Manager that are based on the computer's function. You configure role-based access to a machine for specific tasks to be done. For example, you can configure a machine so that it can be designated as a domain controller, web server, or file server.
When setting up Authorization Manager, you can specify which groups can receive authorization policies. The types of groups are as follows:
Windows Users and Groups This group includes the Active Directory users, computers, and built-in group objects. The Windows users and groups are used not only for Authorization Manager but throughout the Microsoft domain model.
Application Group The Application group consists of users, computers, and other security groups in Authorization Manager. This group is an Authorization Manager group only; it is not a group of applications but a group of security objects.
LDAP Query Group This is a type of Application group whose membership is dynamic. This group uses Lightweight Directory Access Protocol (LDAP) queries to help determine, as needed, the membership of the group.
Basic Application Groups This is a type of Application group that is specific to Authorization Manager. This group type allows you to specify the members of the group, but it also allows you to specify who is not a member of the group.
Business Rule Application Group This is a type of Application group whose members are created by a script (using VBScript or JScript, for example) at application runtime. This group allows you the flexibility to determine the criteria of the group membership through the use of a script.
Windows Server 2008 includes many new features for the Authorization Manager Microsoft Management Console (MMC) snap-in:
- Authorization stores that can be stored in SQL databases, AD DS, AD LDS, or an XML file
- Business rule groups (groups whose membership is configured by a script at application runtime)
- Custom object pickers
- API improvements
- Improved auditing
When you are using business and authorization rules in Authorization Manager, you set the rules by configuring registry settings. In earlier versions the rules were enabled by default, but this has changed in Windows Server 2008 Authorization Manager, where the rules are disabled by default. Authorization Manager is available for all editions of Windows Server 2008 in both 32- and 64-bit versions.
In Exercise 3.3 we will start using Authorization Manager by installing the MMC snap-in. MMC is the application that all other Microsoft applications run through. For example, there is an MMC snap-in for DNS, DHCP, and Active Directory. Knowing that most administrative tasks run using the MMC allows you to customize and configure custom administrative console windows. Let's say you are responsible for DNS, DHCP, and Authorization Manager; you can configure an MMC snap-in that has all of these applications in one location.
Installing authorization manager
5. Authorization Manager should now be the only item in the window on the left. Choose File > Save. In the File Name box, type Authorization Manager.msc. Save the file in the Administrative Tools folder by choosing Administrative Tools from the Save In drop-down list.
6. Close all MMC windows.
Once the installation of Authorization Manager is complete, it's time to configure Authorization Manager. One of the first things that we have to do is create a new authorization store. To do this, we must be in the Developer mode of Authorization Manager. In Exercise 3.4 we begin by changing the mode type and then create a new authorization store.
Configuring authorization manager
1. To start the Authorization Manager, click Start > All Programs > Administrative Tools, and then click Authorization Manager.msc.
2. Once the application opens, click on Authorization Manager in the window on the left. Right-click and choose Options.
3. Make sure that the Developer mode radio button is selected and click OK.
4. To use Authorization Manager, you must create an authorization store. Select Action > New Authorization Store.
5. In the resulting dialog box, make sure the XML File and Schema Version 2.0 radio buttons are selected. In the Store Name box, append TestStore to the end of c:\users\Administrator\Documents\ and click OK.
6. We need to now create an Application group. On the left-hand side, click the Groups folder under TestStore.xml. Right-click on the Groups folder and choose New Application Group.
7. In the Name field, type testgroup and make sure the Basic Application Group radio button is selected. Click OK.
8. In the center window, select and then right-click the TestGroup group and choose Properties. Click the Members tab. In the Select Additional Members From box, make sure that Windows And Active Directory is selected, and click the Select button.
9. In the Enter The Object Names To Select box, choose a user on your machine and click the Check Names button. After the name is verified, click OK. As you can see here, we chose the Will Panek account for this example. Click OK again when you return to the TestGroup Properties screen.
10. Close the Authorization Manager MMC snap-in.
Authorization Manager can help any organization manage its virtual environment safely. But when it comes to the virtual environment, there are many more areas that we can configure to make virtualization run more efficiently. Let's take a look at one of the utilities that allows you to manage and configure your virtual world.
Introducing System Center Virtual Machine Manager
Microsoft has been using virtualization in the IT field for many years. To make it easier for IT personnel to do their jobs, over the years Microsoft has released applications that use wizards and templates.
Microsoft has also tried to improve the manageability of virtualization by implementing System Center Virtual Machine Manager (SCVMM). SCVMM is an easy-to-use and cost-effective application for administrators who are responsible for managing virtual networks. Since SCVMM works with the Windows Server 2008 technology, it allows you to configure and manipulate the physical and virtual machines, consolidate underutilized physical machines, and implement new virtual machines.
One of the advantages of SCVMM is that it provides a centralized location to manage your virtual environment. This allows administrators to manage and configure the virtual machines from one spot. The SCVMM has many other advantages including the following:
Windows Server 2008 Support SCVMM takes full advantage of the Windows Server 2008 operating system and its advantages, which include Hyper-V and all of its benefits along with the Windows Server 2008 64-bit architecture. Windows Server 2008 also supports clustering support and attack hardening.
Multivendor Virtualization Support One of the nice features of using SCVMM is the ability to support multivendor virtualization platforms. This allows the virtual machines to run operating systems other than Microsoft's. This gives your organization the flexibility to run applications that require non-Microsoft platforms.
Performance and Resource Optimization A new feature is the Performance and Resource Optimization (PRO) utility. PRO can automatically react to failed or badly configured components. One nice advantage of PRO is that it also works with VMware, which allows you to manage your entire virtualized network no matter which virtualization platform you choose.
Clustering Support SCVMM 2008 has new clustering support built in, which allows your organization to improve its availability for managing critical virtual machines. SCVMM can also detect Hyper-V host clusters and then manage those clusters as a single unit.
To install SCVMM, you must first install the .NET Framework (see Exercise 3.5).
Installing the .NET framework
1. Start the Server Manager application by clicking Start > Administrative Tools > Server Manager.
2. On the left-hand side, click the Features link.
3. On the right-hand side, click Add Feature.
4. Click the .NET Framework 3.0 Features check box.
5. An information box appears asking whether you want to install IIS as well. Click OK.
6. On the Select Features screen, click Next.
7. On the Introduction to Web Server (IIS) screen, click Next.
8. The Select Role Services screen appears; accept the defaults and click Next.
9. On the Confirmation screen, click Install.
10. On the Installation Results screen, make sure that all components installed successfully and click Close. Close the Server Manager application.
In Exercise 3.6 we will download and install SCVMM. Microsoft allows you to evaluate this product for 120 days. (The SCVMM will be discussed further throughout this entire book.)
NOTE: At the time that this book was written, the SCVMM 2008 version (vNext) was just released in beta.
Downloading and installing SCVMM 2008
1. We need to download the SCVMM from Microsoft's website. On their web site you will need to register for the SCVMM download. Once you get to the download area, save the download to your computer . After the download is complete, run the SCVMM executable. Click the Install button, and files will begin to extract.
3. On the Microsoft License Terms screen, click the I Accept The Terms Of This Agreement radio licensing button and click Next.
4. You will see the Customer Experience Improvement Program screen next. This screen asks if you would like to participate in an improvement program to make the products better. You can decide how you want to respond. Read both questions and choose one of the radio buttons, and then click Next.
5. At the product registration screen, enter your name and your company name if you
have one. Click Next.
6. The Prerequisites Check screen will appear next, and it will automatically check the hardware of your machine. After it verifies that you meet the minimum requirements, click Next.
7. The Installation Settings screen will then ask you to choose an installation path for the install files. Accept the defaults and click Next.
8. The next screen asks you to either install SQL Server 2005 Express Edition or point to a previously installed version of SQL Server 2005. Click Install SQL Server 2005 Express Edition SP2 and then click Next.
9. The Library Share Settings screen appears, which allows you to create a new library share or use an existing one. The library share is the location of the virtual machine library, and enables you to make resources available when creating new virtual machines. Choose the Create A New Library Share radio button and click Next.
10. The Port Assignment screen asks you to choose which port numbers you want to use when setting up SCVMM. The default ports are 8100, 80, and 443. Port 80 is the HTTP default setting, and port 443 is secure HTTP (HTTPS). Accept the defaults and click Next.
11. On the Summary Of Settings screen, verify your settings and click the Install button.
12. After the installation, make sure the Check For The Latest Virtual Machine Manager Updates check box is selected and then close the installation utility by clicking Close.
The SCVMM utility is a major component in your virtualization toolbox. It allows you to have one application that all administrators can use to configure your entire virtualized infrastructure. When you are setting up virtualization, one component that you must configure is your virtual network. So let's take a look at virtual networking.
Printed with permission from Wiley Publishing Inc. Copyright 2009. MCTS: Windows Server Virtualization Configuration Study Guide: (Exam 70-652) by William Panek. For more information about this title and other similar books, please visit http://www.wiley.com.