Using App-V Remote Desktop Services does not differ much from a normal App-V deployment.
The only component which needs a special installation is the App-V Client, which uses different installation binaries, Microsoft Application Virtualization Client for Remote Desktop Services. The rest of the roles, App-V Management Server (including the Management System and Data Store), Streaming Server, and App-V Sequencer are exactly the same as seen earlier.
To achieve a proper co-existence for these two platforms there are some important matters you should consider and take note of before the implementation - here's a short review.
RDS has the same deployment process for the App-V applications, but the environment where you will be working is not the same as seen earlier. So here are some of the points you should consider:
Consider using a network location for the "User-specific Data Location" option. This is where App-V stores the changes made in the application packages for each user.
The default option is the
AppData
folder of the user's local profile. But if the scenario is using mandatory profiles, all of these changes will be lost and the App-V redirection will be the best approach.Keep in mind that with this redirection it is highly recommended to use a network location near the clients, to optimize the use of bandwidth and maintain an acceptable user experience.
Consider shared read-only cache for App-V for minimizing disk impact in VDI environments. In the App-V client installation you can set a common shared cache directory for App-V packages.
Of course if you are using mandatory profiles and you do not have AppData redirection, this will not add any benefit as the changes in the profiles (including AppData) will not persist and you won't have to worry about profile size.
More information about how to configure this option is available in the How to Configure a Read-only Cache on the App-V Client article at http://technet.microsoft.com/en-us/library/ee956915.aspx.
Cache pre-load is usually a good approach in a RDS environment.
Highly recommended to standardize the RD Session Host settings across your server farm, maintaining the same configurations on all the servers as much as you possibly can.
Microsoft provides a very complete and interesting table about some considerations you should evaluate when you are analyzing the application delivery methods to the Remote Desktop Servers.
You can find the complete reference in the App-V Remote Desktop Services document available from the Microsoft Download Center at http://www.microsoft.com/downloads/en/default.aspx.
Deployment method |
Supports user publishing |
Supports computer publishing |
Upgrade process |
Preload App‑V Cache Capability |
---|---|---|---|---|
Full Infrastructure w/ RTSP(s) |
Yes |
No |
1. Version updated on App-V Management Server. 2. RD Session Host server placed in maintenance mode. 3. First open of package will upgrade. |
No |
Full Infrastructure w/ HTTP(s) or File Streaming |
Yes |
No |
1. Version updated on App-V Management Server. 2. RD Session Host server placed in maintenance mode. 3. Publishing refresh. 4. First open of package will upgrade. |
No |
Stand Alone Client (MSI) |
No |
Yes |
1. RD Session Host server placed in maintenance mode. 2. New version of package MSI executed. |
Yes |
SCCM 2007 R2 |
No |
Yes |
1. RD Session Host server placed in maintenance mode. 2. Configuration Manager 2007 R2 advertisement executes. |
No |
SFTMIME |
Yes |
Yes |
1. RD Session Host server placed in maintenance mode. 2. Updated package published with SFTMIME. |
Yes |
An interesting note to remember about application publishing is that when you are working with RDS, if you are using computer publishing, the applications will be available for all users that are connected to the RD Server. User publishing will provide the granular permissions that are commonly necessary for most environments, only giving access to applications to the right RD clients.
Once you have considered all the options for an App-V deployment with Remote Desktop Services, it is time to install the App-V Client in the RD Session Host.
Installing the App-V client has no differences to any other application installed on a Remote Desktop Session Host, which must be set in install mode.
In the RD Session host, access Control Panel | Programs, and click Install Application on Remote Desktop Server.
A wizard will appear, click Next.
In the next window, insert the path for App-V Remote Desktop Services Client installation file and click on Next.
Follow the installation wizard for App-V, completing the configurations needed.
Once the installation is complete click on Finish and the App-V RDS Client will be installed.
As you have seen earlier, RemoteApp publishes any normally installed program to clients; App-V applications do not fit in the normal environment for RDS. That's why if you are seeking deployment of App-V packages using RemoteApp, it will require some extra configuration.
This example will be using the DefaultApp provided by App-V.
Publish the application to the RD Server.
Make sure you have copied the EXE or DLL file where the application stores the icons used (available in the
Icons
folder for the virtual package). It is necessary to link each virtual application with the appropriate icon.Access the properties from one of the shortcuts shown by the virtual application and copy the application name. The complete name + version used appears right after the
/launch
parameter.In this case, it is
DefaultApp
MFC
Application
1.0.0.1
.Open the RemoteApp Manager console and click on Add RemoteApp Programs.
A new wizard will appear, click Next in the welcome page.
In the next window, click on Browse to select the application path. Search for the Application Virtualization Client folder located in
Program
Files
.Click on Properties. Complete the name and alias for the application.
Select Always use the following command-line arguments option and insert:
/launch
"Application
Name"
(paste the value copied in step 3).Use the Change Icon option to select the proper icon for the application. For that, you will need the EXE or DLL file copied earlier. Click OK.
In the RemoteApp wizard click Next and in the last step, click Finish and you will be done.
With that, all you need to do is deploy the application using an
.rdp
or MSI file, or just access it from a web browser. This example will be using the last option.From a RD Client, access the web portal for Remote Desktop Services and you should see the DefaultApp available.
Clicking on it will give you access to the application as if it were deployed locally.
Even more, you can verify that the App-V Client is being used from the RD Server (in the server name is
w2k8-rds.aalvarez.ad
) just by verifying the existing connection in the tray bar.
Using RemoteApp to publish App-V streamed applications does not involve a complex configuration, but it always needs some manual execution, making this not the most scalable solution available.
But if you deployed App-V packages using SCCM 2007 R2 or an MSI, these particular steps are not necessary, as the application should already be available for selection in the RemoteApp wizard.