With Azure Stack TP3, we’ve worked with customers to improve the product through numerous bug fixes, updates, and deployment reliability & compatibility improvements from TP2. With Azure Stack TP3 customers can:
Deploy with ADFS for disconnected scenarios
Start using Azure Virtual Machine Scale Sets for scale out workloads
Syndicate content from the Azure Marketplace to make available in Azure Stack
Use Azure D-Series VM sizes
Deploy and create templates with Temp Disks that are consistent with Azure
Take comfort in the enhanced security of an isolated administrator portal
Take advantage of improvements to IaaS and PaaS functionality
Use enhanced infrastructure management functionality, such as improved alerting
Shortly after TP3, Azure Functions will be available to run on TP3, followed by Blockchain, Cloud Foundry, and Mesos templates. Continuous innovation will be delivered to Azure Stack up to general availability and beyond. TP3 is the final planned major Technical Preview before Azure Stack integrated systems will be available for order in mid-CY17.
During Ignite 2016 in Atlanta, Microsoft announced the technical preview 2 of AzureStack and finally now this friday I got my hardware available (the dang server was not responding on the ILO port and I had to go to the datacenter to give it a kung-fu-devops-kick) so I could deploy the new bits.
First things first! Read the documentation about how to proceed and you will more likely succeed in your deployment!
The download for AzureStack is 20 GB so if you have a slow internet connection it will take some time!
Before getting started i suggest you to run the pre-check script that can tell you if there is some immediate issues,
And then you can unpack and follow the instructions to prepare to vhd-boot into the cloudbuilder disk with the next script:
Once rebooted you want to make sure that you only have one nic enabled and then kick of the deployment which will take about 2-3 hours if you have a decent hardware like me 😛
As you can see the install process uses both desired state and powershell direct (which is a lovely feature in Hyper-V 2016)
And if you are patient and then log in as a azurestack\AzureStackAdmin on the physical machine you will see the status of the deployment. Do not log in as a local user on the server and try to start the deployment again!
Hopefully you will end up with the same result as me:
And then you can log in to the VM MAS-CON01 to connect to the portal,
Maybe I was lucky but I believe that the Stack-Team has done some serious work since TP1 and the deployment process have been thoroughly developed, tested and works really good now.