DexterPOSH's Blog

With an awesome and exciting features being shipped in Server 2016 TP3, I am sure you are going to take a crack at it. What better way  to deploy it n cloud in few minutes using Azure Automation Runbook. I did something similar a while back and have updated the Script to expose new parameters and by default use the Server 2016 TP3 image for now (you can override this value). Also if you are an ITPro like me and have a test LAB running on Azure then you can pass in the arguments to -DomainName and -DomainCredName parameters and the Runbook actually retrieves the Automation Credential Asset and joins the Server 2016 TP3 VM to the AD domain you have running on Azure (make sure the VM is in a Subnet which is reachable to your DC and the DNS is configured properly for the name resolution.

In my previous post, I blogged about using Azure Automation to deploy a Windows 10  Server Technical Preview VM in my test domain running on Azure. But if you noticed there were lot of things that we needed to do from the Azure portal. Being an advocate of doing all things from PowerShell I gave it another shot and below is what I found (notice the colors based on what I was able to do with PowerShell)  : 1. Get the Ground work ready (few bits possible ) 2. Create the Assets  (not possible at the moment) 3. Create a RunBook to deploy the VM (and add it to the domain) (PowerShell Rocks !) PowerShell + Get the Ground work ready As already mentioned at the moment you can't create an Azure Automation account with PowerShell, but what you can do is add a new User to Azure Active directory :) You will have to review Software Requirements and then  install the Azure AD module   Once the module named " Msonline " is installed you can very well go a...