After the installation is finished, there are more tasks before you could call Azure Stack ready for the customers. Theses include the following:
- Installing Azure Stack PowerShell and AzureRM modules
- Installing Azure Stack tools
- Registering ASDK to Azure
- Adding Microsoft VM Extensions to gallery from marketplace
- MySQL and SQL resource provider installation
- Adding SQL Server and MySQL hosting servers
- App service installation and configuration (certificates generation)
- Setting default quotas and a base plan and offer that contain all deployed services
- Configuring Python and Azure CLI for usage with ASDK
You could either run all these tasks manually (per the description available within the Microsoft Documentation, accessible here at https://github.com/mattmcspirit/azurestack) or using a script that has been created by Matt McSpirit.
As it makes configurations quite easy, I would suggest using it every time following the Azure Stack update cycle. It runs for another six to seven hours and a sample should look as follows:
.ConfigASDK.ps1 -azureDirectoryTenantName "contoso.onmicrosoft.com" -authenticationType AzureAD -downloadPath "D:ASDKfiles" -ISOPath "D:WS2016EVALISO.iso" -azureStackAdminPwd 'YourPassword' -VMpwd 'YourPassword' -azureAdUsername "[email protected]" -azureAdPwd 'YourAADPassword' -registerASDK -useAzureCredsForRegistration -azureRegSubId "YourAzureSubscriptionID"
If you run into issues while the script is running, you should correct the setup and simply rerun it.
This should be the last step to finally start with Azure Stack testing.