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
Copy file name to clipboardExpand all lines: azure-local/manage/add-server.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Learn how to manage capacity on your Azure Local, version 23H2 syst
4
4
ms.topic: article
5
5
author: alkohli
6
6
ms.author: alkohli
7
-
ms.date: 05/22/2025
7
+
ms.date: 05/28/2025
8
8
---
9
9
10
10
# Add a node on Azure Local
@@ -99,7 +99,9 @@ On the new node that you plan to add, follow these steps.
99
99
1. Install the operating system and required drivers on the new node that you plan to add. Follow the steps in [Install the Azure Stack HCI Operating System, version 23H2](../deploy/deployment-install-os.md).
100
100
101
101
>[!NOTE]
102
-
> For versions 2503 and later, you'll need to use the OS image of the same solution as that running on the existing cluster. Use the [OS image](https://github.com/Azure-Samples/AzureLocal/blob/main/os-image/os-image-tracking-table.md) table to identify and download the appropriate OS image version.
102
+
> - For versions 2503 and later, you'll need to use the OS image of the same solution as that running on the existing cluster.
103
+
> - Use the [Get solution version](../update/azure-update-manager-23h2.md#get-solution-version) to identify the solution version that you are running on the cluster.
104
+
> - Use the [OS image](https://github.com/Azure-Samples/AzureLocal/blob/main/os-image/os-image-tracking-table.md) table to identify and download the appropriate OS image version.
103
105
104
106
2. Register the node with Arc. Follow the steps in [Register with Arc and set up permissions](../deploy/deployment-arc-register-server-permissions.md).
Copy file name to clipboardExpand all lines: azure-local/manage/repair-server.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -121,10 +121,11 @@ Follow these steps on the node you're trying to repair.
121
121
:::image type="content" source="./media/repair-server/delete-machine-node-resource-1.png" alt-text="Screenshot of deletion of faulty Azure Arc machine node." lightbox="./media/repair-server/delete-machine-node-resource-1.png":::
122
122
123
123
1. Install the operating system and required drivers on the node you wish to repair. Follow the steps in [Install the Azure Stack HCI Operating System, version 23H2](../deploy/deployment-install-os.md).
124
-
125
-
> [!NOTE]
126
-
> - For versions 2503 and later, you'll need to use the OS image of the same solution as that running on the existing cluster. Use the [OS image](https://github.com/Azure-Samples/AzureLocal/blob/main/os-image/os-image-tracking-table.md) table to identify and download the appropriate OS image version.
127
-
> - If you deployed your Azure Local instance using custom storage IPs, you must manually assign IPs to the storage network adapters after the node is repaired.
124
+
125
+
>[!NOTE]
126
+
> - For versions 2503 and later, you'll need to use the OS image of the same solution as that running on the existing cluster.
127
+
> - Use the [Get solution version](../update/azure-update-manager-23h2.md#get-solution-version) to identify the solution version that you are running on the cluster.
128
+
> - Use the [OS image](https://github.com/Azure-Samples/AzureLocal/blob/main/os-image/os-image-tracking-table.md) table to identify and download the appropriate OS image version.
128
129
129
130
1. Register the node with Arc. Follow the steps in [Register with Arc and set up permissions](../deploy/deployment-arc-register-server-permissions.md).
Copy file name to clipboardExpand all lines: azure-local/release-information-23h2.md
+37-22Lines changed: 37 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ author: alkohli
5
5
ms.author: alkohli
6
6
ms.topic: conceptual
7
7
ms.service: azure-local
8
-
ms.date: 05/19/2025
8
+
ms.date: 05/28/2025
9
9
---
10
10
11
11
# Azure Local release information
@@ -22,37 +22,49 @@ This article provides the release information for Azure Local, including the rel
22
22
23
23
## About Azure Local releases
24
24
25
-
The Azure Local includes multiple release trains: 2408, 2411, 2503, and 2504. Each release train includes a feature build and subsequent cumulative updates.
25
+
The Azure Local includes multiple release trains: 2411, 2503, 2504, 2505, and so forth. Each release train after 2411 is either a feature build or cumulative update.
26
26
27
27
-**Feature build**: The feature update build is the initial version of the software in a release train. Feature releases go beyond quality and security fixes, incorporating product enhancements, including updates for Azure Local services and agents.
28
28
29
29
-**Cumulative build**: A cumulative update build includes the incremental updates from the most recent feature build.
30
30
31
-
The following diagram illustrates the release trains, their associated feature builds, and update paths.
31
+
The following diagram illustrates the feature builds, cumulative updates, and update paths.
32
32
33
33
:::image type="content" source="./media/release-information-23h2/release-trains-supported-update-paths.png" alt-text="Diagram illustrating Azure Local release trains with supported update paths."lightbox="./media/release-information-23h2/release-trains-supported-update-paths.png":::
34
34
35
35
## Feature release availability timing
36
36
37
37
Feature release availability dates depend on the model and SKU of the servers in your cluster.
38
38
39
-
If your cluster supports [Solution Builder Extension software updates](./update/solution-builder-extension.md), you'll receive feature release updates (e.g., 2504 or 2510) after your hardware vendor completes their validation and confirms the release is ready. This process typically takes a few weeks following the Microsoft release and varies by hardware vendor.
39
+
If your cluster supports [Solution Builder Extension software updates](./update/solution-builder-extension.md), you'll receive feature release updates (for example, 2504 or 2510). These updates are available after your hardware vendor completes their validation and confirms the release is ready. This process typically takes a few weeks following the Microsoft release and varies by hardware vendor.
40
40
41
41
> [!NOTE]
42
42
> The validation process ensures a reliable update experience for your cluster. It minimizes potential issues and reduces the overall number of updates you need to manage for Azure Local.
43
43
44
-
### Move to the next release train
44
+
## Update paths
45
+
46
+
### Existing deployments
47
+
48
+
For existing deployments, such as the 2411 feature build, you can update to any of the 2411 cumulative update builds. This path includes the 2411.2 and 2411.3 cumulative updates, which are required to update to the 2503 feature build. The 2503 feature build is required to update to the 2504 feature build.
For new deployments, install a feature build directly. For example, you can install the 2504 build which has an OS version 261000.3775 and solution version 12.2504.1001.20. After the installation, you can install the latest cumulative update build (2505) to keep your system up to date.
57
+
58
+
<!-- ### Move to the next release train
45
59
46
60
Follow these guidelines to skip releases with the same release train as you move to the next release train:
47
61
48
62
- Update the existing deployment to a build that allows you to move to the next release train. The following table provides examples of how to move between release trains:
- To keep your Azure Local instance in a supported state, you have up to six months to install updates. For example, if you're running the 2408 feature build, update to a later build within six months.
81
+
> [!NOTE]
82
+
> To keep your Azure Local instance in a supported state, you have up to six months to install updates. For example, if you're running the 2408 feature build, update to a later build within six months.
70
83
71
84
## Azure Local release information summary
72
85
@@ -76,24 +89,24 @@ The following tables summarize the release information for Azure Local across al
76
89
77
90
Starting in 2504, we offer two releases. One release provides the path to upgrade from 2503 to 2504. The other release supports a new deployment of 2504.
78
91
79
-
Starting with Azure Local 2503, you can discover and import update packages for Azure Local with limited connectivity to Azure. To download the bundle and its SHA256 hash, see the **Download URI** column in the following table. For more information on how to import and discover update packages with limited connectivity, see [Update via PowerShell with limited connectivity](./update/import-discover-updates-offline-23h2.md).
92
+
Starting with Azure Local 2503, you can discover and import update packages for Azure Local with limited connectivity to Azure. For more information on how to import and discover update packages with limited connectivity, see [Update via PowerShell with limited connectivity](./update/import-discover-updates-offline-23h2.md).
0 commit comments