Back in December, the ViaMonstra hydration kit was updated to support Server (and SQL) 2016. You can follow the post here to set it up. We get a lot of questions offline about customizing the kit, so here is a summary of customization.
Default behavior for failed deployments in ConfigMgr is for the error box to stick around for 15 minutes before rebooting. That’s plenty of time if you have nothing better to do than watch progress bars and wait for failures. But what if you have work to do and you need the error to stick around a bit longer?
By: Nathan Kofahl
Here are links to all blog posts mentioned in the OS Deployment – Best of 2016 video with me an Mikael Nystrom.
…just kidding. I see the question posted a lot in the community forums – what OS to use for a lab environment. The main theme to the question is always the same thing – the technician wants to be able to use data deduplication. Deduplication, if you're not familiar with it, maximizes your storage space […]
As you probably know, the various driver vendors do not exactly follow the same standard for labeling their models. This is where the concept of ModelAlias comes in. It just a script that normalizes vendor model names to their real model names. In this post, you learn to use ModelAlias for driver management in ConfigMgr.
I’ve been playing around with Server 2016 and the ViaMonstra Hydration Kit for ConfigMgr. If you want your lab environment to be able to connect to the internet, you know (if you’ve been reading our books) that you need to setup a virtual router. In Kent’s book (System Center 2012 R2: Mastering the Fundamentals), we actually walk you through setting up a very complex environment that requires you to use our “GW01” or a Vyatta virtual router in order for your lab to get out to the internet.
Here are notes from Getting ConfigMgr Up and Running in 60 Minutes or Less presented by Johan Arwidmark and complied by Ami Casto @IT/Dev Connections (If you’re not on Twitter, get on Twitter!!)