Microsoft's Surface RT: Using existing Windows apps remotely
Summary: Can you run existing Windows apps on Surface RT and other Windows RT devices? If you have the right back-end infrastructure and licenses, Remote Desktop may provide a way.
Among the top free apps listed in Microsoft's new Windows Store right now are IHeartRadio, Newegg, Kindle and ... Remote Desktop.
Remote Desktop may not be sexy, but it does allow Windows 8 and Windows RT users to connect to a remote Windows PC and access resources from it. And on the Windows RT front, given its restrictions on use of almost any existing Win32 applications (other than Office 2013 Home & Student, Internet Explorer 10 and some other Microsoft-developed utilities), Remote Desktop sounds -- at least in theory -- like a great way for users to continue to use apps they already have on new hardware like the Microsoft Surface RT.
As usual with most things Microsoft, the reality is a lot more complicated. In order to use Remote Desktop and Remote Desktop Services (the renamed "Terminal Services") product, users need certain back-end infrastructure and licenses.
Here's what a Microsoft spokesperson told me regarding use of Remote Desktop and RDS by Windows RT users:
Q: Will Windows RT users, including Surface RT users, be able to run legacy/Win32 apps using Remote Desktop and RDS. If yes, how?
A: The best way is through the Remote Desktop Client, which is available through the Windows Store. When this is combined with Windows Server 2012 or Windows Server 2008 R2, Windows RT devices (including Surface RT) users can access data and easily launch apps – including legacy/Win32 apps – one of two ways:
* RemoteApp: RemoteApp grants access to line-of-business applications and data, allowing a user to easily launch apps from Windows RT devices and securely access corporate data while avoiding storing it on a consumer device, ensuring compliance requirements of the business.
* VDI (Virtual Desktop Infrastructure): This option offers a richer user experience than the above. When using Windows Server 2012 for your VDI infrastructure, additional benefits including WAN enablement, USB redirection, and better multi-touch support can be achieved. This is the best value for VDI and offers a more simplified administration for IT, with single console and full PowerShell support.
Q: How is this licensed/what are the limitations?
A: Appropriate server and client licenses are required for both of the above scenarios. To access a Remote Desktop Server for VDI or RemoteApp, you would need an RDS CAL (Client Access License) and a Windows Server CAL.
Q: What's the deal with VDA (Virtual Desktop Access) license and CDL (Companion Device License)? It seems folks using iPads and Android devices to access Windows desktops remotely also need these. Do Windows RT users need to purchase these additional two licenses in order to use Remote Desktop?
A: RT devices don’t need a VDA or CDL license when used as a secondary device for accessing remote desktops. The user still needs an RDS CAL/VDA license for their primary corporate desktop.
Q: In the description of the Remote Desktop app in the Windows Store, Microsoft mentions Remote Desktop allows users to "experience rich interactivity with RemoteFX in a Remote Desktop client." What does this really mean?
A: RemoteFX is the new branding for the user experience. Previously it referenced just the vGPU for VDI, but now also the term also includes the WAN experience, USB Redirection, etc. There’s not a GPU or Hyper-V requirement to take advantage of the improvements. And it’s not limited to just Windows 8 – a recent update provides the RemoteFX functionality to Win7 desktops as well.
Q: Anything else that might help users trying to wade through these licensing details?
A: Here are a couple of additional documents that might help:
* Windows Server RDS Volume Licensing Brief
* VDI/RemoteApp licensing information
OK. My brain hurts now. Anyone out there who has used Remote Desktop and RDS to gain access to their "legacy" apps on Windows RT hardware? Feel free to chime in with any additional caveats and lessons learned. And anyone with other questions on this, send them in through the comments and we can all try to wade through this together....
Also: If you're still wondering at this point what does and doesn't work on Windows RT, Microsoft's Windows RT "disclaimer statement" is worth a read.
Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.
Talkback
A few extra items
The second is you can always remote to any other machine that is setup for it without needing any special license. I have a work windows 7 machine at home and I can just use the surface rt to remote directly into, hook up my mouse and use the type cover, and fully develop from it wihout needing either of those licenses.
Agreed...
Yes, remote desktop works great among on-LAN machines
This doesn't solve the problem of remote access, but it does allow a Surface RT to make local WiFi access to software and applications running on the other systems. In my case, I'm not about to open up my residential firewall to incoming Internet access, so this is not going to work for roaming access to on-premise applications. I think any consumer-friendly and routine-business solutions are going to involve cloud storage, services, and supporting acess (via Surface RT or Pro applications).
Of course, a Secure Shell and even X Windows client on Surface RT might earn geek-happiness achievements.
RemoteFX in Win 8 is WAN ready
How to work around the latest nightmare MS put on your desk
http://linuxmint.com/
And how does this contribution relate
A great idea!
Visual Studio 2012?
Toad?
can you run either under Windows RT?
Running Visual Studio via remote desktop? On a tablet? That'd be pleasant.
More to the point, there are remote desktop clients for iOS and Android (and Linux). This isn't unique to Windows tablets. Good that Windows tablets also provide this feature, but only because it means comparable functionality to other tablets, not because it distinguishes Windows RT.
that's the ticket!
For businesses...
alternative
http://www.aikotech.com/thinserver.htm
Both 'Metro' and 'Desktop' Remote Desktop works in Win RT
Citrix Clients
Same old profit driven technology 'decisions' (PDTD) ...
If I buy a PROPER Windows PC or laptop (not this 1/2 PC netbook or Surface crap) ... then I simply use Remote Desktop ... to wherever I want. No vastly expensive Enterprise Windows infrastructiure crap, no vastly expensive VMWare Enterprise infrastructure crap, ... I just enter an IP address and use the computers both ends over the network, which I've already paid for by the way.
But in the MSFT REIMAGINED world ... I have to pay a second time!!
The entire play of Windows 8, Server 2012, METRO and Surface ... is based around preserving MSFT's traditional revenues.
I mention this time and time again to ZDNET bloggers, especially Mary Jo who seems to be devoid of design knowledge, ... and they don't have the intellect, objectivity or balls to include it ... not even in a footnote :-(
"Remote Desktop may not be sexy ..."
It is the killer feature, the orgasm for anyone who knows and loves Windows, computers and networking ... since XP!
"As usual with most things Microsoft, the reality is a lot more complicated."
The reality is not more complicated ... the transition from existing technology facts to MSFT corporate Profit Driven Technology Decisions ... follows Scott's 'Oh what a tanlged web we weave, when we practice to deceive'.
To make things worse we have the advert for RemoteFX ... great, MSFT have a more efficient remote protocol, ... but its going to cost you baby. Did I mention you have to have the full MSFT server infrastructure?
"OK. My brain hurts now."
I can see ... but I'm going to be sympathetic to MJF because I think she is a good REPORTER, if a useless TECHNOLOGIST ... here is the bottom line Mary Jo:
1. IP (invented 30-40 years ago) is all you need to connect two computers and run arbitrary applications atop the network. You paid for them in 2001.
2. The whole 'cloud' , 'VDI infrastructure' balony thrust on you by MSFT and VMWare ... is simply their way of maintaining their traditional revenue streams. Its your money they are taking, Ms. Notepad user.
End lesson.
Really?
And there is nothing wrong with a company selling a service that people want and making money at it.
Oh no he di'n't! =O
Ok, but Bro...
Mary Jo
Windows Server 2008 R2 doesn't require RDS Cals... or Server Cals..
So, it isn't like this is news. And.. of course it will work. As long as the applications will run on the server, they can be accessed remotely.
The question is whether it will be a good experience. The answer is probably not. 10 inch screens are TINY for using win32 apps, so it will be a stretch even on the Surface pro. The 15 inch model they say is coming will be a better option.
Microsoft's Surface RT: Using existing Windows apps remotely