This Kit builds a complete ConfigMgr v1606/1610 with Windows Server 2016 and SQL Server 2016 SP1 infrastructure, and some (optional) supporting servers. This kit is tested on both Hyper-V and VMware virtual platforms, but should really work on any virtualization platform that can boot from an ISO. The kit offers a complete setup of both a primary site server running ConfigMgr Current Branch v1606 (server CM01), as well as a primary site server running ConfigMgr Technical Preview Branch v1610 (server CM02). You also find guidance on upgrading these platform to the latest build.
Here is a step-by-step quick guide on building the perfect Windows Server 2016 reference image. This guide is divided in two parts: The first part covers how to create a Windows Server 2016 reference image in just a few minutes using offline servicing. The quick-and-dirty method. The second part is about creating a Windows Server 2016 reference image using MDT 8443. The SHINY method.
The end of 2016 is soon upon us, but before the holidays and hopefully some well-deserved time off, it’s time for a free live event: Windows 10 Deployment – Notes from the field. 1 hour of deployment tips and tricks presented by Johan Arwidmark
Unless you have been living under a rock the last few days, you haven’t missed the Every Windows 10 in-place Upgrade is a SEVERE Security risk blog post from Sami Laiho about the Shift-F10 security issue for Windows 10. Allowing a non-admin to get access to an BitLocker encrypted volume during an inplace-upgrade process of Windows 10.
A quite shiny weekend turned into even shinier with the release of Windows ADK (10) Insider Preview v14965.
During the Microsoft Ignite 2016 OS Deployment pre-conference, I demonstrated the ConfigMgr inplace-upgrade task sequence, and if you want to specify additional command-line options you can use the “not-so-easy-to-find” OSDSetupAdditionalUpgradeOptions variable. For example for using the /InstallLangPacks or /ReflectDrivers switches.
Here is a post on how to configure the Thunderbolt Software to not require admin rights when connecting a new Thunderbolt device.
Just wanted to post a quick reminder that ConfigMgr by default is logging info not only to it’s own log files, which are in the ConfigMgr installation directory, which is typically not on the C: drive, at least, should not be on the C: drive, but also to the IIS logs, which typically are on the C: drive. Obviously it is not good if the C: fills up, because then the site server dies. So some house-keeping is useful.
Here is a step-by-step guide to configure a MDT Lite Touch or ConfigMgr task sequence to move a computer to another OU during deployment. The webservice used in this guide does the same job as Maik Koster’s version available here: http://maikkoster.com/moving-computers-in-active-directory-during-mdt-deployments-step-by-step but I have include the C# source code for my version, so you can review, or modify it if you want to.
Just stumbled across the Zabbix monitoring platform (http://zabbix.com ) while working with a customer in Austin this week, so I figured I’ll set it up in my lab an test it out for a bit.