• Save
10215 A 13
Upcoming SlideShare
Loading in...5
×
 

10215 A 13

on

  • 786 views

 

Statistics

Views

Total Views
786
Views on SlideShare
786
Embed Views
0

Actions

Likes
0
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Module 13: Desktop Virtualization Using Remote Desktop Services Course 10215A Presentation: 60 minutes Lab: 60 minutes After completing this module, students will be able to: Describe Remote Desktop Services (RDS). Implement the Remote Desktop Session Host. Implement the Remote Desktop Connection Broker. Implement the Remote Desktop Virtualization Host. Required materials To teach this module, you need the Microsoft® Office PowerPoint® file 10215A_13.ppt. Important It is recommended that you use PowerPoint 2002 or a later version to display the slides for this course. If you use PowerPoint Viewer or an earlier version of PowerPoint, all the features of the slides might not be displayed correctly. Preparation tasks To prepare for this module: Read all of the materials for this module. Practice performing the demonstrations and the lab exercises. Work through the Module Review and Takeaways section and determine how you will use this section to reinforce student learning and promote knowledge transfer to on-the-job performance. Make sure that students are aware that there are additional online resources for the module on the Course CD.
  • Briefly present the module ’s content. Since RDS is new with Windows Server® 2008 R2, ask the students if they have had any experience with previous versions of Terminal Services . Module 13: Desktop Virtualization Using Remote Desktop Services Course 10215A
  • Module 13: Desktop Virtualization Using Remote Desktop Services Course 10215A
  • Students may be very familiar with Terminal Services. Explain that Remote Desktop Services is the new name for the Terminal Services role. Provide an overview of RDS. Introduce the new terminologies in Windows Server 2008 R2. Describe RDS functionality, if required. Use the slide to explain the RDS role services when you discuss how RDS works. Question : In which situations would you use RDS? Answer : The answers will vary. In general, you can use RDS to allow a user to access applications from any device; run an application or an entire desktop in one location, but control it from another; centralize the deployment of applications; and provide users with flexible work scenarios, such as working from home. Module 13: Desktop Virtualization Using Remote Desktop Services Course 10215A
  • Cover the roles from Terminal Services and their new counterparts in RDS for Windows Server 2008 R2. Cover each RDS role, but from a high level, as these will be detailed later. Make sure you emphasize the similarity between some of the old names and the new ones. Module 13: Desktop Virtualization Using Remote Desktop Services Course 10215A
  • Provide an overview of the new and improved client experience features in Remote Desktop. Explain the features with scenarios. For example, when users use the VDI) solution, Aero® Glass support provides users the same experience as using local computer. Multimonitor support will be helpful when users have multiple monitors as in the banking sector, financial institutions, or if working at technical support. You can also start a discussion with the students by asking "Which of the listed improvements would be the most important for you?" Question : How can you benefit from the new Remote Desktop Client Experience features? Answer : Answers will vary, but could include use of multiple monitors, bringing sound from remote systems to the client. The Remote Desktop Client Experience features improve the experience of remote users by making the experience more similar to the experience enjoyed by users accessing local computing resources. Module 13: Desktop Virtualization Using Remote Desktop Services Course 10215A
  • Provide an overview about how RemoteApp and Desktop Connection integrate with Windows® 7 clients. Explain how the published RemoteApp applications, to which we subscribe through feeds, are available on the Start menu. Explain that RemoteApp and Remote Desktops are available only on Window 7 and Windows Server 2008 R2. Clients using older versions can access the same applications through RD Web Access or shortcuts, but they will not be integrated on the Start menu. Explain the benefits of RemoteApp and Remote Desktops, and how you can configure them. Question : When would you use RDS Web Access to access RemoteApp applications, instead of RemoteApp and Desktop Connection? Answer : RemoteApp and Desktop Connection requires Windows 7 as a client. If your client is running an earlier version of Windows operating system, you cannot use RemoteApp and Desktop Connection, but you can still access the RDS Web portal and run RemoteApps from there. The RD Connection Broker ensures that the same RemoteApps are available through both interfaces. Course 10159A Module 6: Configuring Remote Desktop Services and Virtual Desktop Infrastructure in Windows Server 2008 R2
  • 120-day grace period. A licensing server is required. Licensing server be installed on a separate computer from session host. Module 13: Desktop Virtualization Using Remote Desktop Services Course 10215A
  • Introduce the lesson content. Emphasize that this is an overview of the Remote Desktop Session Host. Module 13: Desktop Virtualization Using Remote Desktop Services Course 10215A
  • Discuss the design criteria that must be addressed, the types and number of remote programs, licensing server or servers, or what type of network level authentication will be required. Module 13: Desktop Virtualization Using Remote Desktop Services Course 10215A
  • Discuss the Remote Desktop Services Best Practices Analyzer. Make sure to cover its configuration and operation. Module 13: Desktop Virtualization Using Remote Desktop Services Course 10215A
  • Demonstration Steps Note: Installing the RD Session Host role service requires a reboot for the virtual machine. Consider completing the first part of this demonstration earlier in the presentation. Install the Remote Desktop Session Host on NYC-SVR4 1. On NYC-Host1, in Hyper-V Manager, click NYC-Host2, and connect to 10215A-NYC-SVR4. 2. On NYC-SVR4, log on as Contoso\\Administrator using the password Pa$$w0rd. 3. Open Server Manager . 4. Click Roles, click Add Roles, and then click Next . 5. On the Select Server Roles page, select the Remote Desktop Services check box, and then click Next. 6. On the Remote Desktop Services page, click Next. 7. On the Select Role Services page, select the Remote Desktop Session Host check box, and then click Next twice. 8. On the Specify Authentication Method for Remote Desktop Session Host page, click Require Network Level Authentication, and then click Next. 9. On the Specify Licensing Mode page, verify that Configure later is selected, and then click Next. 10. On the Select User Groups Allowed Access to this RD Session Host Server page, click Add. 11. In the Select Users, Computers, or Groups dialog box, type IT;Production, and click OK. Click Next. 12. On the Configure Client Experience page, select the Audio and Video playback and Desktop composition check boxes, and then click Next. 13. On the Confirm Installation Selections page, click Install. 14. On the Installation Results page, click Close , and then click Yes to restart the system. Configure the Remote Desktop Session Host 1. After NYC-SVR4 restarts, log on to NYC-SVR4 as Contoso\\Administrator , using the password Pa$$w0rd. 2. Wait for the installation to finish, and then click Close. 3. Click Start, point to Administrative Tools, point to Remote Desktop Services , and then click Remote Desktop Session Host Configuration. 4. In the Connections pane, double-click on RDP-Tcp. 5. On the Sessions tab, select the top Override user settings check box, and configure the Idle session limit to 15 minutes. 6. On the Client Settings tab, in the Color Depth section, change the Limit Maximum Color Depth to 16 bits per pixel. Click OK. 7. Under Licensing, right-click Remote Desktop Licensing mode, and then click Properties. 8. On the Licensing tab, click Per Device, and then click OK. 9. Right-click Delete temporary folders on exit, and click Properties. 10. Clear the Restrict each user to a single session check box, and click OK. 11. Close the Remote Desktop Session Host Configuration console. Run the Remote Desktop Services Best Practices Analyzer 1. In Server Manger , open Roles. 2. In Roles, click Go to Remote Desktop Services. 3. In Remote Desktop Services, in the Best Practices Analyzer section, click Scan this role. Module 13: Desktop Virtualization Using Remote Desktop Services Course 10215A
  • Consider demonstrating how to configure the RDS client connections by using each of the options. Show how you can configure the same setting by using each of the different options, and then discuss what happens if you configure the same setting in multiple places. Module 2: Installing and Configuring the Hyper-V R2 Server Role Implementing and Managing Microsoft Server Virtualization
  • Module 13: Desktop Virtualization Using Remote Desktop Services Course 10215A
  • Module 13: Desktop Virtualization Using Remote Desktop Services Course 10215A
  • Demonstration steps: Configure a RemoteApp 1. On NYC-SVR4, click Start , point to Administrative Tools , point to Remote Desktop Services , and click RemoteApp Manager . 2. In the RemoteApp Manager console, in the Actions pane, click Add RemoteApp Programs . 3. On the RemoteApp Wizard welcome page, click Next . 4. On the Choose programs to add to the RemoteApp Programs list page, select the Calculator check box, and click Properties . 5. In the RemoteApp Properties window, on the User Assignment tab, click Specified domain users and domain groups . 6. Click Add , type IT , and then click OK twice. 7. Click Next to continue, and then click Finish . Create an .msi file to deploy the RemoteApp 1. In RemoteApp Manager, click Calculator in the RemoteApp Programs pane and then click Create Windows Installer Package on the Actions pane. 2. On the RemoteApp Wizard page, click Next . 3. On the Specify Package Settings page, click Next . 4. On the Configure Distribution Package page, check Associate client extension for this program with the RemoteApp program and click Next . 5. Click Finish . Install the .msi file on a client computer 1. On NYC-CL1, click Start , and in the Search field, type \\\\NYC-SVR4\\c$ and press ENTER. 2. In the c$ window, browse to Program Files\\Packaged Programs . 3. In the Packaged Programs windows, right-click Calculator.msi and click Install . 4. Close Windows Explorer. Test RemoteApp access 1. On NYC-CL1, click Start , click All Programs , click Remote Programs and then click Calculator . 2. In the RemoteApp window, click Connect . 3. In the Windows Security dialog box, type Pa$$w0rd as the password. Click OK . 4. Verify that the application opens, and then close the application window. . Module 13: Desktop Virtualization Using Remote Desktop Services Course 10215A
  • Introduce the lesson content. Emphasize that this is an overview of the Remote Desktop Connection Broker. Module 13: Desktop Virtualization Using Remote Desktop Services Course 10215A
  • Provide an overview of the RD Connection Broker role service. Explain that this is a renaming of Terminal Services Session Broker role service. In Windows Server 2008 R2, it is now known as the RD Connection Broker. Two functionalities, reconnecting to existing sessions and distributing session load among RD Session Host servers, are very similar to previous ones. The third functionality, providing users with access to RemoteApp programs, has been extended with support for consolidating multiple RD Session Host servers and virtual desktops hosted on RD Virtualization Host servers. Question : How can you provide users a unified view and access to RemoteApps that are published on multiple RD Session Hosts servers? Answer : You need to configure RD Connection Broker to aggregate RemoteApp by configuring multiple RemoteApp sources. Module 13: Desktop Virtualization Using Remote Desktop Services Course 10215A
  • Module 13: Desktop Virtualization Using Remote Desktop Services Course 10215A
  • Module 13: Desktop Virtualization Using Remote Desktop Services Course 10215A
  • Demonstration steps: Install the Remote Desktop Connection Broker 1. On NYC-SVR4, open Server Manager . 2. Click Roles . 4. Under Remote Desktop Services , click Add Role Services . 5. On the Select Role Services page, select the Remote Desktop Connection Broker check box, and then click Next . 6. On the Confirm Installation Selections page, click Install . 7. In the Installation Results windows, click Close . Add RD Session Host computers to the Session Broker Computers group 1. On NYC-SVR4, in Server Manager, expand Configuration , expand Local Users and Groups , expand Groups , and then double-click Session Broker Computers . 2. Click Add , and in the Select Users, Computers, Service Accounts, or Gr oups dialog box, click Object Types . 3. Select the Computers check box, and click OK twice. 4. In the Enter the object names to select field, type NYC-SVR4 . Click OK . Configure the RD Session Host computers as members of the RD Connection Broker farm 1. On NYC-SVR4, click Start , point to Administrative Tools , click Remote Desktop Services , and then click Remote Desktop Session Host Configuration . 2. In Remote Desktop Session Host Configuration , right-click Member of farm in RD Connection Broker , and then click Properties . 3. On the RD Connection Broker tab, click Change Settings . 4. In the RD Connection Broker Settings dialog box, click Farm member . 5. In the RD Connection Broker server name dialog box, type NYC-SRV4.contoso.com . 6. In the Farm Name box, type ContosoRDS . Click OK . 7. Select the Participate in Connection Broker Load-Balancing box. 8. Under Select IP Addresses to be used for reconnection , select the 10.10.0.24 check box. Click OK . Module 13: Desktop Virtualization Using Remote Desktop Services Course 10215A
  • Introduce the lesson content. Explain and discuss the Remote Desktop Connection Virtualization Host. Module 13: Desktop Virtualization Using Remote Desktop Services Course 10215A
  • Introduce the VDI concept. Compare VDI with an environment where each user has an operating system installed locally. Mention the benefits of VDI, especially with all RDP improvements in Windows Server 2008 R2. Users can connect from any device and always access the same desktop. Remind students that everything that is required for the VDI implementation, such as RD Session Host, RD Connection Broker, RD Virtualization Host, and Hyper-V, is part of Windows Server 2008 R2. Concentrate on the high-level VDI overview, but do not go into too much detail. Mention related role services, and explain that more detailed information will be provided in later topics. Question : Which environments can benefit from implementing VDI? Answer : Answers will vary, because some students may have already implemented the VDI solution and others may have only heard of it. Environments that can benefit the most from VDI are those with very strict policies for user desktops, such as financial institutions where users are not allowed to customize the environment to work with confidential data that must not be stored locally. Module 13: Desktop Virtualization Using Remote Desktop Services Course 10215A
  • Discuss the main steps in connecting to a virtual desktop in VDI. Explain that the steps for connecting to personal virtual desktops and virtual desktop pools are very similar. Explain the concept, and then point out the differences in both approaches. Also point out that in a personal virtual desktop scenario, a user is assigned a personal virtual desktop by using Active Directory® Users and Computers, while the similar setting is not required if the user connects to a virtual desktop pool. Course 10159A Module 6: Configuring Remote Desktop Services and Virtual Desktop Infrastructure in Windows Server 2008 R2
  • Discuss the requirements for virtual machines that will be used as virtual desktops. Mention that a client operating system must be used for these virtual machines, and they must be Active Directory domain members. After installing the operating system, you need to perform some additional configuration tasks. You should consider Virtual Enterprise Centralized Desktop (VECD) licensing when performing additional tasks. In the next topic, you will show how VDI and virtual desktops are configured, and students will perform similar steps in the lab at this module’s end. Course 10159A Module 6: Configuring Remote Desktop Services and Virtual Desktop Infrastructure in Windows Server 2008 R2
  • In this lab, students will plan the implementation of Remote Desktop Services. Exercise 1 In this exercise, students will install and configure the Remote Desktop Session Host . Exercise 2 In this exercise, students will deploy and test access to RemoteApps. Exercise 3 In this exercise, students will install and configure the Remote Desktop Connection Broker. Before the students begin the lab, read the scenario associated with each exercise to the class. This will reinforce the broad issue that the students are troubleshooting and will help to facilitate the lab discussion at the end of the module. Remind the students to complete the discussion questions after the last lab exercise. Note: The lab exercise answer keys are provided on the Course Companion CD. To access the answer key, click the link located at the bottom of the relevant lab exercise page. Module 13: Desktop Virtualization Using Remote Desktop Services Course 10215A
  • Module 13: Desktop Virtualization Using Remote Desktop Services Course 10215A
  • Use the questions on the slide to guide the debriefing after students have completed the lab exercises. Question 1 : How will Contoso benefit from deploying Remote Desktop Services ? Answer: Contoso will benefit by reducing the number of servers to manage, by decreasing the number of service calls to answer, and by providing centralized and easy-to-manage deployed applications. Question 2: How will you restrict the user from viewing the icon for the RemoteApp program in RD Web Access? Answer: You need to use the User Assignment feature of Remote Desktop Services to restrict the user from viewing the icon for the RemoteApp program. Module 13: Desktop Virtualization Using Remote Desktop Services Course 10215A
  • Review Questions 1. Users in your organization need access to an application that must not be installed locally on the client computers. How can you provide them access to the application? Answer : You can install the application on an RDS server, and then publish it as a RemoteApp. Users can access the application through RD Web Access. You also can add a shortcut to the RemoteApp on user computers or integrate it with their Start menu, if they have Windows 7 installed. 2. Can users access published RemoteApps from the Internet or from outside the internal network? Answer : Yes, they can. Users can establish a virtual private network (VPN) connection or they can use DirectAccess, if they are Windows 7 users and if their infrastructure is configured for DirectAccess. You also can implement RD Gateway, which will enable them to securely access RDS over a public network. 3. How is the use of RemoteApp and Desktop Connection different from simply accessing RemoteApp from RD Web Access? Answer : RemoteApp and Desktop Connection will integrate published RemoteApps and Desktop Connections with the Start menu of Windows 7 computers. When using RD Web Access, you must open the Web page, and then run RemoteApps from there. 4. You installed RDS in a testing environment. After 120 days, you are no longer able to connect to the RDS server. What is the most probable reason for this? Answer : You have a 120-day grace period in which to install RD Licensing, after installing the RDS Session Host. You probably did not install the RD Licensing role service in the testing environment, and when the grace period expired, you would no longer be able to connect to the RDS Session Host server. Module 13: Desktop Virtualization Using Remote Desktop Services Course 10215A

