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
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.
17
17
18
18
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.
19
19
20
20
## Usage considerations
21
21
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.
23
24
- 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).
24
25
- 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).
25
26
- 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
Use the following cmdlet to fetch the device configuration:
98
91
99
92
```azurepowershell
100
93
Get-DeviceConfiguration | To-json
@@ -181,7 +174,7 @@ Run the following cmdlets in PowerShell:
181
174
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.
182
175
183
176
> [!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).
185
178
186
179
### Configure a single-node device
187
180
@@ -249,7 +242,7 @@ Run the following cmdlets in PowerShell:
249
242
250
243
### Configure a two-node device
251
244
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.
253
246
254
247
> [!NOTE]
255
248
> 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
Here's sample output showing that the device is activated:
716
709
717
710
```output
718
711
PS C:\> Get-DeviceConfiguration | To-json
@@ -736,7 +729,7 @@ Use the following steps to activate an Azure Stack Edge device. Note that activa
736
729
737
730
## Quickly fetch or change device configuration settings
738
731
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.
740
733
741
734
1. Load the device configuration cmdlet.
742
735
@@ -817,7 +810,7 @@ Use the following steps to sign in to the device, fetch the status of the `WebPr
817
810
}
818
811
```
819
812
820
-
## Enable proactive log consent
813
+
## Enable proactive log collection
821
814
822
815
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).
823
816
@@ -855,9 +848,9 @@ Use the following steps to fetch the current setting and then enable or disable
855
848
856
849
## Run device diagnostics
857
850
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).
859
852
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.
861
854
862
855
1. Run device diagnostics.
863
856
@@ -997,7 +990,7 @@ Use the following steps to sign in to the device and run device diagnostics to v
997
990
> [!NOTE]
998
991
> Two-node configurations are only supported on Azure Stack Edge Pro GPU and Azure Stack Edge Pro 2 devices.
999
992
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.
1001
994
1002
995
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).
0 commit comments