Skip to content

Commit 84a3a23

Browse files
Merge pull request #18459 from haraldfianbakken/release-local-disconnectednew
Minor fixes, calling out 2506 which is now public / iso - in deploym…
2 parents 00df0a9 + 1b65d04 commit 84a3a23

File tree

3 files changed

+16
-6
lines changed

3 files changed

+16
-6
lines changed

azure-local/manage/disconnected-operations-deploy.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -52,12 +52,12 @@ Here's a checklist of things you need before you deploy Azure Local with disconn
5252
- Local credentials for Azure Local machines.
5353
- Active directory credentials for Azure Local deployment.
5454
- [Active directory prepared for Azure Local deployment](../deploy/deployment-prep-active-directory.md).
55-
- Certificates to secure ingress endpoints (26 certificates) and the public key (root) used to create these certificates.
55+
- Certificates to secure ingress endpoints (24 certificates) and the public key (root) used to create these certificates.
5656
- Certificates to secure the management endpoint (2 certificates).
5757
- Credentials and parameters to integrate with identity provider:
5858
- Active Directory Federations Services (ADFS) application, credentials, server details, and certificate chain details for certificates used in identity configuration.
5959
- Disconnected operations deployment files (manifest and appliance).
60-
- The preview ISO (accompanying release 2411.2 or later).
60+
- The Azure Local composite ISO (follows release 2506 or later).
6161
- Firmware/device drivers from OEM.
6262

6363
## Deployment sequence
@@ -220,7 +220,7 @@ To prepare the first machine for the disconnected operations appliance, follow t
220220
Copy-Item \\fileserver\share\azurelocalcerts $certspath -recurse
221221
```
222222
223-
1. Verify the certificates, public key, and management endpoint. You should have two folders: `ManagementEndpointCerts` and `IngressEndpointCerts` and at least 26 certificates.
223+
1. Verify the certificates, public key, and management endpoint. You should have two folders: `ManagementEndpointCerts` and `IngressEndpointCerts` and at least 24 certificates.
224224
225225
```powershell
226226
Get-ChildItem $certsPath

azure-local/manage/disconnected-operations-pki.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -289,6 +289,16 @@ _continue_ = "DNS=$subject"
289289

290290
- Copy the management certificates (*.pfx) to the directory structure represented in ManagementEndpointCerts.
291291

292+
## Export Root CA certificate
293+
294+
You need the root certificate public key for deployment. The following example shows how to export your root certificate public key:
295+
296+
```azurecli
297+
certutil -ca.cert applianceRootCA.cer
298+
```
299+
300+
For more information, see [Active Directory Certificate Services](/troubleshoot/windows-server/certificates-and-public-key-infrastructure-pki/export-root-certification-authority-certificate).
301+
292302
## Obtain certificate information for identity integration
293303

294304
To secure your identity integration, we recommend that you pass these two parameters:

azure-local/manage/disconnected-operations-set-up.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -65,18 +65,18 @@ To create a virtual appliance and download the required files for your on-premis
6565
> [!NOTE]
6666
> For the next two steps, see the supplemental documentation for getting the appliance. During the first preview, special instructions are required for downloading the appliance. Steps 6 and 7 are subject to change during preview.
6767
68-
1. Look for the **download manifest** and **get appliance** actions. You need these files for your on-premises installation.
68+
1. Look for the **download manifest** and **get virtual appliance** actions. You need these files for your on-premises installation.
6969

7070
| Action | Description | Estimated download size |
7171
|------|-------------|----------------|
7272
| Manifest file | Identified as `AzureLocal.DisconnectedOperations.Appliance.manifest`. This file is needed for deployment and to activate the appliance. It contains the required licensing information and more. | < 1 KB |
73-
| Appliance | Downloads a set of files, identified as `AzureLocal.disconnectedoperations.zip`, `ArcA_LocalData_A.vhdx`,`ArcA_SharedData_A.vhdx`, and`OSAndDocker_A.vhdx`. These files contain the virtual hard disks and virtual machine together with the operations module required to deploy and configure the virtual appliance as a whole. | 70 GB+ |
73+
| Appliance | Shows a set of files you can download, identified as `AzureLocal.disconnectedoperations.zip`, `ArcA_LocalData_A.vhdx`,`ArcA_SharedData_A.vhdx`, and`OSAndDocker_A.vhdx`. These files contain the virtual hard disks and virtual machine together with the operations module required to deploy and configure the virtual appliance as a whole. You can download each file individually or run the script provided on the page to automate the download. | 70 GB+ |
7474

7575
1. Select **download manifest**.
7676

7777
:::image type="content" source="media/disconnected-operations/set-up/new-appliance.png" alt-text="Screenshot of the resource page for the virtual appliance you created." lightbox="media/disconnected-operations/set-up/new-appliance.png":::
7878

79-
1. Select **get appliance** and download each file in the list. This can take several hours. When completed, move these files to a single folder. Unzip the `AzureLocal.disconnectedoperations.zip` file in that folder. After you extract the zip file, delete it. You should have the following files required for installation in the folder after this step:
79+
1. Select **get virtual appliance** and download each file in the list. This can take several hours. When completed, move these files to a single folder. Unzip the `AzureLocal.disconnectedoperations.zip` file in that folder. After you extract the zip file, delete it. You should have the following files required for installation in the folder after this step:
8080

8181
- manifest.xml
8282
- OperationsModule

0 commit comments

Comments
 (0)