70-659 testing bible(81 to 96) for examinee: Mar 2021 Edition

★ Pass on Your First TRY ★ 100% Money Back Guarantee ★ Realistic Practice Exam Questions

Free Instant Download NEW 70-659 Exam Dumps (PDF & VCE):
Available on: https://www.certleader.com/70-659-dumps.html

70-659 Product Description:
Exam Number/Code: 70-659 vce
Exam name: TS: Windows Server 2008 R2, Server Virtualization
n questions with full explanations
Certification: Microsoft Certification
Last updated on Global synchronizing

Instant Access to Free VCE Files: Microsoft 70-659 TS: Windows Server 2008 R2, Server Virtualization

70-659 examcollection

Question No. 81


You create a snapshot of a running virtual machine (VM) before installing a new application. 

You receive an alert that the host is running low on disk space on the volume where you took a snapshot of the VM. 

You need to free up disk space on the volume while ensuring that future restarts of the VM are successful. 

Which three actions should you perform in sequence? (To answer, move the appropriate actions from the list of actions to the answer area and I arrange them in the correct order.) 


Question No. 82


A company has a Windows Server 2008 R2 Hyper-V server environment. The environment is managed by using Microsoft System Center Virtual machine Manager (VMM) 2008 R2. 

You deploy a new Hyper-V host server. New Virtual Network #0 is attached to a switch that is configured with an 802.1q trunk port. 

You need to ensure that the host server can communicate on the New Virtual Switch #0 to access VLAN 325. 

Which option should you select first? (To answer, select the appropriate setting in the work area.) 


Question No. 83

You work as a Network Administrator at ABC.com. The network consists of a single Active Directory Domain Services (AD DS) domain named ABC.com. 

The company network consists of an internal LAN and a perimeter network. To comply with company security policy, servers located in the perimeter network are not members of the ABC.com domain. 

A Microsoft Hyper-V Server 2008 R2 server named ABC-VMHost1 is located in the perimeter network. You relocate ABC-VMHost1 into the internal network. You now need to join ABC-VMHost1 to the ABC.com AD DS domain. 

How should you join ABC-VMHost1 to the ABC.com domain? 

A. You should use the System Properties control panel applet. 

B. You should use the Netsh command line utility. 

C. You should use the Hyper-V configuration utility (hvconfig). 

D. You should use the dcpromo utility. 




Question No. 84


A company has an environment that includes Microsoft Hyper-V Servers 2008 R2, Microsoft System Center Virtual manager (VM) and the VMM self service portal (SSP). That company’s network consists of one Active Directory Domains Services (AD DS) forest domain. All virtual machines (VMs) are currently owned by individual database team members. 

The company wants to delegate rights for virtual machines (VMs) and has the following requirements: 

-The database team must be able to create VMs and administer them by using the SSP. -The database team must be able to share the VMs with other members of the database team. 

-The principle of the least privilege must be used. 

You need to provide a solution to meet the requirements. 

Which three actions should you perform in sequence? (To answer, move the appropriate actions from the list of actions to the answer, arrange them in the correct order) 


Question No. 85

All servers on your companys network run Windows Server 2008 R2. You deploy Remote Desktop Services (RDS). 

The company has a load-balanced Remote Desktop Connection Broker (RD Connection Broker) cluster. 

You are adding a Remote Desktop Session Host (RD Session Host) server to the cluster. 

You need to ensure that the RD Session Host server will receive only half of the RDS sessions. 

What should you do? 

A. Enable IP redirection on the RD Session Host server. 

B. Enable token redirection on the RD Session Host server. 

C. Configure the server weight for the RD Session Host server. 

D. Configure the DNS weight priority for the RD Session Host server. 



TS Session Broker Load Balancing sets a limit of 16 for the maximum number of pending logon requests to a particular terminal server. This helps to prevent the scenario where a single server is overwhelmed by new logon requests; for example, if you add a new server to the farm, or if you enable user logons on a server where they were previously denied. 

The TS Session Broker Load Balancing feature also enables you to assign a relative weight value to each server. By assigning a relative weight value, you can help to distribute the load between more powerful and less powerful servers in the farm. 

