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-stack/asdk/asdk-admin-basics.md
+3-5Lines changed: 3 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,10 +4,8 @@ description: Learn how to do basic admin tasks for the Azure Stack Development K
4
4
author: sethmanheim
5
5
6
6
ms.topic: article
7
-
ms.date: 10/29/2021
7
+
ms.date: 08/19/2024
8
8
ms.author: sethm
9
-
ms.reviewer: misainat
10
-
ms.lastreviewed: 10/15/2019
11
9
12
10
# Intent: As an ASDK user, I want to familiarize myself with the admin basics so my users can become productive as quickly as possible.
13
11
# Keyword: asdk admin basics
@@ -16,22 +14,22 @@ ms.lastreviewed: 10/15/2019
16
14
17
15
18
16
# ASDK admin basics
17
+
19
18
There are several things you need to know if you're new to Azure Stack Development Kit (ASDK) administration. This guidance provides an overview of your role as an Azure Stack operator in the evaluation environment. Familiarizing yourself with this info ensures your test users will become productive as quickly as possible.
20
19
21
20
First, you should review the [What is Azure Stack Development Kit?](asdk-what-is.md) article to make sure you understand the purpose of the ASDK and its limitations. You should use the development kit as a "sandbox," where you can evaluate Azure Stack to develop and test your apps in a non-production environment.
22
21
23
22
Like Azure, Azure Stack innovates rapidly so we'll regularly release new builds of the ASDK. However, you can't upgrade the ASDK like you can Azure Stack integrated systems deployments. So, if you want to move to the latest build, you must completely [redeploy the ASDK](asdk-redeploy.md). You can't apply update packages. This process takes time, but the benefit is that you can try out the latest features as soon as they become available.
24
23
25
24
## What account should I use?
25
+
26
26
There are a few account considerations you should be aware of when managing Azure Stack. This is especially true in deployments using Windows Server Active Directory Federation Services (AD FS) as the identity provider instead of Microsoft Entra ID. The following account considerations apply to both Azure Stack integrated systems and ASDK deployments:
|AzureStack\AzureStackAdmin|ASDK host admin<br><br>Can be used to sign in to the Azure Stack administrator portal<br><br>Access to view and administer Service Fabric rings|ASDK host admin<br><br>No access to the Azure Stack administrator portal<br><br>Access to view and administer Service Fabric rings<br><br>No longer owner of the Default Provider Subscription (DPS)|
32
32
|AzureStack\CloudAdmin|Can access and run permitted commands within the Privileged Endpoint|Can access and run permitted commands within the Privileged Endpoint<br><br>Can't sign in to the ASDK host<br><br>Owner of the Default Provider Subscription (DPS)|
33
-
|Microsoft Entra Global Administrator|Used during installation<br><br>Owner of the Default Provider Subscription (DPS)|Not applicable|
34
-
|
35
33
36
34
## What tools do I use to manage?
37
35
You can use the Azure Stack administrator portal `https://adminportal.local.azurestack.external` or PowerShell to manage Azure Stack. The easiest way to learn the basic concepts is through the portal. If you want to use PowerShell, you need to install [PowerShell for Azure Stack](asdk-post-deploy.md#install-azure-stack-powershell) and [download the Azure Stack tools from GitHub](asdk-post-deploy.md#download-the-azure-stack-tools).
Copy file name to clipboardExpand all lines: azure-stack/asdk/asdk-deploy-considerations.md
+4-8Lines changed: 4 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,10 +4,8 @@ description: Learn about the hardware, software, and environment requirements fo
4
4
author: sethmanheim
5
5
6
6
ms.topic: article
7
-
ms.date: 09/23/2020
7
+
ms.date: 08/19/2024
8
8
ms.author: sethm
9
-
ms.reviewer: misainat
10
-
ms.lastreviewed: 09/23/2020
11
9
12
10
# Intent: As an ASDK user, I want to know the requirements for properly deploying the ASDK.
13
11
# Keyword: asdk requirements
@@ -91,7 +89,7 @@ If your environment isn't connected to the internet, or you don't want to use Mi
91
89
<aname='azure-active-directory-accounts'></a>
92
90
93
91
### Microsoft Entra accounts
94
-
To deploy Azure Stack by using a Microsoft Entra account, you must prepare a Microsoft Entra account before you run the deployment PowerShell script. This account becomes the Global Admin for the Microsoft Entra tenant. It's used to provision and delegate apps and service principals for all Azure Stack services that interact with Microsoft Entra ID and Graph API. It's also used as the owner of the default provider subscription (which you can later change). You can sign in to your Azure Stack system's administrator portal by using this account.
92
+
To deploy Azure Stack by using a Microsoft Entra account, you must prepare a Microsoft Entra account before you run the deployment PowerShell script. This account becomes the administrator for the Microsoft Entra tenant. It's used to provision and delegate apps and service principals for all Azure Stack services that interact with Microsoft Entra ID and Graph API. It's also used as the owner of the default provider subscription (which you can later change). You can sign in to your Azure Stack system's administrator portal by using this account.
95
93
96
94
1. Create a Microsoft Entra account that is the directory admin for at least one Microsoft Entra ID. If you already have one, you can use that. Otherwise, you can create one for free at [https://azure.microsoft.com/free/](https://azure.microsoft.com/free/) (in China, visit <https://go.microsoft.com/fwlink/?LinkID=717821> instead). If you plan to later [register Azure Stack with Azure](asdk-register.md), you must also have a subscription in this newly created account.
97
95
@@ -100,13 +98,11 @@ To deploy Azure Stack by using a Microsoft Entra account, you must prepare a Mic
100
98
101
99
|**Microsoft Entra account**|**Supported?**|
102
100
| --- | --- |
103
-
| Work or school account with valid global Azure subscription |Yes |
104
-
| Microsoft Account with valid global Azure subscription |Yes |
101
+
| Work or school account with valid Azure subscription |Yes |
102
+
| Microsoft Account with valid Azure subscription |Yes |
105
103
| Work or school account with valid China Azure subscription |Yes |
106
104
| Work or school account with valid US Government Azure subscription |Yes |
107
105
108
-
After deployment, Microsoft Entra global admin permission isn't required. However, some operations may require the global admin credential. Examples of such operations include a resource provider installer script or a new feature requiring a permission to be granted. You can either temporarily reinstate the account's global admin permissions or use a separate global admin account that's an owner of the *default provider subscription*.
109
-
110
106
## Network
111
107
### Switch
112
108
One available port on a switch for the ASDK machine.
A few minutes into ASDK installation you'll be prompted for Microsoft Entra credentials. Provide the global admin credentials for your Microsoft Entra tenant.
88
-
89
-
After deployment, Microsoft Entra global admin permission isn't required. However, some operations may require the global admin credential. Examples of such operations include a resource provider installer script or a new feature requiring a permission to be granted. You can either temporarily reinstate the account's global admin permissions or use a separate global admin account that's an owner of the *default provider subscription*.
85
+
A few minutes into ASDK installation you'll be prompted for Microsoft Entra credentials. Provide the Microsoft Entra admin credentials for your tenant.
90
86
91
87
### Deploy Azure Stack using AD FS
92
88
To deploy the ASDK **using AD FS as the identity provider**, run the following PowerShell commands (you just need to add the -UseADFS parameter):
@@ -115,15 +111,15 @@ If your Microsoft Entra identity is only associated with **one** Microsoft Entra
115
111
```powershell
116
112
cd C:\CloudDeployment\Setup
117
113
$adminpass = Get-Credential Administrator
118
-
$aadcred = Get-Credential "<Azure AD global administrator account name>"
.\InstallAzureStackPOC.ps1 -AdminPassword $adminpass.Password -InfraAzureDirectoryTenantAdminCredential $aadcred -TimeServer 52.168.138.145 #Example time server IP address.
120
116
```
121
117
122
118
If your Microsoft Entra identity is associated with **greater than one** Microsoft Entra directory:
123
119
```powershell
124
120
cd C:\CloudDeployment\Setup
125
121
$adminpass = Get-Credential Administrator
126
-
$aadcred = Get-Credential "<Azure AD global administrator account name>" #Example: [email protected]
.\InstallAzureStackPOC.ps1 -AdminPassword $adminpass.Password -InfraAzureDirectoryTenantAdminCredential $aadcred -InfraAzureDirectoryTenantName "<Azure AD directory in the form of domainname.onmicrosoft.com or an Azure AD verified custom domain name>" -TimeServer 52.168.138.145 #Example time server IP address.
Copy file name to clipboardExpand all lines: azure-stack/asdk/asdk-install.md
+4-7Lines changed: 4 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,10 +4,8 @@ description: Learn how to install the Azure Stack Development Kit (ASDK).
4
4
author: sethmanheim
5
5
6
6
ms.topic: article
7
-
ms.date: 05/06/2019
7
+
ms.date: 08/19/2024
8
8
ms.author: sethm
9
-
ms.reviewer: misainat
10
-
ms.lastreviewed: 02/08/2019
11
9
12
10
# Intent: As an ASDK user, I want to install the ASDK so I can start using it.
13
11
# Keyword: install asdk
@@ -34,9 +32,7 @@ The steps in this article show you how to deploy the ASDK using a graphical user
34
32
35
33

36
34
37
-
If you choose an Azure subscription identity provider, you need an internet connection, the full name of a Microsoft Entra directory tenant in the form of *domainname*.onmicrosoft.com, or a Microsoft Entra ID verified custom domain name. You also need global admin credentials for the specified directory.
38
-
39
-
After deployment, Microsoft Entra global admin permission isn't required. However, some operations may require the global admin credential. For example, a resource provider installer script or a new feature requiring a permission to be granted. You can either temporarily reinstate the account's global admin permissions or use a separate global admin account that's an owner of the *default provider subscription*.
35
+
If you choose an Azure subscription identity provider, you need an internet connection, the full name of a Microsoft Entra directory tenant in the form of *domainname*.onmicrosoft.com, or a Microsoft Entra ID verified custom domain name. You also need admin credentials for the specified directory.
40
36
41
37
When using AD FS as the identity provider, the default stamp directory service is used. The default account to sign in with is [email protected], and the password to use is the one you provided as part of setup.
42
38
@@ -67,7 +63,7 @@ The steps in this article show you how to deploy the ASDK using a graphical user
67
63
> [!TIP]
68
64
> Here you can also copy the PowerShell setup commands that'll be used to install the ASDK. This is helpful if you ever need to [redeploy the ASDK on the host computer using PowerShell](asdk-deploy-powershell.md).
69
65
70
-
8. If you're doing a Microsoft Entra deployment, you'll be prompted to enter your Microsoft Entra global admin account credentials a few minutes after setup starts.
66
+
8. If you're doing a Microsoft Entra deployment, you'll be prompted to enter your Microsoft Entra admin account credentials a few minutes after setup starts.
71
67
72
68
9. The deployment process will take a few hours, during which time the host computer will automatically reboot once. If you want to monitor the deployment progress, sign in as azurestack\AzureStackAdmin after the ASDK host restarts. When the deployment succeeds, the PowerShell console displays: **COMPLETE: Action 'Deployment'**.
73
69
> [!IMPORTANT]
@@ -85,4 +81,5 @@ If the deployment fails for some reason, you can [redeploy](asdk-redeploy.md) fr
Ensure the output returns **FullLanguage**. If any other language mode is returned, registration needs to be run on another computer or the language mode set to **FullLanguage** before continuing.
36
33
37
-
The Microsoft Entra account used for registration needs to have access to the Azure subscription and have permissions to create identity apps and service principals in the directory associated with that subscription. We recommend you register Azure Stack Hub with Azure by [creating a service account to use for registration](../operator/azure-stack-registration-role.md) rather than using global admin credentials.
34
+
The Microsoft Entra account used for registration needs to have access to the Azure subscription and have permissions to create identity apps and service principals in the directory associated with that subscription. We recommend you register Azure Stack Hub with Azure by [creating a service account to use for registration](../operator/azure-stack-registration-role.md).
Copy file name to clipboardExpand all lines: azure-stack/hci/upgrade/install-enable-network-atc.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ author: ronmiab
5
5
ms.author: robess
6
6
ms.topic: how-to
7
7
ms.reviewer: alkohli
8
-
ms.date: 08/14/2024
8
+
ms.date: 08/19/2024
9
9
#Customer intent: As a Senior Content Developer, I want to provide customers with content and steps to help them successfully install and enable Network ATC on their existing Azure Stack HCI, version 22H2 cluster.
10
10
---
11
11
@@ -132,7 +132,7 @@ In this example, there are two intents that are managed across cluster nodes.
132
132
1.**Management and compute**: This intent uses a dedicated pair of network adapter ports.
133
133
2.**Storage**: This intent uses a dedicated pair of network adapter ports.
134
134
135
-
:::image type="content" source="media/install-and-enable-network-atc/group-management-and-compute.png" alt-text="Screenshot of an Azure Stack HCI cluster with a grouped management and compute intent." lightbox="media/install-and-enable-network-atc/group-management-and-compute.png":::
135
+
:::image type="content" source="media/install-enable-network-atc/group-management-and-compute.png" alt-text="Screenshot of an Azure Stack HCI cluster with a grouped management and compute intent." lightbox="media/install-enable-network-atc/group-management-and-compute.png":::
136
136
137
137
Here's an example to implement this host network pattern:
138
138
@@ -148,7 +148,7 @@ In this example, there's a single intent managed across cluster nodes.
148
148
149
149
- **Management, Compute, and Storage**: This intent uses a dedicated pair of network adapter ports.
150
150
151
-
:::image type="content" source="media/install-and-enable-network-atc/group-all-traffic.png" alt-text="Screenshot of an Azure Stack HCI cluster with all traffic on a single intent." lightbox="media/install-and-enable-network-atc/group-all-traffic.png":::
151
+
:::image type="content" source="media/install-enable-network-atc/group-all-traffic.png" alt-text="Screenshot of an Azure Stack HCI cluster with all traffic on a single intent." lightbox="media/install-enable-network-atc/group-all-traffic.png":::
152
152
153
153
Here's an example to implement this host network pattern:
154
154
@@ -163,7 +163,7 @@ In this example, there are two intents that are managed across cluster nodes.
163
163
1. **Management**: This intent uses a dedicated pair of network adapter ports.
164
164
2. **Compute and Storage**: This intent uses a dedicated pair of network adapter ports.
165
165
166
-
:::image type="content" source="media/install-and-enable-network-atc/group-compute-and-storage.png" alt-text="Screenshot of an Azure Stack HCI cluster with a grouped compute and storage intent." lightbox="media/install-and-enable-network-atc/group-compute-and-storage.png":::
166
+
:::image type="content" source="media/install-enable-network-atc/group-compute-and-storage.png" alt-text="Screenshot of an Azure Stack HCI cluster with a grouped compute and storage intent." lightbox="media/install-enable-network-atc/group-compute-and-storage.png":::
167
167
168
168
Here's an example to implement this host network pattern:
169
169
@@ -181,7 +181,7 @@ In this example, there are three intents that are managed across cluster nodes.
181
181
2. **Compute**: This intent uses a dedicated pair of network adapter ports.
182
182
3. **Storage**: This intent uses a dedicated pair of network adapter ports.
183
183
184
-
:::image type="content" source="media/install-and-enable-network-atc/fully-disaggregated.png" alt-text="Screenshot of an Azure Stack HCI cluster with a fully disaggregated intent." lightbox="media/install-and-enable-network-atc/fully-disaggregated.png":::
184
+
:::image type="content" source="media/install-enable-network-atc/fully-disaggregated.png" alt-text="Screenshot of an Azure Stack HCI cluster with a fully disaggregated intent." lightbox="media/install-enable-network-atc/fully-disaggregated.png":::
185
185
186
186
Here's an example to implement this host network pattern:
187
187
@@ -233,7 +233,7 @@ If the **ConfigurationStatus** shows **Failed**, check to see if the error messa
233
233
234
234
In this step, you move from the node deployed with Network ATC to the next node and migrate the VMs from this second node. You must verify that the second node has the same `VMSwitch` name as the node deployed with Network ATC.
235
235
236
-
This is a non-disruptive change and can be done on all the nodes simultaneously. Run the following command:
236
+
This is a nondisruptive change and can be done on all the nodes simultaneously. Run the following command:
237
237
238
238
```powershell
239
239
#Run on the node where you configured Network ATC
@@ -269,4 +269,4 @@ Resume-ClusterNode
269
269
270
270
## Next step
271
271
272
-
Learn how to [Assess solution upgrade readiness for Azure Stack HCI](./validate-solution-upgrade-readiness.md).
272
+
Learn how to [Assess solution upgrade readiness for Azure Stack HCI](./validate-solution-upgrade-readiness.md).
0 commit comments