Post ASDK installation configuration tasks
After installing the ASDK, there are a few recommended post-installation configuration changes be made.
Install Azure Stack PowerShell
Azure Stack compatible Azure PowerShell modules are required to work with Azure Stack.
PowerShell commands for Azure Stack are installed through the PowerShell Gallery. To register the PSGallery repository, open an elevated PowerShell session and run the following command:
Set-PSRepository ` -Name "PSGallery" ` -InstallationPolicy Trusted
Azure Stack compatible AzureRM modules are installed through API version profiles. Azure Stack requires the 2017-03-09-profile API version profile, which is available by installing the AzureRM.Bootstrapper module.
You can install the Azure Stack PowerShell with or without internet connectivity to the ASDK host computer:
With an internet connection from the ASDK host computer. Run the following PowerShell script to install these modules on your development kit installation:
# Install the AzureRM.Bootstrapper module. Select Yes when prompted to install NuGet Install-Module ` -Name AzureRm.BootStrapper # Install and import the API Version Profile required by Azure Stack into the current PowerShell session. Use-AzureRmProfile ` -Profile 2017-03-09-profile -Force Install-Module ` -Name AzureStack ` -RequiredVersion 1.2.11
If the installation is successful, the AzureRM and AzureStack modules are displayed in the output.
Without an internet connection from the ASDK host computer. In a disconnected scenario, you must first download the PowerShell modules to a machine that has internet connectivity using the following PowerShell commands:
$Path = "<Path that is used to save the packages>" Save-Package ` -ProviderName NuGet ` -Source https://www.powershellgallery.com/api/v2 ` -Name AzureRM ` -Path $Path ` -Force ` -RequiredVersion 1.2.11 Save-Package ` -ProviderName NuGet ` -Source https://www.powershellgallery.com/api/v2 ` -Name AzureStack ` -Path $Path ` -Force ` -RequiredVersion 1.2.11
Next, copy the downloaded packages to the ASDK computer and register the location as the default repository and install the AzureRM and AzureStack modules from this repository:
$SourceLocation = "<Location on the development kit that contains the PowerShell packages>" $RepoName = "MyNuGetSource" Register-PSRepository ` -Name $RepoName ` -SourceLocation $SourceLocation ` -InstallationPolicy Trusted Install-Module AzureRM ` -Repository $RepoName Install-Module AzureStack ` -Repository $RepoName
Download the Azure Stack tools
AzureStack-Tools is a GitHub repository that hosts PowerShell modules for managing and deploying resources to Azure Stack. To obtain these tools, clone the GitHub repository or download the AzureStack-Tools folder by running the following script:
# Change directory to the root directory. cd \ # Enforce usage of TLSv1.2 to download the Azure Stack tools archive from GitHub [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12 invoke-webrequest ` https://github.com/Azure/AzureStack-Tools/archive/master.zip ` -OutFile master.zip # Expand the downloaded files. expand-archive master.zip ` -DestinationPath . ` -Force # Change to the tools directory. cd AzureStack-Tools-master
Validate the ASDK installation
To ensure that your ASDK deployment was successful, you can use the Test-AzureStack cmdlet by following these steps:
- Log in as AzureStack\CloudAdmin on the ASDK host computer.
- Open PowerShell as an administrator (not PowerShell ISE).
Enter-PSSession -ComputerName AzS-ERCS01 -ConfigurationName PrivilegedEndpoint
The tests take a few minutes to complete. If the installation was successful, the output looks something like:
If there was a failure, follow the troubleshooting steps to get help.
Activate the administrator and tenant portals
After deployments that use Azure AD, you must activate both the Azure Stack administrator and tenant portals. This activation consents to giving the Azure Stack portal and Azure Resource Manager the correct permissions (listed on the consent page) for all users of the directory.
For the administrator portal, navigate to https://adminportal.local.azurestack.external/guest/signup, read the information, and then click Accept. After accepting, you can add service administrators who are not also directory tenant administrators.
For the tenant portal, navigate to https://portal.local.azurestack.external/guest/signup, read the information, and then click Accept. After accepting, users in the directory can sign in to the tenant portal.
If the portals are not activated, only the directory administrator can sign in and use the portals. If another user signs in, they will see an error that tells them that the administrator has not granted permissions to other users. When the administrator does not natively belong to the directory Azure Stack is registered to, the Azure Stack directory must be appended to the activation URL. For example, if Azure Stack is registered to fabrikam.onmicrosoft.com and the admin user is email@example.com, navigate to https://portal.local.azurestack.external/guest/signup/fabrikam.onmicrosoft.com to activate the portal.
Reset the password expiration policy
To make sure that the password for the development kit host doesn't expire before your evaluation period ends, follow these steps after you deploy the ASDK.
To change the password expiration policy from Powershell:
From an elevated Powershell console, run the command:
Set-ADDefaultDomainPasswordPolicy -MaxPasswordAge 180.00:00:00 -Identity azurestack.local
To change the password expiration policy manually:
- On the development kit host, open Group Policy Management (GPMC.MMC) and navigate to Group Policy Management – Forest: azurestack.local – Domains – azurestack.local.
- Right-click Default Domain Policy and click Edit.
- In the Group Policy Management Editor, navigate to Computer Configuration – Policies – Windows Settings – Security Settings – Account Policies – Password Policy.
- In the right pane, double-click Maximum password age.
- In the Maximum password age Properties dialog box, change the Password will expire in value to 180, and then click OK.