Azure Azure Stack Configuration

Azure Stack – Azure Stack Development Kit Post Deployment

Bildergebnis für post deployment graphic microsoft azure stack

As I mentioned in my previous blog post, I want to get some hands on Azure Stack 1808 and therefore I will write down a couple of post to share my steps, impressions and experience. The posts are not a tutorial how to set up Azure Stack in production, it is more like to get it up and running to test features and see how it works under the hood.

After you successfully deployed Azure Stack Development Kit in your Azure VM you need some post deployment steps to fulfil. First you need to trust PowerShell gallery so you can download necessary PowerShell modules like AzureRM and  other modules. Make sure you execute these commands on your Azure Stack host!

Set-PSRepository -Name "PSGallery" -InstallationPolicy Trusted

# 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 2018-03-01-hybrid -Force

# Install Azure Stack Module Version 1.5.0.
Install-Module -Name AzureStack -RequiredVersion 1.5.0

If this step succeeded we need to download the Azure Stack tools. The Azure Stack tools are a bunch of tools to administer your Azure Stack which are needed to administer ASDK. These are required e.g. to register Azure Stack your Azure Active Directory. Execute the following commands on the ASDK host again. This will download and extract the tools from GitHub

# 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 -OutFile

# Expand the downloaded files.
expand-archive -DestinationPath . -Force

# Change to the tools directory.
cd AzureStack-Tools-master

If you want you can then test your ASDK installation. This command will use PowerShell remoting to access the privileged endpoint VM AzS-ERCS01 and run the Test-AzureStack command…

# Connect to the privileged endpoint VM
Enter-PSSession -ComputerName AzS-ERCS01 -ConfigurationName PrivilegedEndpoint

# Run the test command

It should look something like this…


I got a couple of warnings because I already have deployed some stuff and currently some updates are stressing my system Smile.

From here on you just need to modify the default domain policy, setting the password age to 180 days. This prevents from expiring the ASDK passwords before the evaluation periods ends. See the GPMC.msc started from my host…


…and in the PowerShell console executed on the ASDK host…


That’s it, if you need some multi-tenancy scenario there are other steps to make. I just need an Azure Stack joined to Azure Active Directory, which will be documented in my next post. All the steps I have described here are written down here. In my opinion it is sometimes easier to read a blog post because it is more “real-world” than following the documentation.

Have fun!

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.