Granting user’s access to Azure RemoteApp is done by adding them as a user to an Azure RemoteApp collection. There are 2 ways to do this, the first option is by adding single users through the Azure portal or the second option is to use the bulk user import functionality based on a csv file. Both options need to be executed from the Azure Portal. Unfortunately out-of-the-box it’s not possible to use an Active Directory group for granting access to Azure RemoteApp. There is a PowerShell solution made by Freek Berson which you will give this functionality through a PowerShell Script. You can find the link at the end of this blogpost. In this blogpost I want to focus on syncing an Azure Active-Directory group with Azure RemoteApp through Azure Automation. Since in a Hybrid scenario AD Sync is enabled you can also use an on premise AD group which will be synced to Azure Active Directory and use this group as your source. I like the idea of using Cloud technology where possible so this is why I created this solution.
With Azure RemoteApp we have 2 deployment options. First we can deploy Azure RemoteApp in a Cloud Based deployment. When this deployment model is selected the Azure RemoteApp environment will be deployed in a workgroup. When you select a Hybrid deployment the Azure RemoteApp environment will be joined to an Active Directory domain so when provisioned the environment is fully domain joined and can be managed through your existing domain based management solutions. Looking at the pre-requisites of a Hybrid deployment an ‘On-Premise’ Active Directory and an Azure-VNet is needed to deploy a hybrid deployment. In most of the hybrid deployment scenarios a VPN connection between on premise and Azure is also mentioned. In this blogpost I want to describe the steps needed to create a hybrid Azure RemoteApp deployment based on the fact that all components are hosted on Microsoft Azure. Continue reading
In the first post of this blog series I explained how App-V standalone can be used inside Azure RemoteApp. This blogpost will cover the use of the full App-V infrastructure to publish and stream the applications to the Azure RemoteApp instances. Since a domain joined Session Host server is a prerequisite this can only be done through a Hybrid Azure RemoteApp deployment. This blogpost will not cover the installation of the App-V environment itself. This is well described on TechNet. You can find the information here. If you use an external SQL server install the database component first on the SQL server before starting the installer on the App-V Management Server. Continue reading
Today I configured a new Hybrid Azure RemoteApp environment. The deployment was successful without any errors. Afterwards I configured my user access and published my applications. When the first users logs on to the Azure RemoteApp environment I received the following error:
In this series of blogposts I want to describe the different ways of using App-V with Azure RemoteApp. Azure RemoteApp is a cloud service delivered through Microsoft Azure. With Azure RemoteApp you can publish native Windows applications to your ‘Universal Workplace’. Azure RemoteApp has clients for almost all Windows operating systems and also for iOS, Mac OS X and Android. With this broad support of clients Azure RemoteApp provides the flexibility to publish native Windows Applications to almost all platforms. Azure RemoteApp is the cloud implementation of the on-premise RDS RemoteApp technology. Application Virtualization is used in most of the Desktop Virtualization environments, as there is limited information available on the support of App-V in combination with Azure RemoteApp I want to share this information in the following series of blogposts:
- Part 1: Azure RemoteApp with standalone implementation of App-V
- Part 2: Azure RemoteApp with full infrastructure implementation of App-V
- Part 3: Azure RemoteApp with ConfigMgr 2012 R2 SP1 implementation of App-V
In these series I want to describe the steps which I have taken to enable App-V in Azure RemoteApp en want to discuss the advantages en disadvantages of the implementation. This part will continue with describing the standalone implementation of App-V.