Additionally, a new "server draining" mechanism is provided that enables you to prevent new users from logging on to a terminal server that is scheduled to be taken down for maintenance. This mechanism provides for the ability to take a server offline without disrupting the user experience. If new logons are denied on a terminal server in the farm, TS Session Broker will allow users with existing sessions to reconnect, but will redirect new users to terminal servers that are configured to allow new logons 

110. Your network includes the servers shown in the following table. 

Per-Device Remote Desktop Services client access licenses (RDS CALs) are installed on Server1. 

After you refresh a group of client computers with Windows 7, users on those computers can no longer connect to Server2. 

You need to ensure that the users can connect to remote applications. 

What should you do? 

A. From the affected client computers, initiate a Remote Desktop connection to Server1. 

B. From the affected client computers, initiate a Remote Desktop connection to Server3. 

C. On the affected client computers, open port 3389 on the Windows Firewall. 

D. On Server1, revoke the RDS device CALs of the affected client computers. 



We have enabled RDS CALs per device then the computers can connect to server3 but not to server2 and vice versa. Because, RDS CALs are enabled. 

Revoke the device CALs of the affected group. 

Port has already been open - Not a firewall issue. 

We need to fix the issue on server2 not on server1 or server3. 

Question No. 86

A company has a server that runs Microsoft System Center Virtual Machine Manager (VMM) 2008 R2, System Center Data Protection manager (DPM) 2010, and Windows Server 2008 R2 with Hyper-V. 

A Hyper-V host has a virtual machine (VM) that uses a basic disk. 

You need to perform a backup of the VM configuration and its virtual hard disk while minimizing downtime. 

What should you do? 

A. Perform an offline backup by using DPM. 

B. Perform an online backup by using DPM. 

C. Perform a system state backup by using windows Server Backup. 

D. Perform a VMM database backup by using VMM. 



Backing up Hyper-V Host-Based Backups One exciting benefit of server virtualization is the prospect of no longer having to individually back up the virtualized systems. Now that these systems are simply files living on a host's file system, you can just back up the files and call it a day, right? Not exactly. Because these are live computers consisting of in-memory data, data on disk, system configurations, and open files, there are a few things to consider. So how do we ensure backup data consistency given all these moving parts? 

A significant improvement to the Windows Server backup story came with Windows Server 2003 and the advent of VSS, which provides a standard set of extensible APIs that VSS writers (hooks in applications and services that help provide consistent shadow copies) use in order to create backups of open files and applications. With the help of the VSS service, providers, and writers, the backup application can generate a point-in-time copy of a volume very quickly, one that the application is aware of and can process appropriately. Hyper-V comes with its own VSS writer that allows software makers to create compelling backup solutions. The writer lets backup applications achieve host-based VSS backups of running VMs. If the operating system running within the VM has the Hyper-V Integration Components installed as well as the VSS service (available in Windows XP SP1 and Windows Server 2003 and later), the host-based backup will occur as if it were run inside the guest; the backup will be performed with the VM running and the data will be consistent (see Figure 4). 

Figure 4 VSS backup (Click the image for a larger view) However, if the guest operating system does not support the Integration Components or VSS, the backup process requires that the guest machine be put into a saved state and that a host-based VSS snapshot is taken of VM data files that can be used for point-in-time recovery. Saved-state VSS snapshots will incur some VM downtime (this can typically be limited to 5-10 minutes), with full backup-to-tape procedures taking place against the VSS copy of the data. 

Guest-Based Backups In a physical environment, servers and applications need to be backed up on an individual basis, and such backups can certainly continue in a virtualized datacenter. In this situation, the same considerations need to be taken into account when backing up a VM, such as network capacity requirements for network-based backups and performance impact to the system during the backup window. With guestbased backups, you can choose to have a dedicated physical NIC in the host that is bound to a virtual network that all guests use. Windows Server Backup Included with Windows Server 2008 is the VSS-capable Windows Server Backup (WSB), which can be used to perform Hyper-V host- and guest-based backups of your VMs. Because it's fully VSS-capable, it can perform host-based backups of your running VMs, which of course is preferable. 

