In my previous blog Updating Azure Stack to 1804 – Features, Fixes, and Updates – Part I I talked a little about the new features and the one that grabbed my attention the most, along with what the update fixed and some of the updates that are not included in the release but are related.
In Part II, I will go blog about my experiences with the actual process of installing 1804 on my multi-node stamp. This blog series currently is split up into the following three sections:
- Fixes and Features
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.
First, we need to download the updates. You can find the Azure Stack 1804 update package here. This will download the Azure Stack Update Downloader application. Run this application.
If you have not done so, you will need to install the following hotfix before updating to 1804. You can download AzS Hotfix – 1.0.18042.9 Build 1.1.180421.9 along with the Azure Stack 1804 Update. The Hotfix has the previous 1.0.180413.1 rolled up into it. I actually had issues trying to install Hotfix 1.0.180413.1 the first time. It installed just fine within the rolled up hotfix 1.0.18042.9.
Once the hotfix package has been downloaded you will need to extract that package. Depending on the update there should be at least 3 files or more. The actual 1804 package is already extracted and ready to be imported.
I will admit, I did not read the entire Microsoft Documentation first before trying this and only scanned through what I thought was “important.” This usually leads me to failure and self-examination. :) I created my own Update storage account not even trying to use the pre-built storage account. This led me to wait a very long time for updates not to show up in the Update blade. I then went back to the documentation and discovered that they already had an updateadminacccount storage account where I needed to create the blog storage and store the updates.
So, if you walk away with anything today on my blog, please do not do what I do at least first. This next process is very well documented here:
The first thing we need to do is create a blob under the UpdateAdminAccount storage account that is already created for you and is part of the Update Resource Provider.
Click on storage accounts on the Admin Portal. Under Subscriptions: Default Provider Subscription in the search field, type in UpdateAdminAccount. Below you should only see a single storage account. Click on the storage account.
On the UpdateAdminAccount storage account blade, select the Blobs section.
Click the New Container and name it something that you will remember like 1804.
Once the container has been created, click the upload button. On the right blade under Upload Blob, click the file icon and search for your updates. You can select all the files in the directory at one time. Once they are listed, click the blue upload button. This will take some time depending on how big the update is.
At this point, you can go to the Update tile and you should now see the new 1804 Update available. Click on the 3 dots to the right and select Update Now.
The update should start and you should now see the status in the Updates run details screen.
Now, at this point, you will need to monitor the updates either by using the admin portals Update run details window or you can also use the privileged Endpoint to monitor the status of the updates. This will bring me to Part III of my series Monitoring the Updates.