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.

It has been a while, since I chartered the waters of WMI and Configuration Manager, so pardon any silly mistakes made. One of my friend from PSBUG asked me few questions revolving around creating packages & programs in ConfigMgr using PowerShell. Every ConfigMgr admin knows that new Application model has been introduced in ConfigMgr 12 but the Packages are here to stay for a while. Packages and Programs are ideal for deploying Scripts (one time or reoccurring ones) and better suited for deploying apps during OSD (heard this one). ConfigMgr ideally has 3 ways of working with it and below is the pic which says it all : The post is broken up in 3 parts (based on how you use ConfigMgr): GUI Way - Doing this to show background on how we do it manually. Cmdlet Way - using the CM cmdlets to create the package and program WMI Way - exploring WMI to do the same.