Thursday, July 14, 2016

How to implement Azure RemoteApp (ARA) for business (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 :-)

No comments:

Post a Comment