Microsoft Azure

Upgrading Software in Microsoft Azure RemoteApp


In this article, I’ll show you how to upgrade, remove, or replace software in a Microsoft Azure RemoteApp app collection by re-deploying the session hosts from an updated template image.

The Problem

Imagine that you have deployed even the smallest of app collections in Azure using a custom template; a basic plan app collection deploys two session hosts. You will have users logging into at least two hosts. Eventually, a time will come when you need to upgrade, remove, or replace software on those session hosts. How will you do this?

Note that if you use Microsoft-supplied templates then Azure will update the deployments when required. If you use a custom template, then you are responsible for updating the deployments.

Sponsored Content

Devolutions Remote Desktop Manager

Devolutions RDM centralizes all remote connections on a single platform that is securely shared between users and across the entire team. With support for hundreds of integrated technologies — including multiple protocols and VPNs — along with built-in enterprise-grade password management tools, global and granular-level access controls, and robust mobile apps to complement desktop clients.

In theory, you could log into each host via Remote Desktop with an administrator account and manage the installed programs. You could, in theory, use a software management tool such as System Center Configuration Manager, to do the work. But there remains a problem: users will have access to the session hosts, and you potentially will have a lot of work if you have lots of hosts.

The Solution

Fortunately, Azure RemoteApp does have a feature that allows you to update an app collection with a new image in an orchestrated manner. The process works as follows:

  1. You create a new version of your template and add it to RemoteApp.
  2. Select the Update action in your app collection and select the new image.
  3. Choose how to deal with currently logged in users.

Users will either:

  • Be given 60 minutes to finish up their work, where they are notified via an on-screen message and sign out. Any signed in users will be automatically signed out after 60 minutes and the upgrade will start.
  • All signed in users will be immediately signed out without any warning. Choose this option if you are evil, like angry users and bosses, or are working in a test/development environment.

Performing an Update

Use the original virtual machine image that you used to create your app collection. Update this image with any program changes and software updates that are required, and create a new virtual machine image.

  1. Open the classic management portal at (RemoteApp is not available in the new Azure Portal yet), browse to RemoteApp, and enter Template Images.
  2. Click Add, and select Import An Image From Your Virtual Machines Library.
  3. Select the image and confirm that you have met the requirements.
  4. Give the new image a name and select the region of your app collection. Wait for the image to be imported into RemoteApp – refresh the page and you’ll see that it has a status of “Upload pending,” followed by “Import in progress,” so wait for it to be “Ready.”

When the image is imported, browse into the app collection and click Update:

  1. Select the image (previously imported into RemoteApp) that you want to update the app collection to.
  2. Choose when you want to do the update; immediately or give the users 60 minutes’ notice (with an alert). The alert option is strongly recommended in a production environment.
Updating an Azure RemoteApp app collection (Image Credit: Aidan Finn)
Updating an Azure RemoteApp app collection (Image Credit: Aidan Finn)



Related Topics:


Don't have a login but want to join the conversation? Sign up for a Petri Account

Comments (0)

Leave a Reply

Aidan Finn, Microsoft Most Valuable Professional (MVP), has been working in IT since 1996. He has worked as a consultant and administrator for the likes of Innofactor Norway, Amdahl DMR, Fujitsu, Barclays and Hypo Real Estate Bank International where he dealt with large and complex IT infrastructures and MicroWarehouse Ltd. where he worked with Microsoft partners in the small/medium business space.
The World’s Most Comprehensive Teams to Teams Migration Checklist

Whether you have just started thinking about migration or have already begun to move, our Microsoft Teams Migration Checklist can help guide you through the different phases for a Teams migration to another tenant.

This detailed six-step guide will walk you through key decision points while also providing more prescriptive best practice recommendations where appropriate.

Discover key insights for the following phases of a Teams migration: 

  • Discovery
  • Pilot
  • Planning
  • Communication
  • Execution
  • Validation

Sponsored by: