Ts windows server 2008 r2 desktop virtualization

It goes too much into detail to complete describes this feature in this article, but it's worth mentioning that changes are made to several roles like the formerly Session Broker, now called RD Connection Broker for this component which I won't will mention separately.

Microsoft performed a lot of effort improving the client experience. Lots of improvements are made to the performance of multimedia components like audio and video playback. One of the big improvements is multiple monitor support. This feature is really cool and is probably the best multiple monitor solution available in the Server Based Computing product at this moment. In this new version also audio recording devices like microphones are now supported.

For the RemoteApp and also Desktop Connections can also be placed within the Start Menu of the users on their workstations. The last additions are Aero support and language bar redirection the languages settings on the server can be easily changed. One of the biggest disappointments with the release of TS Web Access in Windows was the absence of the possibility to assign RemoteApps to users or groups on the Web Access portal. Every user could start every application displayed using the Web Access.

With the new RD Web Access applications can be filtered on a user account basis. RD Gateway improvements. On the Gateway component several smaller, but useful improvements have been made, mainly based on maintenance and management of this component. The updates are Configurable idle and session timeouts, Background session authentication and authorization, System and logon messages, Device redirection enforcement , Network Access Protection NAP remediation and Pluggable authentication and authorization.

Fair Share CPU Scheduling distributes processor time dynamically across sessions based on the number of active sessions and load on those sessions by using a scheduling mechanism which is available within Windows R2. Using this mechanism performance of the user won't be affected by another user.

This is a brand new feature special for Remote Desktop Services. With this feature you can install a program on the Terminal Server just like you would install the program on a local desktop.

Ensure, however, that you install the program for all users and that all components of the program are installed locally on the RD Session Host server. Roaming User Profile Cache. This feature is actually a group policy setting which configures a maximum size for the profile directory on each Terminal Server. If the size is reached the profile, which is used least. Personally I found this not really astonishing, but more a kind of bad workaround.

Actually all profiles should be removed when the user logs off and if this is not the case I always delete such profiles when the server starts-up.

IP Virtualization. Some applications use the IP address as their unique identification to the back-end environment. In current Terminal Server environment users on the same Terminal will use logically the same IP address, so such a application cannot be offered using a Terminal Server. With IP virtualization different IP addresses can be assigned to remote desktop connections on a per session or per program basis creating the possibility to add such an application to your farm. This feature is comparable to similar solutions available in several Server Based Computing solutions like Citrix XenApp.

Automatic discovery of License Servers not supported anymore. You will need to specify the license server manually or using the Group Policy option to configure the license server for your Terminal Servers. In this article I summarized the new features and improvements Microsoft made to the formerly known Terminal Server platform.

We all definite need to get used to the new names of the roles I wonder when nobody talks about a Terminal Server anymore. Looking at the features an improvements Microsoft added lots of new and useful functionalities, which will definitely hurt some smaller Server Based Computing manufacturers. Also the addition of VDI within the default Microsoft platform is big step for the adoption of the VDI methodology, although it is just as other VDI solutions not easy to implement as I understood did not try that option yet.

In an upcoming review I will show the new features in practice soon. Home News Reviews. Additional benefits will let you:. All the other related role services have been renamed as follows:. Windows Server R2 role service name is now:. When RD Session Host is configured to provide remote access to virtual desktops redirection mode , it cannot be used to connect users to standard terminal server desktop sessions.

Remote Desktop Web Access provides a web interface with which users connect to remote virtual desktops. Once a user has selected their personal virtual desktop or a virtual desktop pool, the request is passed to the Remote Desktop Gateway, which establishes a secure connection to RD Session Host. Pre-Windows 7 clients must access personal virtual desktops directly from the RD Web Access web page. Figure 1. Look here for detailed system requirements. While it is not recommended, all of the RD role services can be installed on one machine; however, in a production environment, it would be best to dedicate a separate physical box for the RD Virtualization Host role service at a minimum.

Log in as a domain administrator and install the role services using PowerShell, which can be launched from the taskbar or by typing PowerShell into the Search programs and files box on the Start menu. First, add the RDVirtualization Host role service:. Figure 2. The RD Session Host server can be automatically configured for redirection mode, which is required for VDI, by unchecking the Do not automatically configure box see Figure 3. Figure 3. To provide authenticated users access to virtual desktop pools or their assigned personal virtual desktops, RD Web Access must be configured manually to use an RD Connection Broker.

Internet Explorer will open. Sign in using a domain administrator user name and password. You can then sign out see Figure 4. Figure 4. Continue clicking through the Configure Virtual Desktops Wizard until you reach the summary on the last page see Figure 5.