Hey, here’s Martin with a Blogpost about the common mistakes when you do your first Azure Remote App Deployments.
First, you can try this for free, just create a new Azure subscription, or add the Trial period to your existing: http://azure.microsoft.com/en-us/pricing/free-trial/
One word about licensing
When you consider to stretch your period with a paid license, Keep in mind, that you will be billed for twenty account, even if you only have activated one:
Virtual Network (Azure Site-To-Site VPN)
Keep in mind, that there is no Connection between the normal Site-To-Site VPN to Azure and the RemoteApp Virtual Network. This means, you don’t have to create a normal Site-To-Site VPN to Azure, when you want to connect your RemoteApp Collection to your On-Premise Services like SAP or so. But you have to create a Virtual Network in the RemoteApp Section of the Azure Portal:
In the lower section of the Portal, click on Create, and the following wizard appears, where you have to Name the VLAN, and choose a proper Region (this will be used later for uploading your template):
Afterwards, you have to define the Network Addresses for the VLAN, and for your Local Network:
The last Screen of the wizard asks for the DNS Servers for your Network, and the VPN Device IP, which has to be a public IP obviously, and IPv6 Addresses are not allowed (Shame on you Microsoft… 🙂 )
Important: If you are using a Windows RRAS for the VPN Tunnel, choose Dynamic Routing, otherwise static:
You can then download the script, to install the VPN Connection on your Device, this process is straight Forward, thus I don’t Show this here.
When your Firewall Rules are OK, you can then establish the connect to your Azure Remote App Environment. A small word of Routing and Firewall here: Be sure, that the traffic from your On-Premise Servers is Routed correctly to the VPN Device.
Now it is time to talk about creating an Image for your RemoteApp Collection, this is quite simple, and documented here: http://azure.microsoft.com/en-us/documentation/articles/remoteapp-create-custom-image/
- VHD required (VHDX not supported)
- If you are using Server 2012 R2 with Update, the KB2977219 is already included
If you have successfully sysprepped your Image, it’s time to upload. Depending on your Internet Connection, bring bathtubs of coffee 😉
With my small 2MBit Uplink, it took over 12 hours to upload the Image. But you are also able, to create the template Inside Azure, so you don’t have to upload the Image. This means, you have to create a VM in Azure IaaS, and prepare the machine as you do On-Premise (except the addition that you have to delete the unattend.xml). Afterwards you can Upload your Template with the perfect script from Scott Brickey (http://www.sbrickey.com/Tech/Blog/Post/Publishing_a_custom_RemoteApp_service_in_3_hours), do this also within an Azure IaaS VM. Mind to install the Azure Powershell (http://azure.microsoft.com/en-us/documentation/articles/install-configure-powershell/).
When you are uploading your Image, make sure, that you choose the same Region, as you did for the virtual Network:
Be sure, that you start the Upload on a Machine, which is running through, because, you can’t Abort the upload on a machine, and restart it on another. It is possible to stop the upload, and start it again on the same machine, and it will also upload, where it has stopped. But this works only on the same machine.
When the Upload is done, you can create your RemoteApp Collection, and assign users to it.
The users will then be able to consume Applications with On-Premise Data on the Device they like to use, let me say, using KeePass on a iPad:
I also have Installed Microsoft UE-V and everthing works like a charm.
Hope this helps.
One thought on “Azure Remote App – Common mistakes”
[…] « Azure Remote App – Common mistakes […]