1 / 22

Microsoft Server 2008 R2

Microsoft Server 2008 R2. Remote Desktop Services. Remote Desktop Services. Remote Desktop Services Remote Desktop Session Host RemoteApps Remote Desktop Protocol Hardware Roles Users. Remote Desktop Services. Who needs Remote Desktop Services (RDS)?

libby
Download Presentation

Microsoft Server 2008 R2

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Microsoft Server 2008 R2 Remote Desktop Services

  2. Remote Desktop Services • Remote Desktop Services • Remote Desktop Session Host • RemoteApps • Remote Desktop Protocol • Hardware • Roles • Users

  3. Remote Desktop Services • Who needs Remote Desktop Services (RDS)? • Can be used to allow users to run Windows-based applications on a remote server from the computer • Hosting server is called a Remote Desktop Session Host (RD Session Host) • Users can also access a full desktop using this method. (standard method in 2003 and prior)

  4. Remote Desktop Services • What can you do with RDS? • Deploy and manage applications on RDS servers rather than on hundreds of client computers • Provide applications to end users who you cannot easily support because they are in remote offices • File based applications • Removes need for dedicated server

  5. Remote Desktop Services • What can you do with RDS? • Reduce impact of client hardware failures by keeping applications on a central server. • Plug new computer in and back in business • Avoid configuring or mis-configuring computers • Extend the lifetime of existing client hardware • Use computers/thin clients in environments that are not so computer friendly • Simplify helpdesk support

  6. Remote Desktop Services • Thin client/Server based networking • Application processing is done at the server, not the client. • All processes/instructions are run by the server: • Video • Mouse clicks • Keystrokes • Mainframe born again? • Not quite…but close

  7. Remote Desktop Session Host • Centralized application deployment • Install application once on a RD Session host. • Supporting remote users • Performance isn’t impacted by poor connections • Allows for more users to work from home

  8. Remote Desktop Session Host • PC unfriendly environments • Install thin clients or older PCs • Reduces the exposure due to theft • Extend hardware refreshes • PC is simply a window or interface to the RD Session host server • Utilizes the power of the server and not dependent upon the processor/RAM of workstation.

  9. Managing RDS • Remote Desktop Session Host

  10. Hardware • Server—bigger is better • Calculate the resources needed for OS • Calculate the resources for a small number of sessions • Multiply resources by total number of sessions • Add to the resources needed for the OS

  11. Hardware • Server—bigger is better • Processor—faster is better, but caching is more important…choose caching over speed • Memory—high speed error-correcting memory and a lot of it. A lot depends on the apps you will be running…C.A.D. v. Notepad? • Disk—SCSI or SAS • Network—load balancing (TEAMING) NICs

  12. Roles • Not all are required • RD Session Host—enables server to host Windows-based programs. This service is required • RD Virtualization Host—integrated with Hyper-V to allow users to connect to a virtual machine on a server hosting Hype-V. Can allow users to connect to their own VM and allows users to run multiple OS’s. • RD Licensing—manages the client access licenses that are needed to connect to the session host. 120 day grace period w/out licenses. • RD Connection Broker—load balancing • RD Gateway—allows users to connect o host servers and remote desktops over the Internet. Requires IIS, NP and Access services, RPC over HTTP proxy and RSAT. • RD Web Access—allows users to connect through browser. Requires IIS and RSAT.

  13. Users • You will be prompted to select a group of users for RDS • These users will be added to the Remote Desktop Users Group • Required to be a member if accessing the RD Session host • Administrators are added by default • Two groups exist. Domain and local. Users must be added to the local group on session host.

  14. Managing RDS • Group Policy

  15. Managing RDS

  16. Remote Desktop Protocol • Display protocol • How RDP works • Downloads instructions and renders the video from the server to the client computer • Demands are reduced by using a feature called client side caching • Client remembers images that have already been downloaded • Only changed parts or the screen are downloaded • Screen does have a refresh rate

  17. RDS Protocol Configuration • Remote Desktop Session Host

  18. RDS Protocol Configuration

  19. RemoteApps • Deploying RDS Applications • Application is installed/running on RD Session Host server • Appears as if it is running on the end users desktop • This was not available in previous versions of Terminal Services. Introduced in Server 2008

  20. RemoteApps • Remoteapps can be accessed by the following (Quiz/Exam): • Web browser—requires RD Web Access • RDP file • Start Menu/Icon—can be installed using a .MSI file

  21. RemoteApp

  22. Resources • http://technet.microsoft.com/en-us/windowsserver/ee236407 • http://technet.microsoft.com/en-us/library/dd772639(WS.10).aspx

More Related