Last year when Azure RemoteApp was announced at a conference, I asked the speaker about support for App-V 5 sequences running on the Azure RemoteApp platform. While the speaker actually questioned my question, I wasn’t really sure if App-V sequences are supported by Microsoft.
When Microsoft states a certain configuration is not supported, then they basically state two possible scenarios:
- The scenario has been tested and it really doesn’t work, a KB article will state why
- The scenario has never been tested at all
I wasn’t able to find any statement by Microsoft, this leaves me to believe it has never been tested.
Other projects limited my time to figure it out. This was fine as long as it was in Preview which allowed me to sit it out for a bit, until now…
Recently I was asked to deliver a masterclass regarding application provisiong using Azure RemoteApp. One of the participants asked me if App-V 5 sequences could be used. One of the other trainers, Alex Sweserijnen (@AlexSweserijnen on Twitter), also started a healthy discussion with me about this feature. Since I’m more focused on application deployment than application scripting using MSI or App-V which is more Alex’ cup of tea, I am a strong believer in using App-V.
However, I am talking about App-V client in stand-alone mode because of my ConfigMgr background. I’m not so familiar with App-V streaming infrastructures. Since Azure RemoteApp is just a ‘black-box’ RDS server I see no technical limitations to run App-V 5 sequences as long as the following requirements are met:
- App-V 5 client for RDS is configured in stand-alone mode, no streaming or ConfigMgr whatsoever
- App-V 5 sequences are loaded and published prior to uploading the .vhd to Azure RemoteApp
Alex had a few small App-V 5 sequences available I could use for testing. I’d like to thank Alex for delivering them so I didn’t need to create them myself.
So I decided to find out if this scenario works. I used the following lab setup:
- 1 VM configured as an RDS Session Host server which meets the requirements mentioned at https://azure.microsoft.com/en-us/documentation/articles/remoteapp-imagereqs
- On the VM I installed App-V for RDS 5.1 in stand-alone mode
- I added and published the App-V 5 sequences delivered by Alex, I used the following cmdlet for each sequence: Add-AppvClientPackage <whatever location>\package.appv | Publish-AppvClientPackage -Global
- I shut down the VM using sysprep to prepare the .vhd for uploading
After uploading the image I created a RemoteApp collection by using the Quick Create option and I selected the image uploaded before. After taking a lunch break (provisiong takes quite some time) the RemoteApp collection was ready. So now I need publish some apps, the result is shown below:
As you can see , Azure RemoteApp is perfectly happy to publish applications sequenced in App-V 5.I adde some The next question obviously is if they will actually work. So I need to test it on my client. So let’s start my Azure RemoteApp client.
So here are my apps published. Let’s start PuTTY to see what happens.
We can clearly see PuTTY is started as a RemoteApp.
Notepad++ works fine as well.
These test results show Azure RemoteApp is perfectly happy working with App-V 5 sequences. Keep in mind that applications sequenced must be able to run in a RemoteApp (basically RDS) environment. I can answer the question with YES: App-V 5 sequences can be run on Azure RemoteApp
I was kind of expecting this result since I see no technical reason why this shouldn’t work in the first place.
Feel free to play around with this yourself. The Azure RemoteApp environment allows you to test the environment by publishing the apps to a limited set of users before publishing them to all users who need them.