Creating and uploading the image for RemoteApp turned out to be a challenge for some odd reasons. For the script Upload-AzureRemoteAppTemplateImage.ps1 to work you need to make sure you fulfill the prereqs it needs. Which can be found if you read the script 😉
If Upload-AzureRemoteAppTemplateImage.ps1 fails for “odd” reasons you need to make sure that you’re running PowerShell as Admin and that you’re starting “Windows Azure PowerShell” or have the Azure module loaded.
Here’s my short list of what you need to do:
- Create a new Hyper-V VM with a 40 GB
FIXEDdynamic (now supported) size disk.
- Install Windows Server 2012 R2 (only OS supported)
- Install RDSH role and Desktop Experience feature (both needed)
- Reboot (needed to make sure application installations are aware of RDS)
- Install the applications you want to publish to your users
- From an elevated CMD, run “fsutil behavior set disableencryption 1” (disables EFS encryption of file system)
- Reboot (makes sure EFS disable is written to registry)
- Run “sysprep /oobe /generalize /shutdown”
Once your machine is turned off you need to start PowerShell as administrator with the Azure cmdlets.
Run the script provided by the portal, find your VHD-file and you should be on your way!
Uploading the file
The portal states the template status as “uploading”