In an earlier blogpost I explained Azure RemoteApp (ARA) functionality and to publish native and virtual (App-V) applications. Now the story continues with some other device experiences. Therefore I installed the Remote Desktop client on a Windows 10 Mobile, Android phone and iPad 3 device. Let's have a look again.
ARA can be used on a variety off devices. Sounds like a cool scenario to use Windows applications on multiple devices.
On a Windows 10 Mobile you need to install Remote Desktop client and logon. As easy as that. All applications published can be started within a RDP session.
On iOS (iPad) you need to install Remote Desktop client and logon. As easy as that. All applications published can be started within a RDP session.
Besides of the Azure RemoteApp RDP client and Windows 10 Remote Desktop client, you can use the Windows Azure RemoteApp website as well. That's the third option I found to access published applications.
Hope there will be still some development on ARA policies (you won't want to use "Save as" on the RDS host within applications), publish specific applications to users and/or groups, and ugly logon screen during logon.
Hope you like my posts so far on ARA functionality!
Check earlier blogposts:
Azure RemoteApp Part 1 and Part 2
In an earlier blogpost I explained Azure RemoteApp (ARA) functionality and to setup a virtual machine. Now the story continues with a new ARA collection, build on the virtual machine template created earlier. After that applications are published to make them available.
Steps to take:
Create a new ARA collection. You can choose between:
-Cloud based: Create and manage RemoteApp collections running in Windows Azure.
-Hybrid based: Create a hybrid deployment of RemoteApp that uses VNet to connect to your on-premise infrastructure.
The virtual machine template created earlier must be available now.
Choose the new template created and continue. As you can see it's not that hard to create a new collection. This will take even more time now, so be patience again ;)
When done choose "Configure user access" and "Publish RemoteApp programs" to make them available to end users.
Both native and virtual (App-V) applications will be published now. Just select the ones to publish to end users.
Once the applications have been published and user access has been configured, you can then download the Azure RemoteApp RDP client (or use the Windows 10 Remote Desktop client instead).
After you have been authenticated, you will see your published applications (both native and virtual applications) assigned and published to the user. You can then begin to test virtual application behavior in Azure RemoteApp.
They will be added to the local start menu automatically, which is very cool if you ask me :-) Applications are integrated seamless, where you cannot seen if they are installed locally, or added by ARA. No locally installed App-V client is needed as well.
Check the Roadmap too:
-What's coming in Azure RemoteApp
And remember: with added value like the "Ability to publish individual applications to specific users" it will be even better :-)
For a customer environment it was needed to offer applications to local devices, without using a local infrastructure. Because Microsoft Cloud is the way to go, I was thinking about Azure RemoteApp (ARA). Let's have a look at the solution and how to implement it for offering applications. It is not that hard to setup.
ARA helps employees stay productive anywhere, and on a variety of devices (Windows, Mac OS X, iOS, or Android). Your company’s applications run on Windows Server in the Azure cloud, where they’re easier to scale and update. Employees simply install Remote Desktop clients on their (Internet-connected) PC, Mac, tablet, or phone and then access applications as if they were running locally. Sounds easy isn't it?
Pro's and cons:
-ARA is available in the old Azure portal only (for now). It will be available in the new Azure portal later this year.
-Applications within a single collection can be offered to specific users or groups only. Not possible to divide them to different users or groups. This will be available in the new Azure portal later.
-Deploying virtual (App-V) applications within ARA isn't supported by Microsoft. It is working, but not a recommended option. This will be supported in future in the new Azure portal.
-Deploying virtual (App-V) applications within ARA is supported in hybrid collections only. When using cloud collections this isn't the case. It is working, but not a recommended option.
Steps to take:
-Open the Azure portal, go to virtual machines and create a new "Windows Server Remote Desktop Session Host" from template. Choose the configuration wanted and wait for it to complete.
-The applications needed can be installed native or may be virtual (App-V) as well. Make sure the App-V Client for Remote Desktop Services is installed too, when App-V packages are used.
-To register App-V packages for later usage, use the following command(s): Microsoft TechNet. Don't start them yet, otherwise delete data in the local VFS Folder (%LOCALAPPDATA%\Microsoft\AppV\Client\VFS) for sure.
When ready start ValidateRemoteAppImage.ps1 on the desktop. This script will check for errors and start Sysprep afterwards. The virtual machine will be stopped afterwards.
Choose to capture the virtual machine afterwards (Capture button).
Go to RemoteApp now and "Add a new template image". The virtual machine captured before must be available now. This will take some time, so be patience ;)
That's it for now. In a next blogpost I will continue creating a new ARA collection, and publish some applications.
Check weblinks:
-Using App-V apps in Azure RemoteApp
-Create a Azure RemoteApp image based on an Azure virtual machine
-Capture an image of an Azure Windows virtual machine created with the classic deployment model
-App-V: On App-V Applications Hosted in Azure RemoteApp
Update 14-7: Change on virtual (App-V) applications. Thanks to @ArjanVroege and @fberson for comments.
