Windows Server R2 VDI Series (i)-Environment brief

From today on, let's talk about the Vdi,windows Server 2012 in Windows server R2. Microsoft has overhauled VDI, and the entire deployment process has been simplified a lot, so let's take a look at how the Windows Server Deployment of VDI environments (R2)

First, let's take a quick look at our experimental topology.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/41/64/wKiom1PU-BaCwc_ZAAEktDm6o8o651.jpg "title=" VDI topology. jpg "alt=" wkiom1pu-bacwc_zaaektdm6o8o651.jpg "/>

Let's take a look at the experimental virtual machines and their corresponding roles

Server name	Role	IP Address
RDVH.contoso.com (physical machine)	RDVH (RD Virtualization Host)	192.168.10.215
RDCB.contoso.com	RDCB (RD Connection Broker)	192.168.10.211
RDWA.contoso.com	Rdwa (RD Gateway)	192.168.10.212
RDSH1.contoso.com	RDSH (REMOTEAPP)	192.168.10.213
RDSH2.contoso.com	RDSH (RemoteDesktop)	192.168.10.214
DC01.contoso.com	AD, DNS, DHCP	192.168.10.1
Router.contoso.com	Nat	192.168.10.80 192.168.1.160 (extranet address)

The above is the main framework of this experiment, the final router is responsible for forwarding external access requests, although called Router, but the match is actually NAT. Finally all the machines have been added to the domain, and logged by the Administrator user, because the virtual machine in Hyper-V is no longer able to open the virtual machine, so this experiment is assumed by the physical machine RDVH,RDVH has been separate to the disk hosting the virtual machine has enabled the Deduplication function

This article is from the IT Technology sharing blog, so be sure to keep this source http://mxyit.blog.51cto.com/4308871/1530994