This year I’ve blogged more than last year. I really like sharing my knowledge with the community. This year I also changed the focus of my blog to Remote Desktop Service, Enterprise Mobility Suite and the Operations Management Suite. I want to share some statistics of this year with you. This blogpost will also be the last blogpost of this year!
This year a lot of new features are developed and released in Azure RemoteApp. At the end of this year I want to summarize all the improvements which are released this year. The RDS Team is continuous improving the product by releasing new features and improvements each month. On the 11th of December 2014 Brad Anderson announced the GA of Azure RemoteApp. Since this date a lot of new features and improvements are added and this blogpost will summarize most of them. At the end of this blogpost I want to look into the roadmap of Azure RemoteApp for the coming months.
Last week Microsoft introduced the Azure Custom Roles functionality in their Role Based Access model. We now have the possibility to create custom Roles for granting access to resources on Microsoft Azure. Looking to RBAC this is a very nice addition and really powerful. A lot of companies have invested in AGDLP in their on premise Active Directory. Today I’ve tested if this investment can be re-used when granting permissions based on these groups to custom roles in Azure.
Based on announcement that Azure Automation now supports Azure Resource Manager (source) I checked my solution for synchronizing Azure RemoteApp membership through Azure Automation. You can find the original blogpost here. The solution used both Service Management API cmdlets and Azure Resource Manager cmdlets. Based on the testing the Azure Resource Manager cmdlets did fail during the execution of the runbook. I’ve updated the runbook and everything is now working again using the new Azure Resource Manager cmdlets.
This is the 4th part of the blog series about User Environment Management within Azure RemoteApp. In the first 2 blogposts which you can find here and here I discussed the use of Microsoft User Experience Virtualization in combination with Azure RemoteApp. In the 3rd part I explained why you should disable the User Profile Disk when using another solution for User Environment Virtualization. This post will describe the use of AppSense DesktopNow in combination with Azure RemoteApp. I’m writing this blogpost together with my formal colleague Corné van Ginkel which is specialized the AppSense products.
You can deploy Azure RemoteApp in different scenarios. One of the scenarios is a Hybrid Deployment. In a Hybrid deployment the Azure RemoteApp instances are added to your Active Directory. The instances will be added to a dedicated OU in that Active Directory. When you start working with a Hybrid Deployment you will notice after some time that the orphaned AD Computer objects of Azure RemoteApp instances will not be deleted. This blogpost will focus on using cleaning up this computer accounts with using a new Azure RemoteApp cmdlet and Azure Automation.