You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Prepare an Ubuntu image for Azure Local virtual machines
@@ -20,7 +20,7 @@ This article describes how to prepare an Ubuntu image to create a virtual machin
20
20
Before you begin, meet the following prerequisites:
21
21
22
22
- Have access to an Azure Local instance. This system is deployed, registered, and connected to Azure Arc. Go to the **Overview** page in the Azure Local resource. On the **Server** tab on the right pane, **Azure Arc** should appear as **Connected**.
23
-
-[Download the latest supported Ubuntu server image](https://ubuntu.com/download/server) on your Azure Local system. The supported OS versions are *20.04*, *22.04*, *24.04 LTS*. You prepare this image to create an Azure Local VM image.
23
+
-[Download the latest supported Ubuntu server image](https://ubuntu.com/download/server) on your Azure Local system. The supported OS versions are *Ubuntu 20.04*, *22.04*, and*24.04 LTS*. You prepare this image to create an Azure Local VM image.
Copy file name to clipboardExpand all lines: azure-stack/includes/warning-cloud-admin-backup-account.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,12 +3,12 @@ author: sethmanheim
3
3
ms.author: sethm
4
4
ms.service: azure-stack
5
5
ms.topic: include
6
-
ms.date: 3/30/2022
6
+
ms.date: 01/28/2022
7
7
ms.reviewer: thoroet
8
8
ms.lastreviewed: 03/30/2022
9
9
---
10
10
11
-
> [!Warning]
12
-
> By default your Azure Stack Hub stamp is configured with only one [CloudAdmin account](../operator/azure-stack-manage-basics.md#what-account-should-i-use). There are no recovery options if the account credentials are lost, compromised, or locked. **You will lose access to the privileged endpoint and other resources**.
13
-
>
14
-
> **It is *highly* recommended that you [create additional CloudAdmin accounts](../reference/pep/new-cloudadminuser.md), to avoid redeployment of your stamp at your own expense.** Make sure you document these credentials based on your company's guidelines.
11
+
> [!WARNING]
12
+
> By default, your Azure Stack Hub stamp is configured with only one CloudAdmin account. There are no recovery options if the account credentials are lost, compromised, or locked. You will lose access to the privileged endpoint and other resources.
13
+
>
14
+
> It's highly recommended that you [create additional CloudAdmin accounts](../reference/pep/new-cloudadminuser.md), to avoid redeployment of your stamp at your own expense. Make sure you document these credentials based on your company's guidelines.
description: Learn how to install Azure Stack Hub Updates.
2
+
title: Install Azure Stack Hub updates
3
+
description: Learn how to install Azure Stack Hub updates.
4
4
author: sethmanheim
5
5
ms.topic: how-to
6
-
ms.date: 07/26/2021
6
+
ms.date: 01/28/2025
7
7
ms.author: sethm
8
8
ms.lastreviewed: 09/10/2019
9
-
ms.reviewer: niy
10
9
11
10
# Intent: As an Azure Stack operator, I want to install OEM updates to keep my system up to date.
12
11
# Keyword: install oem updates azure stack
13
12
14
13
---
15
14
16
15
17
-
# Install Azure Stack Hub Updates
16
+
# Install Azure Stack Hub updates
18
17
19
18
You can install update packages using the **Update** blade in the Azure Stack Hub administrator portal. This article describes the steps to update, monitor, and troubleshoot the update process. Use the **Update** blade to view update info, install updates, monitor update progress, review update history, and view the current Azure Stack Hub and OEM package version.
20
19
@@ -30,49 +29,43 @@ You can manage updates from the administrator portal and use the **Updates** sec
30
29
You can view the current version of Azure Stack Hub in the **Update** pane. To open:
31
30
32
31
1. Open the Azure Stack Hub administrator portal.
32
+
1. Select **Dashboard**. In the **Update** pane, the current version is listed:
33
33
34
-
2. Select **Dashboard**. In the **Update** pane, the current version is listed:
35
-
36
-
[](./media/azure-stack-apply-updates/dashboard-expanded.png#lightbox)
34
+
[](./media/azure-stack-apply-updates/dashboard-expanded.png#lightbox)
37
35
38
36
## Install updates and monitor progress
39
37
40
38
> [!IMPORTANT]
41
-
> Before applying updates in Azure Stack Hub, ensure you have completed all steps in the [pre-update checklist](release-notes-checklist.md) and have scheduled an appropriate maintenance window for the update type that you are applying.
39
+
> Before applying updates in Azure Stack Hub, ensure that you complete all steps in the [pre-update checklist](release-notes-checklist.md) and schedule an appropriate maintenance window for the update type that you are applying.
42
40
43
41
1. Open the Azure Stack Hub administrator portal.
42
+
1. Select **Dashboard**, then select **Update**.
43
+
1. Select the available update that you want to install. If you don't have an update marked as **Available**, [prepare the update package](azure-stack-update-prepare-package.md).
44
+
1. Select **Install now**.
44
45
45
-
2. Select **Dashboard**. Select **Update**.
46
-
47
-
3. Select the available update that you want to install. If you don't have an update marked as **Available**, [prepare the update package](azure-stack-update-prepare-package.md).
48
-
49
-
4. Select **Install now**.
46
+
[](./media/azure-stack-apply-updates/updates-2-expanded.png#lightbox)
50
47
51
-
[](./media/azure-stack-apply-updates/updates-2-expanded.png#lightbox)
48
+
1. You can view high-level status as the update process iterates through various subsystems in Azure Stack Hub. Example subsystems include physical hosts, Service Fabric, infrastructure virtual machines, and services that provide both the admin and user portals. Throughout the update process, the update resource provider reports additional details about the update, such as the number of steps that have succeeded, and the number in progress.
52
49
53
-
5. You can view high-level status as the update process iterates through various subsystems in Azure Stack Hub. Example subsystems include physical hosts, Service Fabric, infrastructure virtual machines, and services that provide both the admin and user portals. Throughout the update process, the update resource provider reports additional details about the update, such as the number of steps that have succeeded, and the number in progress.
50
+
1. Select **Download summary** from the update run details blade to download full logs.
54
51
55
-
6. Select **Download summary** from the updaterun details blade to download full logs.
52
+
If you experience an issue while monitoring the update, you can use the [privileged endpoint](./azure-stack-privileged-endpoint.md) to monitor the progress of an Azure Stack Hub update run. You can also use the privileged endpoint to resume a failed update run from the last successful step if the Azure Stack Hub portal becomes unavailable. For instructions, see [Monitor updates in Azure Stack Hub using PowerShell](azure-stack-update-monitor.md).
56
53
57
-
If you experience an issue while monitoring the update, you can use the [privileged endpoint](./azure-stack-privileged-endpoint.md) to monitor the progress of an Azure Stack Hub update run. You can also use the privileged endpoint to resume a failed update run from the last successful step if the Azure Stack Hub portal becomes unavailable. For instructions, see [Monitor updates in Azure Stack Hub using PowerShell](azure-stack-update-monitor.md).
54
+
58
55
59
-
60
-
61
-
7. When complete, the update resource provider displays a **Succeeded** confirmation to show that the update process has finished, and how long it took. From there, you can view info on all updates, available updates, or installed updates using the filter.
56
+
1. When complete, the update resource provider displays a **Succeeded** confirmation to show that the update process has finished, and how long it took. From there, you can view info on all updates, available updates, or installed updates using the filter.
62
57
63
58
If the update fails, the **Update** blade reports **Needs attention**. Use the **Download full logs** option to get a high-level status of where the update failed. Azure Stack Hub log collection helps with diagnostics and troubleshooting.
0 commit comments