Not too long ago, I got a DL380 Gen10 from HPE to deploy the Azure Stack Development Kit. I had been limping along with a couple Frankstein systems running on Gen8 and Gen9 hardware. They had slow disks, not enough storage, and not enough RAM. This new beast has 384GB of RAM, 20 cores, and SSDs for the OS disk. Basically it’s awesome, and I am a very happy nerd. Since the early days of the ASDK, when it was just a little Technical Preview, there have appeared a growing library of scripts to help with the deployment of the ASDK. Since I am deploying the latest version today (1811), I thought it might be a good idea to share some helper scripts I put together to make the process a bit faster.
Below are two scripts that will help grease the deployment wheels. The first is meant to simplify the download of the ASDK files. If you are deploying for the first time, you should fill out the form on the Microsoft website and agree to whatever the EULA is for the ASDK. That being said, if this is the 20th time you’re deploying the ASDK, filling out the form and getting the downloader executable is a bit of a hassle. This script replaces that downloader executable and just pulls down the bin files and extraction executable to the location of your choice. It also grabs the askd-installer.ps1 file for good measure. After all, once you have the VHDX to deploy the ASDK, the next natural step is to actually deploy the dang thing.
The second script helps out with the process of pulling and running the ConfigASDK.ps1 script written by the excellent Matt McSpirit. I based it off this post by Kristopher Turner. I added a little piece to download the Server 2016 ISO. That’s an eval copy, so don’t be surprised if it expires after 120 days. Of course, after 120 days you’re probably going to redeploy the ASDK to get the latest version anyhow.
I hope this helps out someone besides me. I would also recommend checking out Kenny Lowe’s post about exposing your ASDK to your network.