Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ArcBox - Update custom password scenario #504

Merged
merged 1 commit into from
Feb 13, 2025
+6 −6
Merged

ArcBox - Update custom password scenario #504

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/azure_jumpstart_arcbox/DataOps/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -267,7 +267,7 @@ By design, ArcBox doesn't open port 3389 on the network security group. Therefor

> **Note:** When using Azure Bastion, the desktop background image isn't visible. Therefore some screenshots in this guide may not exactly match your experience if you are connecting to _ArcBox-Client_ with Azure Bastion.

- If the _`windowsAdminPassword`_ parameter is not specified during deployment, the password is automatically generated and stored in the Key Vault. Select "Password from Azure Key Vault" as the authentication type and use "windowsAdminPassword" as the Azure Key Vault secret name.
- Select "Password from Azure Key Vault" as the authentication type and use "windowsAdminPassword" as the Azure Key Vault secret name.

![Screenshot showing connecting to the VM using Bastion and Key Vault](./bastion_connect_password.png)

Expand Down Expand Up @@ -296,7 +296,7 @@ Example:

> **Note:** Logging into the Client VM without the UPN format [email protected]_ will prevent the automation from running automatically.

- If the _`windowsAdminPassword`_ parameter is not specified during deployment, the password is automatically generated and stored in the Key Vault. Copy the "windowsAdminPassword" secret value from the Key Vault to log in.
- If the _`windowsAdminPassword`_ parameter is specified during deployment, use the provided password to log in. If not specified, the password is automatically generated and stored in the Key Vault. Copy the "windowsAdminPassword" secret value from the Key Vault to log in.

#### The Logon scripts

Expand Down
4 changes: 2 additions & 2 deletions docs/azure_jumpstart_arcbox/DevOps/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -309,7 +309,7 @@ By design, ArcBox doesn't open port 3389 on the network security group. Therefor

![Screenshot showing connecting to the VM using RDP](./rdp_connect.png)

> **Note:** If the _`windowsAdminPassword`_ parameter is not specified during deployment, the password is automatically generated and stored in the Key Vault. Copy the "windowsAdminPassword" secret value from the Key Vault to log in.
> **Note:** If the _`windowsAdminPassword`_ parameter is specified during deployment, use the provided password to log in. If not specified, the password is automatically generated and stored in the Key Vault. Copy the "windowsAdminPassword" secret value from the Key Vault to log in.

#### Connect using Azure Bastion

Expand All @@ -319,7 +319,7 @@ By design, ArcBox doesn't open port 3389 on the network security group. Therefor

> **Note:** When using Azure Bastion, the desktop background image isn't visible. Therefore some screenshots in this guide may not exactly match your experience if you are connecting to _ArcBox-Client_ with Azure Bastion.

- If the _`windowsAdminPassword`_ parameter is not specified during deployment, the password is automatically generated and stored in the Key Vault. Select "Password from Azure Key Vault" as the authentication type and use "windowsAdminPassword" as the Azure Key Vault secret name.
- Select "Password from Azure Key Vault" as the authentication type and use "windowsAdminPassword" as the Azure Key Vault secret name.

![Screenshot showing connecting to the VM using Bastion and Key Vault](./bastion_connect_password.png)

Expand Down
4 changes: 2 additions & 2 deletions docs/azure_jumpstart_arcbox/ITPro/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -214,7 +214,7 @@ By design, ArcBox doesn't open port 3389 on the network security group. Therefor

![Screenshot showing connecting to the VM using RDP](./rdp_connect.png)

> **Note:** If the _`windowsAdminPassword`_ parameter is not specified during deployment, the password is automatically generated and stored in the Key Vault. Copy the "windowsAdminPassword" secret value from the Key Vault to log in.
> **Note:** - If the _`windowsAdminPassword`_ parameter is specified during deployment, use the provided password to log in. If not specified, the password is automatically generated and stored in the Key Vault. Copy the "windowsAdminPassword" secret value from the Key Vault to log in.

#### Connect using Azure Bastion

Expand All @@ -224,7 +224,7 @@ By design, ArcBox doesn't open port 3389 on the network security group. Therefor

> **Note:** When using Azure Bastion, the desktop background image isn't visible. Therefore some screenshots in this guide may not exactly match your experience if you are connecting to _ArcBox-Client_ with Azure Bastion.

- If the _`windowsAdminPassword`_ parameter is not specified during deployment, the password is automatically generated and stored in the Key Vault. Select "Password from Azure Key Vault" as the authentication type and use "windowsAdminPassword" as the Azure Key Vault secret name.
- Select "Password from Azure Key Vault" as the authentication type and use "windowsAdminPassword" as the Azure Key Vault secret name.

![Screenshot showing connecting to the VM using Bastion and Key Vault](./bastion_connect_password.png)

Expand Down
Loading