Applies to: Azure Stack Development Kit
To deploy the Azure Stack Development Kit, you must complete the following steps:
- Download the deployment package to get the Cloudbuilder.vhdx.
- Prepare the cloudbuilder.vhdx by running the asdk-installer.ps1 script to configure the computer (the development kit host) on which you want to install development kit. After this step, the development kit host will boot to the Cloudbuilder.vhdx.
- Deploy the development kit on the development kit host.
For best results, even if you want to use a disconnected Azure Stack environment, it is best to deploy while connected to the internet. That way, the Windows Server 2016 evaluation version can be activated at deployment time. If the Windows Server 2016 evaluation version is not activated within 10 days, it shuts down.
Download and extract the development kit
Before you start the download, make sure that your computer meets the following prerequisites:
- The computer must have at least 60 GB of free disk space.
- .NET Framework 4.6 (or a later version) must be installed.
Go to the Get Started page, provide your details, and click Submit.
- Under Download the software, click Azure Stack Development Kit.
- Run the downloaded AzureStackDownloader.exe file.
- In the Azure Stack Development Kit Downloader window, follow steps 1 through 5.
- After the download completes, click Run to launch the MicrosoftAzureStackPOC.exe.
- Review the License Agreement screen and information of the Self-Extractor Wizard and then click Next.
- Review the Privacy Statement screen and information of the Self-Extractor Wizard and then click Next.
- Select the Destination for the files to be extracted, click Next.
- The default is:
:<current folder>\Microsoft Azure Stack
- The default is:
- Review the Destination location screen and information of the Self-Extractor Wizard, and then click Extract to extract the CloudBuilder.vhdx (~25 GB) and ThirdPartyLicenses.rtf files. This process will take some time to complete.
After you extract the files, you can delete the exe and bin files to recover space on the machine. Or, you can move these files to another location so that if you need to redeploy you don’t need to download the files again.
Prepare the development kit host
- Make sure that you can physically connect to the development kit host, or have physical console access (such as KVM). You must have such access after you reboot the development kit host in step 13 below.
- Make sure the development kit host meets the minimum requirements. You can use the Deployment Checker for Azure Stack to confirm your requirements.
- Sign in as the Local Administrator to your development kit host.
- Copy or move the CloudBuilder.vhdx file to the root of the C:\ drive (C:\CloudBuilder.vhdx).
Run the following script to download the development kit installer file (asdk-installer.ps1) to the c:\AzureStack_Installer folder on your development kit host.
# Variables $Uri = 'https://raw.githubusercontent.com/Azure/AzureStack-Tools/master/Deployment/asdk-installer.ps1' $LocalPath = 'c:\AzureStack_Installer' # Create folder New-Item $LocalPath -Type directory # Download file Invoke-WebRequest $uri -OutFile ($LocalPath + '\' + 'asdk-installer.ps1')
- Open an elevated PowerShell console > run the C:\AzureStack_Installer\asdk-installer.ps1 script > click Prepare vhdx.
- On the Select Cloudbuilder vhdx page of the installer, browse to and select the cloudbuilder.vhdx file that you downloaded in the previous steps.
- Optional: Check the Add drivers box to specify a folder containing additional drivers that you want on the host.
- On the Optional settings page, provide the local administrator account for the development kit host. If you don't provide these credentials, you'll need KVM access to the host during the install process below.
- Also on the Optional settings page, you have the option to set the following:
- Computername: This option sets the name for the development kit host. The name must comply with FQDN requirements and must be 15 characters or less in length. The default is a random computer name generated by Windows.
- Time zone: Sets the time zone for the development kit host. The default is (UTC-8:00) Pacific Time (US & Canada).
- Static IP configuration: Sets your deployment to use a static IP address. Otherwise, when the installer reboots into the cloudbuilder.vhx, the network interfaces are configured with DHCP.
- Click Next.
- If you chose a static IP configuration in the previous step, you must now:
- Select a network adapter. Make sure you can connect to the adapter before you click Next.
- Make sure that the IP address, Gateway, and DNS values are correct and then click Next.
- Click Next to start the preparation process.
- When the preparation indicates Completed, click Next.
- Click Reboot now to boot into the cloudbuilder.vhdx and continue the deployment process.
Deploy the development kit
Sign in as the Local Administrator to the development kit host. Use the credentials specified in the previous steps.
For Azure Active Directory deployments, Azure Stack requires access to the Internet, either directly or through a transparent proxy. The deployment supports exactly one NIC for networking. If you have multiple NICs, make sure that only one is enabled (and all others are disabled) before running the deployment script in the next section.
Open an elevated PowerShell console > run the \AzureStack_Installer\asdk-installer.ps1 script (which may be on a different drive in the Cloudbuilder.vhdx) > click Install.
- In the Type box, select Azure Cloud or ADFS.
- Azure Cloud: Azure Active Directory is the identity provider. Use this parameter to specify a specific directory where the AAD account has global admin permissions. Full name of an AAD Directory tenant in the format of .onmicrosoft.com.
- ADFS: The default stamp Directory Service is the identity provider, the default account to sign in with is firstname.lastname@example.org, and the password to use is the one you provided as part of the setup.
- Under Local administrator password, in the Password box, type the local administrator password (which must match the current configured local administrator password), and then click Next.
- Select a network adapter to use for the development kit and then click Next.
- Select DHCP or static network configuration for the BGPNAT01 virtual machine.
- DHCP (default): The virtual machine gets the IP network configuration from the DHCP server.
- Static: Only use this option if DHCP can’t assign a valid IP address for Azure Stack to access the Internet. A static IP address must be specified with the subnetmask length (for example, 10.0.0.5/24).
- Optionally, set the following values:
- VLAN ID: Sets the VLAN ID. Only use this option if the host and AzS-BGPNAT01 must configure VLAN ID to access the physical network (and Internet).
- DNS forwarder: A DNS server is created as part of the Azure Stack deployment. To allow computers inside the solution to resolve names outside of the stamp, provide your existing infrastructure DNS server. The in-stamp DNS server forwards unknown name resolution requests to this server.
- Time server: Sets a specific time server.
- Click Next.
- On the Verifying network interface card properties page, you'll see a progress bar.
- If it says An update cannot be downloaded, follow the instructions on the page.
- When it says Completed, click Next.
- On Summary page, click Deploy.
- If you're using an Azure Active Directory deployment, you'll be asked to enter your Azure Active Directory global administrator account credentials.
The deployment process can take a few hours, during which the system automatically reboots once.
If you want to monitor the deployment progress, sign in as azurestack\AzureStackAdmin. If you sign in as a local admin after the machine is joined to the domain, you won't see the deployment progress. Do not rerun deployment, instead sign in as azurestack\AzureStackAdmin to validate that it's running.
When the deployment succeeds, the PowerShell console displays: COMPLETE: Action ‘Deployment’.
If the deployment fails, you can use the following PowerShell rerun script from the same elevated PowerShell window:
cd c:\CloudDeployment\Setup .\InstallAzureStackPOC.ps1 -Rerun
This script will restart the deployment from the last step that succeeded.
Or, you can redeploy from scratch.
Reset the password expiration to 180 days
To make sure that the password for the development kit host doesn't expire too soon, follow these steps after you deploy:
- On the development kit host, open Group Policy Management and navigate to Group Policy Management – Forest: azurestack.local – Domains – azurestack.local.
- Right click on MemberServer 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 on Maximum password age.
- In the Maximum password age Properties dialog box, change the Password will expire in value to 180, then Click OK.