Skip to content

Commit 482a573

Browse files
committed
Edit pass
1 parent 2e6107a commit 482a573

File tree

1 file changed

+14
-21
lines changed

1 file changed

+14
-21
lines changed

articles/databox-online/azure-stack-edge-powershell-based-configuration.md

Lines changed: 14 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -6,20 +6,21 @@ author: alkohli
66
ms.service: databox
77
ms.subservice: edge
88
ms.topic: article
9-
ms.date: 03/17/2023
9+
ms.date: 03/20/2023
1010
ms.author: alkohli
1111
---
1212
# Use a config file to deploy an Azure Stack Edge device
1313

1414
[!INCLUDE [applies-to-GPU-and-pro-r-and-mini-r-skus](../../includes/azure-stack-edge-applies-to-gpu-pro-r-mini-r-sku.md)]
1515

16-
This article describes how to automate initial device configuration and activation of Azure Stack Edge devices using PowerShell. Use the steps in this article as alternatives to the local web user interface setup sequence.
16+
This article describes how to use PowerShell to automate initial device configuration and activation of Azure Stack Edge devices. Use the steps in this article as alternatives to the local web user interface setup sequence.
1717

1818
You can run as many rounds of device configuration as necessary. You can also use the Azure portal or the device local user interface to modify device configuration.
1919

2020
## Usage considerations
2121

22-
- You can apply individual configuration changes to a device using PowerShell cmdlets, or you can apply bulk configuration changes using a JSON file. You can apply changes with a JSON file at any point in the appliance lifecycle.
22+
- You can apply individual configuration changes to a device using PowerShell cmdlets, or you can apply bulk configuration changes using a JSON file.
23+
- You can apply changes with a JSON file at any point in the appliance lifecycle.
2324
- To manage devices using the local web user interface, see [Connect to Azure Stack Edge Pro with GPU](azure-stack-edge-gpu-deploy-connect.md?pivots=single-node).
2425
- You can't change device authentication using this method. To change device authentication settings, see [Change device password](azure-stack-edge-gpu-manage-access-power-connectivity-mode.md#change-device-password).
2526
- Cluster formation is not supported using PowerShell cmdlets. For more information about Azure Stack Edge clusters, see [Install a two-node cluster](azure-stack-edge-gpu-deploy-install.md?pivots=two-node).
@@ -84,17 +85,9 @@ Use the following steps to import the PowerShell module and sign in to the devic
8485
Set-Login "https://<IP address>" "<Password1>" "<NewPassword>"
8586
```
8687

87-
## Change password and fetch the device configuration
88+
## Fetch the device configuration
8889

89-
Use the following steps to sign in to a device, change the password, and fetch the device configuration:
90-
91-
1. Sign in to the device and specify a new device password.
92-
93-
```azurepowershell
94-
Set-Login "https://<IP address>" "<CurrentPassword>" "<NewPassword>"
95-
```
96-
97-
1. Fetch the device configuration.
90+
Use the following cmdlet to fetch the device configuration:
9891

9992
```azurepowershell
10093
Get-DeviceConfiguration | To-json
@@ -181,7 +174,7 @@ Run the following cmdlets in PowerShell:
181174
Once a config.json file has been created, as shown in the previous example, with the desired configuration, use the JSON file to change configuration settings on one or more devices.
182175

183176
> [!NOTE]
184-
> Use a config.json file that meets the needs of your organization. [Sample JSON files are available here](https://github.com/Azure-Samples/azure-stack-edge-deploy-vms/tree/master/PowerShellBasedConfiguration/).
177+
> Use a config.json file that meets the needs of your organization. [Sample JSON files are available here](https://aka.ms/aseztp-ps).
185178
186179
### Configure a single-node device
187180

@@ -249,7 +242,7 @@ Run the following cmdlets in PowerShell:
249242

250243
### Configure a two-node device
251244

252-
This sequence of PowerShell cmdlets signs in to a two-node device, applies device configuration settings from a JSON file, verifies completion of the operation, and then fetches the new device configuration.
245+
This sequence of PowerShell cmdlets applies device configuration settings from a JSON file, verifies completion of the operation, and then fetches the new device configuration.
253246

254247
> [!NOTE]
255248
> Two-node configurations are only supported on Azure Stack Edge Pro GPU and Azure Stack Edge Pro 2 devices.
@@ -712,7 +705,7 @@ Use the following steps to activate an Azure Stack Edge device. Note that activa
712705
Get-DeviceConfiguration | To-json
713706
```
714707

715-
Here's sample output showing device activation status:
708+
Here's sample output showing that the device is activated:
716709

717710
```output
718711
PS C:\> Get-DeviceConfiguration | To-json
@@ -736,7 +729,7 @@ Use the following steps to activate an Azure Stack Edge device. Note that activa
736729

737730
## Quickly fetch or change device configuration settings
738731

739-
Use the following steps to sign in to the device, fetch the status of the `WebProxy` properties, set the `WebProxy` property to “isEnabled = true” and set the `WebProxy` URI, and then fetch the status of the changed `WebProxy` properties. After running the package, verify the new device configuration.
732+
Use the following steps to fetch the status of the `WebProxy` properties, set the `WebProxy` property to “isEnabled = true” and set the `WebProxy` URI, and then fetch the status of the changed `WebProxy` properties. After running the package, verify the new device configuration.
740733

741734
1. Load the device configuration cmdlet.
742735

@@ -817,7 +810,7 @@ Use the following steps to sign in to the device, fetch the status of the `WebPr
817810
}
818811
```
819812

820-
## Enable proactive log consent
813+
## Enable proactive log collection
821814

822815
Proactive log collection gathers system health indicators on your Azure Stack Edge device to help you efficiently troubleshoot any device issues. Proactive log collection is enabled by default. For more information, see [Proactive log collection](azure-stack-edge-gpu-proactive-log-collection.md).
823816

@@ -855,9 +848,9 @@ Use the following steps to fetch the current setting and then enable or disable
855848

856849
## Run device diagnostics
857850

858-
To diagnose and troubleshoot any device errors, you can run the diagnostics tests. For more information, see [Run diagnostics](azure-stack-edge-gpu-troubleshoot.md#run-diagnostics).
851+
To diagnose and troubleshoot device errors, run diagnostic tests. For more information, see [Run diagnostics](azure-stack-edge-gpu-troubleshoot.md#run-diagnostics).
859852

860-
Use the following steps to sign in to the device and run device diagnostics to verify status after you apply a device configuration package.
853+
Use the following steps to verify device status after you apply a configuration package.
861854

862855
1. Run device diagnostics.
863856

@@ -997,7 +990,7 @@ Use the following steps to sign in to the device and run device diagnostics to v
997990
> [!NOTE]
998991
> Two-node configurations are only supported on Azure Stack Edge Pro GPU and Azure Stack Edge Pro 2 devices.
999992
1000-
Define a virtual IP that allows you to connect to a clustered device instead of a specific node. A virtual IP is an available IP in the cluster network. Any client connecting to the cluster network on the two-node device should be able to access this IP.
993+
A virtual IP is an available IP in the cluster network. Set a virtual IP to connect to a clustered device instead of an individual node. Any client connecting to the cluster network on the two-node device must be able to access the virtual IP.
1001994

1002995
You can set either an Azure Consistent Services or a Network File System configuration. Additional options include static or DHCP network settings. For more information about setting virtual IPs, see [Configure virtual IPs](azure-stack-edge-pro-2-deploy-configure-network-compute-web-proxy.md#configure-virtual-ips).
1003996

0 commit comments

Comments
 (0)