10215 A 13 10215 A 13 Presentation Transcript

  • Module 13 Desktop Virtualization Using Remote Desktop Services
  • Module Overview
    • Overview of Remote Desktop Services
    • Implementing the Remote Desktop Session Host
    • Implementing the Remote Desktop Connection Broker
    • Implementing the Remote Desktop Virtualization Host
  • Lesson 1 : Overview of Remote Desktop Services
    • What Are Remote Desktop Services?
    • What Are the RDS Role Services?
    • Client Experience with RDS
    • RemoteApp and Desktop Connection
    • What Is Remote Desktop Licensing?
  • What Are Remote Desktop Services? The Remote Desktop Services provides access from anywhere to session-based desktops, virtual machine–based desktops, and applications RDS provides the following benefits:
    • Run an application or an entire desktop from a central location
    • Manage session-based desktops, applications, or virtual machine–based desktops on centralized servers in the data center
    • Provide users with an entire desktop environment, or with their individual applications and data
    • Provide integration of local applications and RemoteApp applications that run on RDS hosts
    • Enable secure remote access to an entire desktop, remote application, or virtual machine without users having to establish a VPN connection
    • Centrally control which RD Session hosts can be accessed, who can access them, and device redirection
  • What Are the RDS Role Services? Previous Name Name in Windows Server 2008 R2 Terminal Services Remote Desktop Services (RDS) Terminal Server Remote Desktop Session Host (RD Session Host) Terminal Services Licensing (TS Licensing) Remote Desktop Licensing (RD Licensing) Terminal Services Gateway (TS Gateway) Remote Desktop Gateway (RD Gateway) Terminal Services Session Broker (TS Session Broker) Remote Desktop Connection Broker (RD Connection Broker) Terminal Services Web Access (TS Web Access) Remote Desktop Web Access (RD Web Access)
  • Client Experience with RDS The following enhancements are available to Remote Desktop users in Windows Server 2008 R2: Windows media redirection True multiple-monitor support Audio input and recording Improved audio and video synchronization Enhanced bitmap redirection Aero Glass support Language bar redirection Task scheduler
  • RemoteApp and Desktop Connection The benefits of RemoteApp and Desktop Connection are:
    • Published Remote Desktop connections are included with RemoteApp programs
    • Changes to the published connection are automatically reflected on the user’s Start menu
    • RemoteApp programs can be easily accessed through Windows search
    • RemoteApp and Desktop Connection does not require domain membership for client computers
    • You can create and distribute client configuration files for users
    The RemoteApp and Desktop Connection feature provides a personalized view for users of RemoteApp programs, session-based desktops, and virtual desktops
  • What Is Remote Desktop Licensing?
    • RD Session host determines if a RDS CAL is required when a client connects
    • You must have at least one RD Licensing Server
    • You must configure the Remote Desktop licensing server correctly in order for your RD Session Host server to accept connections from clients
    • RDS provides a 120-day grace period before licenses are required
  • Lesson 2: Implementing the Remote Desktop Session Host
    • Planning the RD Session Host Server Implementation
    • Remote Desktop Services and Best Practices Analyzer
    • Demonstration: Configuration and Management of RDS
    • Configuring and Monitoring RDS Client Connections
    • Methods for Securing a RDS Session
    • Using RemoteApp to Deploy Programs
    • Demonstration: Deploying a RemoteApp
  • Planning the RD Session Host Server Implementation When planning the RD Session Host configuration:
    • Consider the basic hardware, software, and other requirements
    • Identify the applications that will be deployed on the server
    • Identify the number of concurrent client connections
    • Plan the server hardware configuration based on the application and client expectations
    • Perform server capacity testing
  • Remote Desktop Services and Best Practice Analyzer Remote Desktop Services BPA identifies:
    • RDS server role configuration issues
    • RDS server role operation issues
    • Issues related to all of the RDS role services
    Windows Server 2008 R2 Best Practices Analyzer can be used to compare the server role configuration with Microsoft Best Practices
  • Demonstration: Configuring RD Session Host Servers
    • In this demonstration , your instructor will show you how to :
    • Install the Remote Desktop Session Host.
    • Configure the Remote Desktop Session Host
    • Run the Remote Desktop Services Best Practices Analyzer
  • Configuring and Monitoring RDS Client Connections To configure RDS client connections: Configure the Remote Desktop Services settings in Group Policy Configure the connection settings in Remote Desktop Session Host Configuration Configure the user account in Active Directory User and Computers Modify the Remote Desktop Connection options Use Remote Desktop Services Manager to monitor and manage user connections 1. 2. 3. 4.
  • Methods for Securing a RDS Session
  • Using RemoteApp to Deploy Programs RD Remote Apps provide access to individual applications running on RD Session Host computers The benefits of RemoteApp are:
    • Enables user access to only applications and not the RD Session Host desktop
    • Applications run in individual windows on user desktops
    • Multiple RemoteApps share in single connection
    • You can configure per-user access to RemoteApps
    You can enable access to RemoteApps by:
    • Creating and distributing .rdp files
    • Creating and distributing Windows Installer Package (.msi) files
    • Publishing the RemoteApp to an RD Web Access server
  • Demonstration: Deploying a RemoteApp
    • In this demonstration , your instructor will show you how to :
    • Configure a RemoteApp
    • Create an .msi file to deploy the RemoteApp.
    • Distribute and install the RemoteApp
    • Test RemoteApp access
  • Lesson 3: Implement Remote Desktop Connection Broker
    • What Is the Connection Broker Role in RDS?
    • Installing the RD Connection Broker Role Service
    • Configuring the RD Connection Broker Role Service
    • Demonstration: Configuring a Connection Broker Server Farm
  • What Is the Connection Broker Role in RDS? The RD Connection Broker role service:
    • Allows users to reconnect to their existing sessions in a RD Session Host server farm
    • Evenly distributes the session load among RD Session Host servers in a load-balanced RD Session Host server farm
    • Provides users with access to virtual desktops on RD Virtualization Host servers, and to RemoteApp programs hosted on RD Session Host servers through RemoteApp and Desktop Connection
  • Installing the RD Connection Broker Role Service When you install the RDS Connection Broker:
    • The service is installed and enabled
    • The Session Broker Computers local group is created
    • The Remote Desktop Connection Manager tool is installed
    Install the RD Connection Broker role service in Server Manager
  • Configuring RD Connection Broker To configure a RD Session Host farm:
    • Add RD Session Host servers to the Session Broker Computers group on the RD Connection Broker server
    • Add the RD Session Host servers to the farm on the RD Connection Broker server
    • Configure a load balancing mechanism
    To configure RemoteApp sources:
    • Add the RD Connection Broker computer to the TS Web Access Computers group on the RD Session Host servers
    • Add the RD Session Host computer as a RemoteApp source
  • Demonstration: Connection Broker Service
    • In this demonstration , your instructor will show you how to :
    • Install the Remote Desktop Connection Broker.
    • Add RD Session Host computers to the Session Broker Computers group
    • Configure the RD Session Host computers as members of the RD Connection Broker farm.
  • Lesson 4: Implementing Remote Desktop Connection Virtualization Host
    • What Is the Virtual Desktop Infrastructure?
    • How Virtual Desktop Infrastructure Works
    • Deploying Virtual Machines for Virtual Desktop Infrastructure
  • What Is the Virtual Desktop Infrastructure? VDI is a centralized desktop delivery architecture, which allows you to centralize the storage, execution, and management of Windows desktops Benefits of VDI:
    • Provides access to data and applications from any device
    • Improves data security and compliance
    • Simplifies management and deployment of applications
    • Improves business continuity
    • Integrates management of physical, virtual, and session-based desktops
    • Centralizes data storage and backup
    Key deployment scenarios of VDI are persistent virtual machines and pooled virtual machines
  • How Virtual Desktop Infrastructure Works A user can connect to a virtual machined based on the VDI configured for: Personal virtual desktops
    • A user initiates the connection to the personal virtual desktop
    • The user sends the request to the RD Session Host server running in redirection mode
    • The RD Session Host server forwards the request to the RD Connection Broker server
    • The RD Connection Broker server queries AD DS and retrieves the name of the virtual machine that is assigned to the requesting user account
    • The RD Connection Broker server sends a request to the RD Virtualization Host server to start the virtual machine
    • The RD Virtualization Host server returns the IP address of the FQDN to the RD Connection Broker server
    • The RD Session Host server redirects the request to the client computer that initiated the connection
    • The client computer connects to the personal virtual desktop
    Pooled virtual desktops
    • A user initiates the connection to the virtual desktop pool
    • The user sends the request to the RD Session Host server running in redirection mode
    • The RD Session Host server redirects the request to the RD Connection Broker server
    • The RD Connection Broker server verifies whether any existing session exists for the requesting user account
    • The RD Session Host server redirects the request to the client computer that initiated the connection
    • The client computer connects to the virtual desktop pool
    A user can connect to a virtual machined based on the VDI configured for: Personal virtual desktops Pooled virtual desktops
  • Virtual Machines for Virtual Desktop RD Virtualization Host can assign each user a unique virtual machine, a personal virtual desktop, or can redirect users to a shared virtual machine pool, where a virtual machine is dynamically assigned After installing a virtual machine, you must configure the following to work with RDS:
    • Join the virtual machine to a domain
    • Enable Remote Desktop
    • Add user accounts to the local Remote Desktop Users security group
    • Allow RPC
    • Create a firewall exception to allow Remote Services Management
    • Add permissions to RDP
  • L ab : Implementing Remote Desktop Services
    • Exercise 1: Installing the Remote Desktop Session Host
    • Exercise 2: Configuring Remote Apps
    • Exercise 3: Installing and Configuring the Remote Desktop Connection Broker
    Logon information Estimated time: 6 0 minutes NYC-Host1, NYC-Host2 Host machines Virtual machines NYC-DC1, NYC-CL1, NYC-SVR4, NYC-SVR5 User name Administrator Password Pa$$w0rd
  • Lab Scenario
    • You are a server administrator at Contoso, Ltd. Your organization includes several branch offices as well as a main office. Users in many of the branch offices must be able to run applications that are running on servers located in the main office, and that access data on SQL Servers in the main office. To ensure that the users can access the applications at all times, you need to enable access to these applications by installing and configuring the RDS role services.
  • Lab Review
    • How will Contoso b enefit from implementing Remote Desktop Services ?
    • How will you restrict the user from viewing the icon for the RemoteApp program in RD Web Access?
  • Module Review and Takeaways
    • Review Questions
    • Common Issues