In the 78 minute long Best of 2015 – OS Deployment, MDT, ConfigMgr (and some other stuff) video, presented by Mikael Nystrom and Johan Arwidmark, we have gathered our favorite things from 2015. A mix of war stories, demos, events, deployments and more… Here are the links mentioned in that video (also available as annotations during the video).
As you probably have notices, at least if you use Twitter, is that the new generation of ConfigMgr products were released yesterday (December 3). The first version is ConfigMgr v1511, and here is an hydration kit that’s builds it for you.
You probably know that a bug in MDT 2013 Update 1 causes some very strange permissions being set on the deployment share created via Deployment Workbench. Here is a script that sets them to a working level. If needed, modify the script to fit your environment, for example, you may not use the VIAMONSTRAMDT_BA account.
The Intel NUC devices have turned out to be a great machine for a small but efficient Hyper-V host. The challenge is that Intel doesn’t get that, and in fact block their network adapter device drivers for Windows Server 2016. In this post you learn how to fix this properly.
The latest Windows 10 ADK update, build 10586, was silently released a few days ago (Thanks Keith Garner for tweeting the download link). In this post you learn about what’s changed.
In this post you learn to upgrade an existing ConfigMgr 2012 R2 SP1 environment to Cumulative Update 2 (CU2).
One of the many restrictions of the Windows 10 inplace-upgrade process is that it doesn’t support changing BIOS to EUFI (see my Windows 10 Upgrade Limitations post for complete listing). So, do you really need UEFI to deploy Windows 10? The answer is no, Windows 10 can absolutely be deployed to BIOS-based machines, but some of it’s features does require UEFI. Here is the (current)list:
Earlier today I had the opportunity to troubleshoot a ConfigMgr 2012 R2 SP1 CU1 server that could happily PXE boot Generation 1 VMs, but not Generation 2 VMs. The SMSPXE.Log had really no info than it tried to serve the wdsmgfw.efi to the client. but then nothing happened.
Microsoft Hardware Assessment and Planning Toolkit (MAP) 9.3 is released and is available for download.
Finding Windows 10 drivers, or drivers in general, for the Surface 3 machine can be a bit challenging since Microsoft decided to change the search experience for their download site from poor to worse. Anyway, the trick is to Google/Bing for the Surface Pro 3 drivers which are available here: http://www.microsoft.com/en-us/download/details.aspx?id=38826
With the release of MDT 2013 Update 1 (build 8298) Microsoft pulled the download for the old MDT 2013 (without Update 1, build 5019)
I have updated one of my Hydration Kit to use MDT 2013 Update 1 (and Windows ADK 10).
This feels like the never ending story… I created an ADSI plugin for WinPE 2.0 back in 2007/2008-ish, and for every new release of WinPE I get requests for a new version. So here it is.
The last few weeks I have stumbled across quite a number of customers wanting to set Internet Explorer 11 as the default browser in Windows 10.
Here are the slides from my Windows 10 Deployment workshop at IT / Dev Connetions 2015 at the ARIA hotel in Las Vegas.
In this post you learn to upgrade an existing MDT 2013 environment, with or without ConfigMgr integration, to MDT 2013 Update 1. The guide is divided in two parts:
If your mission is to deploy Windows 10, you want to read this!
With Windows Server 2016 Technical Preview 2 Microsoft added the Nano Server, and in this guide you learn to create an bootable ISO file that deploys it. If you want you can also copy the content of the ISO file to a USB stick, make it active, and then you can deploy the Nano Server from the USB stick too.
With Windows Server 2016 Technical Preview 2 Microsoft added the Nano Server, and in this guide you learn learn how to deploy the Nano Server using MDT 2013 Update 1 Preview. The article has three main parts to it:
If you upgraded your ConfigMgr 2012 R2 SP1 server to Windows 10 ADK you probably learned that some of the existing Windows 7 deployment no longer works. More specifically, it’s the computer refresh and computer replace scenarios that fails because an issue with loadstate on Windows 7 machines. The simple root cause is that loadstate requires additional files when run on Windows 7, files that are not in the USMT package.