by
Brian Madden
Microsoft just updated their TS Application Analyzer, a free tool that analyzes EXEs to help figure out whether they’ll work on a Terminal Server (or how much effort will be required to get them to work). But that got me thinking: With the new features of Windows 2008 R2 like per-session and per-app IP addresses, multi-session Microsoft Installer compatibility, and CPU fair share technology, is application compatibility still a major problem for Terminal Server?
I don’t even mean in a “Terminal Server versus VDI” context. Instead, I’m thinking back to the old days where we would dread looking at a customer’s app list because we knew a third of them wouldn’t run on TS. But now it seems that those days are largely behind us. Even in the rare case where an app doesn’t work on TS, we can easily virtualize it with one of the many app virtualization products on the market. (Although not with Microsoft’s own App-V, ironically. Yes, Windows Server 2008 RS is x64 only (which means the “current” version of TS is x64 only). Unfortunately App-V is still only 32-bit (although an x64 version is currently in beta).
So what do you think? Does terminal server still have app compat issues that limit its usefulness? Or are those days behind us now?
(Note: You must be logged in to post a comment.)
If you log in and nothing happens, delete your cookies from BrianMadden.com and try again. Sorry about that, but we had to make a one-time change to the cookie path when we migrated web servers.