When using MDT 2013 Update 2 (Lite Touch) for your deployments the default behavior is to run every task sequence action as the local Administrator account. In addition to this, MDT also connects to the deployment share using the account you start the deployment with. Either typed in via MDT deployment wizard login dialog box, or automated via bootstrap.ini. But what if you want to run the task sequence, at least the last part of it, as a different user in order to access resources on other servers than the deployment server? Or simply to install applications as a different user.
Over the years I have been using a few different scripts to have the task sequence send an email when the deployment is completed. For example this post: Configure MDT 2010 to send an email when deployment is completed. Another common way to do this is to use status filter rules in ConfigMgr. A good example is the Send an email when OSD completes a deployment post by Benoit Lecours.
It’s been two great weeks, I’ve been travelling the US presenting Windows 10 trainings and sessions in Phoenix, Austin and Dallas (SCU 2016). But, it turned out I said something wrong, on all of them too, which is a new kind of record for me… Anyway I decided to use this classic joke as the headline for an apology, and clarification, to the good folks attending my Windows 10 sessions.
A little while ago, a good friend (you know who you are :) ) asked for help on creating a new Windows 7 reference image. So here it is: A Step-by-step guide to create the perfect Windows 7 reference image using MDT 2013 Update 2.
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 VIAMONSTRA\MDT_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).