But if you have VMs without the Integration Components installed, VSS will not be used. In that case, you have a couple of options from which to choose. You can still use WSB to back up a VM that does not have the Integration Components installed, which means the VM's state will be saved and then the backup will grab the VM's virtual disks and configuration files. However, this may not be desirable with an application such as Exchange because the application will not be aware a backup has run and application logs will not be truncated. Moreover, downtime will occur on the VM, which will vary depending on how long the backup takes. 

Alternatively, a backup can be run from inside the VM just as if it were a physical machine using either NTBackup or WSB, depending on the VM's OS. Let's see how to use WSB for supported guests that have the Integration Components installed. Backing up VMs with WSB Hyper-V does not automatically register its VSS writer for use with WSB. You must manually add the registry key and value shown in Figure 5 before WSB will support a Hyper-V backup. You can add them via the command line, like so: 

Copy Code reg add "HKLMSoftwareMicrosoftwindows nt currentversionWindowsServerBackupApplication Support{66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}" reg add "HKLMSoftwareMicrosoftwindows nt currentversionWindowsServerBackupApplication Support{66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}" /v "Application Identifier" /t REG_SZ /d Hyper-v 

Question No. 87

You use Microsoft System Center Virtual Machine Manager (VMM) 2008 R2 to manage virtual machines (VMs). 

You need to deploy a cloned VM and automatically assign it a different name. 

Where should you deploy the cloned VM? 

A. to the same host as the source VM 

B. to a different host from the source VM 

C. to the same library as the source VM 

D. to a different library from the source VM 



If the cloned VM is placed in the same host then it will create a VM name called "Copy of VMname" in VMware. 

I am not sure about the Hyper-V. 

Question No. 88

On each Guest, in Windows Rename the network connections accordingly. I have mine as such: 

Question No. 89

Your environment includes Hyper-V and VMware ESX. You manage your virtual environment by using Microsoft System Center Virtual Machine manager (VMM) 2008 R2. 

You plan to perform a virtual-to-virtual (V2V) conversion of a virtual machine (VM) that is located on the ESX server. 

You start the conversion by using the Convert Virtual Machine Wizard. 

Communication between the destination host and the ESX server fails, and the conversion does not finish successfully. 

You need to ensure that the conversion finishes successfully. 

What should you change? 

A. WSMan permissions and settings 

B. Windows Firewall exceptions for Background Intelligent Transfer Service (BITS) 

C. Secure Shell (SSH) and HTTPS settings 

D. Server Message Block (SMB) settings 



We need to make sure that the conversion has right port settings in both the source and target. 

ESX server uses SSH (Port 22) and Hyper-V uses HTTPS (443) port for secure transmission. 

System Center Virtual Machine Manager (VMM) allows you to convert existing VMware 

Server–based virtual machines so you can manage them in a VMM environment. 

Requirements This section lists the V2V requirements for converting VMware Server-based virtual machines. 

Source Virtual Machines 

To perform a V2V, your source virtual machine must contain one of the following operating systems: 

Microsoft Windows 2000 Server Service Pack 4 (SP4) 

The Windows Server 2003 operating systems with Service Pack 1 (SP1) 

The Windows Server 2003 R2 Standard Edition operating system 

The Windows XP operating systems with SP1 

The source virtual machine consists of the following files that you store in the Virtual Machine Manager library: 

A .vmx file, which is a VMware virtual machine configuration file. A .vmx file is the text file that describes the properties and structure of a virtual machine, including name, memory, disk assignments, network parameters, and so on. 

One or more .vmdk (virtual hard disk) files, which are not passed directly as input to the wizard but are listed in the .vmx file. A .vmdk file is a VMware virtual hard disk that contains the virtual machine's guest operating system, applications, and data. Supported VMWare virtual hard disk formats include the following: 






Requirements for the Host Server 

In Virtual Machine Manager, a host is a physical computer on which you can deploy one or more virtual machines. To run V2V, you need a host on which to place the converted files while the virtual machine is converted. 

Requirements for the host server include: 

Virtual Server R2 SP1 or later 

Adequate RAM (256 MB plus memory for the virtual machine) 

By default, the amount of memory reserved for the target host is 256 MB. This is in addition to the memory required by the V2V process for each source computer. If the host does not have enough memory, you will get a placement error in the Convert Virtual Machine Wizard. 

If you need to configure the virtual machine memory, you must perform the V2V from the command line. You will need to run the New-V2V cmdlet and set the MemoryMB parameter to a lower memory value. How to Perform a V2V Conversion 

