Lately one of my Windows 10 machines started to behave quite strange, after about a day of use, browsing Internet was no longer possible. I could still ping resources, but not use any browser or other application requiring Internet access. A reboot fixed the problem, and then after about a day, sometimes less, the same thing happened.
Follow-up post to an earlier post on installing PowerShell 4.0 for Windows 7 using MDT, this time for PowerShell 5.0.
Yesterday I got a question on Twitter from Kyle Wilcox about installing PowerShell 4.0 using MDT for a Windows 7 build. So here it is: A geeks guide to install PowerShell 4.0 for Windows 7 using MDT 2013 Update 2.
Earlier this afternoon I was watching the Deploying Windows 10: Automating Deployment by Using System Center Configuration Manager live event from Microsoft Virtual Academy (MVA). The three sessions were presented by Aaron Czechowski and Wally Mead, both well known profiles within the ConfigMgr space. Here follows a summary of the live event:
In two different production environments, running ConfigMgr Current Branch (1511), I have seen the “Failed to find a valid network adapter” error happening when starting a bare metal deployment. In both environments the machines did get an IP address, and pretty quickly too, but apparently not quickly enough for ConfigMgr.
What to do on a Sunday morning? Well copying a 10 GB MDT media deployment share (OEM Scenario) to 32 USB sticks for a start :)
Yay! My Windows 10 OS Deployment sessions from NIC 2015 are now available on YouTube.
If you have been deploying Windows for longer than 4 seconds, you know that the MDT log files are written in a format designed for the CMTrace utility. Here are two quick guides on how to add it to the MDT boot images (the supported way, and the cool/fun way :) ).
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.