As mentioned earlier Windows Server 2008 R2 Remote Desktop Services includes the possibility of a centralized deployment of applications, called RemoteApp.
RemoteApp programs are applications installed on a RDS server, from which you can publish them to clients. Users can also access these applications from their computers, seemingly as locally installed applications. RemoteApp is integrated directly into the user's desktop, running in a local window and with its own entry in the taskbar.
As for App-V, RemoteApp applications can run with other applications on the client's machine with no conflicts or incompatibilities. You can access RemoteApp applications from the Start menu (already published by an administrator), from an MSI file, or using .rdp
(Remote Desktop Protocol) files, also created and distributed by an administrator.
Using RemoteApp doesn't need much expertise or a large hardware installation. RemoteApp is included, obviously, in the Remote Desktop Services role in Windows Server 2008 R2.
To install this role, all you need to do is add it from the Server Manager console.
If you are using a simple configuration for RDS, all you need is the Remote Desktop Session Host service which will be in charge of handling client desktops and published applications.
Additionally, you can use the Remote Desktop Web Access service (also requires IIS) to facilitate users' access to their resources from a web browser. This could be really useful if you want a Citrix-like remote access environment.
Similar to the App-V Full Infrastructure model, you can configure the users and user groups to be granted access to the resources that will be published.
Adding and configuring simple applications can be done from the RemoteApp Manager console, which does not support complex configurations. And user's access can be via an .rdp
or MSI file, or through using a web browser.
This example accesses PowerShell via a web browser.
For a complete guide to using RemoteApp, have a look at the Deploying RemoteApp Programs to the Start Menu by Using RemoteApp and Desktop Connection Step-by-Step Guide article at http://technet.microsoft.com/en-us/library/dd772639(WS.10).aspx.
After reading this quick overview about RemoteApp, it sounds like it has all the features that we can find in virtualized applications using App-V, so what are the differences?
RemoteApp |
App-V |
---|---|
Installed on RDS server, published to clients |
Sequenced on a similar desktop machine, delivered to clients |
Using remote resources (memory, processor, and so on) |
Using local resources |
Requires a server hosting the application |
Does not require any server, just the package you want to deliver |
No possibility of using offline applications as you need an active connection to a server |
Can be used for offline deployments |
You need two servers if you want to publish incompatible applications using RDS (that is, Office 2007 and Office 2010) |
You don't need any servers, just the sequenced applications |
Published applications do not need compatibility with the client operating system |
Applications should be captured and deployed in the same type of operating system |
Without a question both technologies, RemoteApp and App-V, can save a lot of time and money. But before deciding on either of these two you should evaluate, plan, and design the best approach for your environment, considering that you can combine App-V with RDS and RemoteApp.