During the conversion process, the Convert Virtual Machine Wizard converts the .vmdk files to .vhd files and makes the operating system on the virtual machine compatible with Microsoft virtualization technologies. The virtual machine created by the wizard matches VMware virtual machine properties, including name, description, memory, disk-to-bus assignment, and so on. 

The process for running a V2V conversion from the UI is as follows: 

Copy the .vmx file and each .vmdk file for the VMware virtual machine to the Virtual Machine Manager library. 

Run the Convert Virtual Machine Wizard, which performs the following steps: 

Identifies the disk formats and characteristics of the virtual machine. 

Converts the .vmdk files to virtual hard disk files in Virtual Server (.vhd) that reside on the destination host. 

VMM prepares the virtual hard disks and prepares for virtual machine creation. 

Convert Virtual Machine Wizard 

You can use the Convert Virtual Machine Wizard to convert a VMWare virtual machine. For detailed steps, see the "How to Convert a Virtual Machine to a VMM Virtual Machine" topic in 

VMM Help (http://go.microsoft.com/fwlink/?LinkId=101776). 

Performing V2V from the Command Line 

You can perform a V2V conversion from Windows PowerShell by using the New-V2V cmdlet. 

For more information about using the New-V2V cmdlet see "Windows PowerShell Scripting in Virtual Machine Manager" (http://go.microsoft.com/fwlink/?LinkId=91727). 

To watch a video of the V2V process as performed from the command line, see “VMM Introduction – Virtual Machine to Virtual Machine Migration” 



Before beginning a formal troubleshooting process, confirm that the source virtual machine has one of the following operating systems installed: 

Windows 2000 Server with Service Pack 4 (SP4) 

The Windows Server 2003 operating systems with Service Pack 1 (SP1) 

Windows Server 2003 R2 

The Windows XP operating systems with Service Pack 1 

If you use the Convert Virtual Machine Wizard to convert a VMWare-based virtual machine running any operating system not in the preceding list, the virtual machine might not start or function correctly. Some V2V conversions might require you to add additional system files and drivers to the internal cache. If additional files or drivers are required when you run the Convert Virtual Machine Wizard, do the following: 

Use information provided in an error message that appears when you run the wizard to identify what updates or drivers are required. 

Obtain a copy of those update or driver files and copy the files to the Patch Import directory on the Virtual Machine Manager server (the default path is <C>:Program FilesMicrosoft System Center Virtual Machine Manager 2007Patch Import). 

Run the Add-Patch cmdlet to extract those patches and populate the patch cache. 

Run the Convert Virtual Machine Wizard again, or use the New-V2V cmdlet. 

General Troubleshooting Strategy Find the source of the error by opening the Jobs view, selecting a job, and clicking theChange Trackingtab in the details pane. Find the job where the Status property changed. Once you find this job, click theSummarytab of the details pane to investigate the issue. 

Failed V2V Conversions 

Any V2V task failure places the virtual machine in the Creation Failed state. Some of the most common causes and their associated resolution strategies are described in the following sections. 

Numbered Error Codes 

Cause: You receive a specific error code. 

Resolution strategy: See "Virtual Machine Conversion Issues" 



Cause: Communication failed between: the VMM server, the library server that stores the VMware configuration and data files, and the virtual machine host on which the virtual machine will be created. 

Resolution: Check WSMan permissions and settings and Windows Firewall exceptions for the BITS and HTTPS ports. 


Cause: A patch or driver file that is required for the conversion is missing. 

Resolution strategy: If a patch file or driver is missing, download the requested patch and driver files to the Patch Import directory on the Virtual Machine Manager server (the default path is <C>:Program FilesMicrosoft System Center Virtual Machine Manager 2007Patch Import), and extract the files by using the Add-Patch cmdlet. 


Cause: Virtual Machine Manager does not have permission to access one or more files involved in the V2V process from the command line. 

Resolution: Ensure that the machine account for the destination host has access to the share that stores the virtual machine configuration file. 

vmx or .vmdk Files 

Cause: A V2V conversion was performed on a configuration file with an unsupported or unrecognized .vmx or. 

vmdk file format. 

Resolution: If the .vmx or .vmdk file format of the source virtual machine is not recognized, V2V conversion is not supported for that virtual machine in this version of Virtual Machine Manager. 

Operating System 

Cause: VMM cannot find a supported Operating System or does not recognize the physical disk layout on the new .vhd file, and cannot complete the conversion. 

Resolution: If VMM does not support the disk layout or operating system of the VMware virtual machine, VMM will create the virtual machine, but will not complete the conversion. As a result, the virtual machine might not start up or function correctly. 

Question No. 90

You have a Windows Server 2008 R2 Hyper-V server. 

You need to ensure that you are prompted to specify a custom snapshot name when you create a snapshot. 

What should you use to create the snapshot? 

A. Hyper-V Manager 

B. Windows Server Backup 

C. the Virtual Machine Connection window 

D. the Backup command-line tool (also known as wbadmin.exe) 



Virtual Machine Connection is a tool that you use to connect to a virtual machine so that you can install or interact with the guest operating system in a virtual machine. Some of the tasks that you can perform by using Virtual Machine Connection include the following: Connect to the video output of a virtual machine Control the state of a virtual machine Take snapshots of a virtual machine Modify the settings of a virtual machine 


Question No. 91

You have a Windows Server 2008 R2 Hyper-V server. You take periodic snapshots of your virtual machines (VMs) when the VMs are not running. 

You delete several snapshots from the snapshot tree of a VM. The .avhd files that are associated with the deleted snapshots are not deleted from the volume where the VHD files are stored. 

You need to ensure that the .avhd files are deleted. 

What should you do? 

A. Reset the VM. 

B. Pause the VM. 

C. Export the VM. 

D. Shutdown the VM. 



If you have deleted a snapshot while the VM is running then the snapshots will not be deleted until the VM is shutdown. 

Question No. 92

Your environment includes a Windows Server 2008 R2 Hyper-V server. The server hosts several virtual machines (VMs). 

You are configuring a VM to use pass-through disks. 

In the Hyper-V Manager Settings window for the VM, Disk 1 through Disk 7, Disk 9, and Disk 10 are available in the Physical hard disk list. Disk 8 does not appear in the list, as shown in the following display. 

You need to configure the VM to use Disk 8 as a pass-through disk. 

What should you do? 

A. Take Disk 8 offline. 

B. Convert Disk 8 to a dynamic disk. 

C. Format Disk 8, and mark the partition as active. 

D. Run the Diskpart command. At the Diskpart prompt, type select disk 8, and then type recover. 



Configuring Pass-through Disks in Hyper-V Pass -through Disk Configuration Hyper-V allows virtual machines to access storage mapped directly to the Hyper-V server without requiring the volume be configured. The storage can either be a physical disk internal to the Hyper-V server or it can be a Storage Area Network (SAN) Logical Unit (LUN) mapped to the Hyper-V server. To ensure the Guest has exclusive access to the storage, it must be placed in an Offline state from the Hyper-V server perspective. Additionally, this raw piece of storage is not limited in size so, hypothetically, it can be a multi-terabyte LUN. After storage is mapped to the Hyper-V server, it will appear as a raw volume and will be in an Offline state (depending on the SAN Policy (Figure 1-1)) as seen in Figure 1. 

Figure 1: Raw disk is Offline 

Figure 1-1 SAN Mode determination usingdiskpart.exe I stated earlier that a disk must beOfflinefrom the Hyper-V servers' perspective in order for the Guest to have exclusive access. However, a raw volume must first be initialized before it can be used. To accomplish this in the Disk Management interface, the disk must first be brought Online. OnceOnline,the disk will show as being Not Initialized(Figure 2). 

Figure 2: Disk is Online but Not Initialized 

Right-click on the disk and select Initialize Disk(Figure 3). 

Figure 3: Initialize the disk 

Select either an MBR or GPTpartition type (Figure 4). 

Figure 4: Selecting a partition type Once a disk is initialized, it can once again be placed in anOfflinestate. If the disk is not in anOfflinestate, it will not be available for selection when configuring the Guest's storage. In order to configure a Pass-through disk in a Guest, you must selectAttach a virtual disk laterin the new Virtual Machine Wizard(Figure 5). 

Figure 5: Choosing to attach a virtual disk later If the Pass-through disk will be used to boot the operating system, it must be attached to an IDE Controller. 

Data disks can take advantage of SCSI controllers. In Figure 6, a Pass-through disk is attached to IDE Controller 0. 

Figure 6: Attaching a pass-through disk to an IDE Controller Note:If the disk does not appear in the drop down list, ensure the disk isOfflinein the Disk Management interface (In Server CORE, use thediskpart.exeCLI). Once the Pass-through disk is configured, the Guest can be started and data can placed on the drive. If an operating system will be installed, the installation process will properly prepare the disk. If the disk will be used for data storage, it must be prepared in the Guest operating system before data can be placed on it. If a Pass-through disk, being used to support an operating system installation, is broughtOnlinebefore the Guest is started, the Guest will fail to start. When using Pass-through disks to support an operating system installation, provisions must be made for storing the Guest configuration file in an alternate location. This is because the entire Pass-through disk is consumed by the operating system installation. An example would be to locate the configuration file on another internal drive in the Hyper-V server itself. Or, if it is a cluster, the configuration file can be hosted on a separate cluster providing highly available file services. Be aware that Pass-through disks cannot be dynamically expanded. Additionally, when using Pass-through disks, you lose the capability to take snapshots, and finally, you cannot use differencing disks with Pass-through disks. 

Note: When using Pass-through disks in a Windows Server 2008 Failover Cluster, you must have the update documented inKB951308: Increased functionality and virtual machine control in the Windows Server 2008 Failover Cluster Management console for the Hyper-V roleinstalled on all nodes in the cluster. 

Question No. 93

You have a Microsoft Hyper-V Server 2008 R2 server. 

You need to join the server to an existing Active Directory Domain Services (AD DS) domain. 

Which should you use? 

A. ocsetup 

B. hvconfig 

C. sc config 

D. net config 



Making HVConfig work on a normal Server Core installation Microsoft's Hyper-V Server 2008 product comes with a wizard, that allows easy configuration of the Server Core-based subsystem. 

This tool can be used on normal Server Core installations of Windows Server 2008 too. This blogpost describes what files to copy from a US English Hyper-V Server 2008 installation, where to place them and how to install this wizard to auto run. All in five easy steps! 


When you're using a different language change the En-Us bit for the files accordingly: 

Step 1 

You will need to following files from a Hyper-V Server 2008 installation: 




These files are also attached to this blogpost. Check the end of this post for a download link. 

Step 2 

Copy the files to their respective location on your Server Core installation. 

Review the instructionhereto get files onto your Server Core box. 

Step 3 

Open the Registry Editor, by runningregedit.exeand browse to the following location: 


Create a new String value (REG_SZ) named HVConfig. Right click it and selectModify Datafrom the context menu. TypeC:Windowssystem32hvconfig.cmdas the data and press theOKbutton to save. 

Close the Registry Editor. 

Step 4 

Log off by typinglogoffon the command prompt. Log on using an account with administrative privileges. 

Step 5 (Optional) 

Optionally change the contents of hvconfig.vbs to display another header. 

Since we're no longer running the script on Hyper-V Server it would be appropriate to change the top banner. 

Type the following command: 

Notepad.exe C:Windowssystem32en-UShvconfig.vbs 

Now change theL_Msg005_Textconstant to something appropriate. 


You can also change the color of the screen by changing the second line in HVConfig.cmd. 

Default color is 17 

(White on Blue), but I prefer 47. (White on Red) 

Question No. 94

A company deploys Remote Desktop Services (RDS) on the following servers. 

You need to use RD Web Access to give users access to RemoteApp applications that they have permissions for. 

What should you do? 

A. Use the Remote Desktop Web Access Configuration tool to configure Server2 to use Server1 as the RemoteApp source. 

B. Use the Remote Desktop Web Access Configuration tool to configure Server1 to use Server2 as the RemoteApp source. 

C. Use the RemoteApp Manager tool to configure Server2 to use Server1 as the RemoteApp source. 

D. Use the RemoteApp Manager tool to configure Server1 to use Server2 as the RemoteApp source. 

Answer: B

Question No. 95


A company uses Windows Server 2008 R2 Domain Name System (DNS). You are configuring Remote Desktop (RD) Connection Broker load balancing. You add the necessary DNS entries for each RD Session Host server. 

RD Connection Broker load balancing is not working. 

You need to ensure that the Remote Desktop sessions are load-balanced across the RD Session Host server farm. 

Which server option should you use? (To answer, select the appropriate setting or settings in the answer area.) 


Explanation: Select “Enable round robin”. 

To load balance sessions in an RD Session Host server farm, you can use the RD Connection Broker Load Balancing feature together with Domain Name System (DNS) round robin. To configure DNS, you must create a DNS host resource record for each RD Session Host server in the farm that maps the RD Session Host server’s IP address to the RD Session Host server farm name in DNS. The following procedure provides the steps to configure DNS on a Windows Server 2008 R2-based domain controller. You must be a member of the Domain Admins, Enterprise Admins, or the DnsAdmins group to complete this procedure. To add DNS entries for each RD Session Host server in the farm Open the DNS snap-in. To open the DNS snap-in, log on to a computer where the DNS snap-in has been installed, click Start, point to Administrative Tools, and then click DNS. 

Expand the server name, expand Forward Lookup Zones, and then expand the domain name. 

Right-click the appropriate zone, and then click New Host (A or AAAA). 

In the Name (uses parent domain name if blank) box, type the RD Session Host server farm name. 

The farm name is the virtual name that clients will use to connect to the RD Session Host server farm. Do not use the name of an existing server. For management purposes, we recommend that you use the same farm name that you specified when you configured the RD Session Host servers to join a farm in RD Connection Broker. 

In the IP address box, type the IP address of an RD Session Host server in the farm. 

Click Add Host. 

Repeat steps three through six for each RD Session Host server in the farm. 

Important You must specify the same farm name in the Name (uses parent domain name if blank) box for each DNS entry. 

For example, if you have three RD Session Host servers in a farm named FARM1, with IP addresses of,, and, the entries would look similar to the following: 


Farm1 Host(A) 

Farm1 Host(A) 

Farm1 Host(A) 

When you are finished, click Done. 


By default, DNS round robin is enabled when using DNS on a 

Windows Server 2008 R2-based domain controller. The Enable round robin setting is available on the Advanced tab when you view the properties of the server in DNS. 


Question No. 96

You are using Microsoft System Center Virtual Machine Manager (VMM) 2008 R2 to perform a virtual-to-virtual (V2V) conversion. 

You need to place the virtual machine (VM) on the host server that has the most available disk I/O. 

Which two actions should you perform? (Each correct answer presents part of the solution. Choose two.) 

A. Set the placement goal to Load balancing. 

B. Set the placement goal to Resource maximization. 

C. Set the resource importance of the disk I/O to Very Important. 

D. Set the maximum disk I/O per second for the host reserves to 10000. 

Answer: AC 


Using Host Ratings to Select Hosts 

You can establish customized default criteria for VMM to use when rating hosts during placement. This helps you to place virtual machines on the most suitable host. You can specify the placement goal that VMM should use to calculate hosts ratings. The placement goals are described in the following table: 

You can also specify the relative importance of each of the following resources that VMM should use when rating hosts: 

CPU utilization 

Memory utilization 

Disk I/O 

Network utilization 

For example, if you create a Windows Server2008-based virtual machine for developers and you know that the virtual machine requires significant CPU, however the host has relatively little hard disk or network resources, you might customize the default ratings to increase the priority of free CPU while lowering the priority of the hard disk and network. 

Setting Host Reserves 

Host Reservesdefine how much of a host's resources are to be reserved for the host operating system. Once these reserves are configured, a virtual machine cannot be deployed on that host if doing so would require the use of those reserved resources. The host resources that may be reserved are as follows: 

CPU Percentage 



Space Maximum Disk I/O Per Second (IOPS) 


Host reserves are specified on a host group basis. In addition, the group reserve settings may also be overridden on a per host basis. To specify the host group reserve settings, right click on the host group name in the Hosts pane, selectPropertiesfrom the menu and click theHost Reserve Tabsin theHost Group Propertiesdialog as illustrated in the following figure: 

In order to override the group host reserve settings, right click on the host in the list, selectPropertiesand click onReservesin the resulting dialog.