Updating Azure Stack to 1804 – Logs, Logs, and More Logs – Part III

This is part III of my series on updating Azure Stack to 1804.  My last blog was Updating Azure Stack to 1804 – Installing The Updates – Part II which covered how to download and import the updates into your stack.  This next blog I will talk about how to monitor the update process using the privileged endpoint as well as the Admin Portal.  This currently is a three-part blog series with the following topics:

  • Fixes and Features
  • Installation
  • Monitoring

First of all, all credit needs to be given to the Microsoft Document team and where I get most my information while working with Azure Stack and these updates.


I sound like a broken record when mentioned the documentation team at Microsoft.  However, I feel it important to make sure everyone knows that most of the information in this series comes from their hard work at documenting the process.

Now that we have the updates imported into our multi-node stamp and have kicked off the update we need a way to monitor these updates.

I am currently aware of 2 ways we can do this.  The first is within the Admin Portal and the other is by using logs from the privileged endpoint.  The admin portal is nice and easy to get to and doesn’t really require much work on the side of the operator.  However, it isn’t always the fastest way to see what is going on with the update process.

The Admin Portal:

From within the Admin Portal, you can click on Updates, select the current updating being installed, then click on progress.  To the right, the Update run details will pop up.  You can see at a high level how many updates are successful,  failed, and what is running.


You can also click on Download Full logs within this window, save the JSON file to your local machine and open it up to view details.   The format that I get when opening this file in Visual Studio code is all on a single line and a little hard to read.  I will look into how to get this JSON file to provide better information.  As of know it is nice to have in case you have issues but doesn’t work well for me as a log file.

Using the Privileged Endpoint (ERCS).

Now another way is to use the Privileged Endpoint (PEP) or also called the Emergency Recovery Console (ERCS) to view real-time logs and status of the update process.


I have found this to be the best way to find out what is going on with the update process since the Admin Portal can be a bit behind in updating.

There are a few ways we can go about getting the logs.  The first way is very basic and easy.  First, you create a PowerShell Session to your ERCS virtual machine.

$cred = Get-Credential
Enter-PSSession -ComputerName <IP or Computer Name> -Credential $cred -ConfigurationName PrivilegedEndpoint

From here you can run several commands.


This will return a good bit of information about the status of the currently running, completed, and failed updates.  This is more for a high-level overview of the update status.  The output is in an XML format so you will need to scroll up and down to find what you are looking for.

Get-AzureStackUpdateVerboseLog -Wait

You can also get an active view of the logging this way as well.  The following command will dump information about what is running and is updated every 60 seconds.


You can also connect to you privileged endpoint and assign a variable to the session to make life a little easier running some of these logs.

$cred = Get-Credential

$pepSession = New-PSSession -ComputerName <Prefix>-ercs01 -Credential $cred -ConfigurationName PrivilegedEndpoint

For a high-level status you can run the following commands:

$statusString = Invoke-Command -Session $pepSession -ScriptBlock { Get-AzureStackUpdateStatus -StatusOnly }



For a more detailed status you can run the following:

[xml]$updateStatus = Invoke-Command -Session $pepSession -ScriptBlock { Get-AzureStackUpdateStatus }



You can also get a verbose progress log.  This should help you with troubleshooting updates.  I have not tried this one to be honest.

$log = Invoke-Command -Session $pepSession -ScriptBlock { Get-AzureStackUpdateVerboseLog }

$log > “.\UpdateVerboseLog.txt”


So wrapping up this series on updating Azure stack to 1804 at this time.  There are some nice new features and fixes that were released as part of 1804.  There are even more to come in the next few releases I am really looking forward to.  Remember, always read the documentation first.  I keep saying that but sometimes I don’t even do it.

2 thoughts on “Updating Azure Stack to 1804 – Logs, Logs, and More Logs – Part III

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s