Hardware optimize

10 reasons why Windows Terminal Services is becoming more popular

Windows Terminal Services has recently been enjoying a resurgence. Brien Posey offers his thoughts on why that's happening.

Windows Terminal Services (which was renamed Remote Desktop Services in Windows Server 2008 R2) has been around for many years. But lately, I've seen an increase in the number of organizations that use it. Here are a few reasons why.

Note: This article is also available as a PDF download.

1: The hardware has finally caught up

When Terminal Services debuted with Windows NT, server hardware was hard pressed to support multiple server sessions. Furthermore, 10 Mbps networks were still the standard at that time and could easily become saturated by network-intensive applications, such as Terminal Services. Today, server hardware is far more powerful than it has ever been, and running multiple operating system instances on a server is the norm. Today's servers are well equipped to handle the demands of hosting Terminal Service sessions.

2: Windows Server 2008 R2 offers a full VDI solution

Windows Server 2008 R2 allows administrators to deploy a full virtual desktop infrastructure (VDI) solution. This means that the terminal server can be configured to host virtual desktop operating systems. When users log off, any changes they made are rolled back, and the virtual hard drive is left in a pristine condition, ready for the next user.

3: You can create dedicated virtual desktops

Normally, a virtual desktop pool is designed so that every virtual desktop within it is identical. Because users are not allowed to make changes to the virtual desktop, each VDI session begins with a pristine virtual machine. Although this technique works well, the business needs of some organizations require users to be able to make certain changes to their desktops. In these types of situations, Windows Server 2008 R2 allows you to dedicate a specific virtual desktop to an individual user. That way, the user has his or her own virtual desktop to configure as needed.

4: You can host individual applications rather than entire sessions

One of my favorite new features in Windows Server 2008 is RemoteApp. RemoteApp allows you to virtualize individual applications, as opposed to virtualizing an entire desktop. Not only is this approach less resource intensive for the server, it allows administrators to centralize application management without having to commit to a full-blown thin client environment.

5: Desktop hardware has a longer lifespan

The economy has seen better days, and everyone is looking to make the most of their IT budget. By using Terminal Services, organizations can squeeze more life out of their desktop computers. Because all the processing occurs at the server end, the desktops are essentially acting as dumb terminals. This means that using existing desktop hardware remains a viable option for much longer than it would if applications were run locally. Likewise, running applications on a terminal server may allow organizations to purchase lower-end desktop hardware than they otherwise would, resulting in cost savings.

6: Users can access their "work computer" from anywhere

Supporting users who need to work from outside the office is nothing new. But if you've ever supported remote users, you know that keeping mobile computers up to date can be challenging. And if they use one computer at work and a different computer away from the office, they may be less productive when working remotely unless the two computers are configured identically. Implementing a Terminal Services environment allows remote users to have a consistent experience regardless of whether they are working in the office or on the road.

7: Application maintenance becomes easier

In a Terminal Services environment, applications are installed on a terminal server rather than on individual desktops. As a result, application patching becomes much easier because there is only one copy of each application. You no longer have to make sure that application-level patches are applied to every desktop in the organization. It is worth noting, though, that each desktop retains its own operating system, which must still be kept up to date.

8: Desktop PCs have a smaller attack surface

Because Terminal Services involves applications or desktop sessions that are centrally hosted, there's no need to install applications on individual desktops. This helps to reduce the attack surface of the desktops in your organization. Typically, the desktop computers will require an operating system, some antivirus software, and a Terminal Services client (which is included with Windows). Everything else can be run on the server.

9: Desktop provisioning becomes easier

Once an organization has adopted Terminal Services, desktops can be configured to run a minimal configuration. This makes the process of provisioning desktops a lot easier. Image files become smaller and can therefore be deployed much more quickly, and the issue of application compatibility testing (at the desktop level) goes away.

10: You may be able to give up your desktop management software

I have seen at least one real-world example of an organization that decided to give up its desktop management software after implementing Terminal Services. It had purchased the desktop management software primarily to maintain hardware and software inventories across the organization. Because the vendor required an annual maintenance contract, ongoing costs were associated with using the software. Switching to a Terminal Services environment eliminated the need for software management at the desktop, thereby allowing the organization to reduce expenses by getting rid of its desktop management software.

About Brien Posey

Brien Posey is a seven-time Microsoft MVP. He has written thousands of articles and written or contributed to dozens of books on a variety of IT subjects.

11 comments
AG4IT
AG4IT

Windows Server 2008 R2 RDS is certainly a significant improvement over previous versions of Terminal Services. Ericom Software has released special, free version of PowerTerm WebConnect which enhances Windows Server 2008 R2 Remote Desktop Services at no extra cost. Among the benefits of PowerTerm WebConnect for WS08 R2 are: - Simplified deployments of Microsoft Windows Server 2008 R2 Remote Desktop Services, supporting a larger number of applications and users - Centralized configuration, management, monitoring and control - Logging, auditing and more Download the free version of WebConnect for WS08 R2 at: http://www.ericom.com/WS08_R2.asp?URL_ID=708 Adam

Digit3c
Digit3c

Remote desktop has indeed brought a revolution in modern computing. I even use my Windows Mobile to run Terminal Service Client service to build my productivity when I am AFK or commuting..kudos to high speed internet connection we enjoy today!

iPadforHumans
iPadforHumans

As usual, Brien has raised a lot of the points that people look for clarification of in a helpful and concise way. 1. FOLLOW-UP. I'd like to see a part two of this column. Unfortunately most of the Microsoft presentations on this capability have a laundry list of servers you need with no translation from the old name to the new name. Also Microsoft Marketing and their attempt to bundle/sell ForeFront security clouds what could be a much improved simple picture. If Brien is interested, please clarify: What are the equivalent / differents between the traditional Cisco and Microsoft capabilities to support remote IPSEC tunnels from approved users on Windows XP or Vista or W7? What is the minimum needed to add this new VDI to existing Windows 2003 Server Active Directory Native Mode environment? 2. CONTRAST AGAINST OTHER SOLUTIONS: All in all, the existing solution works like a charm, but requires skills to setup: Provide a side-by-side list of what's needed and the many new Microsoft names to replace the (simpler?) old standby configuration of: - Secured website on your DMZ to give out a wizard for non-technical employees to install Connection Wizard on their remote PCs where secured IIS only allows user to authenticate locally user to see download page. - Prep work to create Connection Wizard executable per platform for easy VPN (L2TP-over-IPSEC) tunnels. Windows XP wizard required Server 2003 to build; Windows Vista x86/x64 required Server 2008 SP2 to build; WIndows 7 requires Server 2008 R2 (?) and so on. - Cisco firewall accepting incoming remote user VPN connections using LT2P-over-IPSEC and providing IP range for the single VPN group (limitation in PIX 8.x, not quite fixed in ASA as Cisco wanted to sell SSL-based less secured alternative). - Microsoft IAS server that the Cisco firewall authenticates each access to in a secured / VLAN'd network connection (possibly to inner DMZ network) - Active Directory groups to contol who has VPN access, etc. - Cisco core switch VLANs as well as Firewall VLANs, DMZ switch VLANs, VMware virtual switch VLANs / vNIC connections (or Hyper-V equivalents) to keep everyone honest that is accessing your network. - In the under 10 seconds it takes to make the connection described using the resources above, as one replyer pointed out, currently a Citrix XenApp environment would be the next stop for those that enterprise policies prevent RDC connections to their desktops or a pool of virtual machine desktops. So, Brien, great articles, I always read your columns, and maybe you can provide the road map to adding the new Microsoft WDC capabilities so the Apps only or desktops can be done without Citrix or VMware VMview alternatives. Best regards, Larry Larry Timmins larry.timmins@gmail{-.remove.-}.com

rsquaredg
rsquaredg

I want to run RDP on my iPad to access VDI sessions on Terminal Services 2008R2!

djlightbulb
djlightbulb

I personally admin my home server with iRDesktoP, a free little RDP client for iphone.

iPadforHumans
iPadforHumans

Remote Desktop connections using the built-in L2TP-over-IPSEC protocol have been demonstrated by a number of vendors including as far back as VMworld 2009 (Sept). It's a bit pricing, buy Wyse Terminal have a "cloud" application available for download to iTouch, iPhones. It was a bit small screen-wise, but designed to give administrators a way to get in to their environments securely from "anywhere". If the resolution scales up to the iPad (haven't tested it yet), there might actually be some value there for the money (~$30). Good luck, Larry Timmins eVangelist of Distant Computing

rsquaredg
rsquaredg

Hi Tim, I've tried the Wyse product on the iPod and it works well except as you point out the small screen. Problem is finding a client that can connect to Terminal Services 2008R2. According to MS only MS clients running IE8 are able to perform this feat...

Pete6677
Pete6677

Overall cost is HIGHER in an average user situation, as the dumb terminal hardware will cost as much if not more than a PC. Plus you still need a desktop PC for some applications that won't run well in a virtual environment. Every time a discussion comes up about network computers, virtual desktops, or whatever the current euphemism is for dumb terminals, I just tune it out. They will never make sense, so long as hardware keeps getting cheaper and networks remain unreliable.

dmeireles
dmeireles

Citrix always had a big role in Windows Terminal Services. Their application delivery solutions (running on top of RDP) leverage the value of RDP and its flexibility. A must have, I must say, to take the best of your RDP environment.

pethers
pethers

Citrix is only of value in certain industries with specific requirements that will improve the performance over plain old Terminal Services. I think in many office environments citrix is no longer required due to the large feature set of Windows Server 2008 R2.

dmeireles
dmeireles

Of course you'll have a performance increase using the ICA protocol, but that's not all the story. Publishing single applications instead of full desktop sessions and other fancy things, they still increase the value of Terminal Services. Of course, there is a price to pay indeed, but in the long term, the scalability and ease of manage pays off.

Editor's Picks

IT Buying Cycle

Learn more