How To Publish an Internal Windows App on Azure Remote App
Today is a important day, Azure Team is officially releasing in General Availability Azure Remote App (ARA), if you like of Remote Desktop Services, you will love ARA. Imagine the following situation : delivery your Windows Apps (LOB), Office or any app that run on Windows Server 2012 R2 to your users from their desktops, tablets Windows, IOS and Android and your cell mobile Windows Phone without to need to implement nothing on premises, basically contract them as a service, friendly we can call them like RDP as a Service. Don’t confuse with VDI (Virtual Desktop Infrastructure), in first wave only publishing apps will be available, you can’t publish a desktop to your thin clients. Microsoft is studying and validating this possible scenario in the future. By the way let’s focus how to publish your Windows App internally on Azure Remote App.
You can deploy ARA to two ways : HYBRID and CLOUD
HYBRID mode allows you establishing a VPN between Azure Remote App Tenant / Network and you on premises environment and join your virtual machine image with your windows apps installed to your Active Directory Domain. However if your windows app needs to connect to a database or to do a query to any service to your on premises network ( client-server ) , it is possible.
CLOUD mode is more simple, less complex comparing to HYBRID scenario, you don’t need establishing VPN and your identity can be provided by Azure Active Directory or ADFS on premises. It resides completely in Azure and is created using the Quick create option in the Azure management portal.
TIP : Your subscription for Azure Remote App comes with template image that contain Office 2013 for trial use programs.
I am supposing that you already created Remote App service, but you don’t do that yet, create Remote App service. It can take up to 30 minutes to provision your service. After your Remote App service has been created, go to the Remote App quick start page to continue, during your publishing you need do select your custom image including your internal windows app, it is here that begins my article.
Azure Remote App uses Virtual Machines Generation 1 to provide publishing applications, VM Generation 2 is not supported so far, by the way you can’t deploy VHDX file, only VHD, it can be Dynamically or Fixed, we suggest Dynamically to accelerate upload and consume less space on Azure Storage, furthermore Encryption File System (EFS) need to be disabled and Remote Desktop Session Host and Desktop Experience installed. So let’s create a virtual machine on Hyper-V ( Hyper-V Server or Hyper-V Client of your Windows 8).
I am using my laptop with Windows 8.1 Hyper-V. Open your Disk Management (DISKMGMT.MSC), to Action menu and select Create VHD, select VHD format and Dynamically expanding. Take care to size, VHD must be maximum of 127 GB and multiple of 1024, it is mandatory, if you don’t do that you can have issues when try to do upload to Azure Store Blob. I have create a file of 60 GB of size, so 60 x 1024 = 61440 MB.
The disk must be initialized using the Master Boot Record (MBR) partitioning style. The GUI partition table (GPT) partition is not supported.
Create volume, select NTFS file system and 64K on Allocation unit size to better performance, on Volume label, fill out to your preference name, here is AzureRemoteAppCI.
After that, detach VHD to release disk.
Open your Hyper-V Manager, create a new virtual machine, chose your preference path folder and select Generation 1 ( be careful, don’t choose Generation 2)
Select your VHD file that you created previously, use an existing virtual hard disk. ( memory and processors you need to adjust to your app, at least 2 processors and 2 GB of memory is recommended )
Select your ISO of Windows Server 2012 R2.
Start VM and during installation select Standard version with GUI interface.
You can create more than one volume but only one instance of operation system must be installed