Since ConfigMgr 2012 R2 SP1, the boot images used has been more “sensitive” to network configurations, and in ConfigMgr Current Branch it got even worse. However with some simple tweaks you can configure the boot images to work in the crappiest of networks. Here is what you need to do.
Anyone using ConfigMgr for OS Deployment for more than four seconds knows that it’s the log files you turn to when things go wrong. However even in ConfigMgr Current Branch (currently v1511 as base version, with v1602 as most recent upgrade), since debug logging is enabled by default, a log file can easily grow to 5 – 6 MB with just the default task sequence. That wouldn’t be much problem if the log file didn’t truncate a 2 MB, and then created an archive (one archive only). 2 + 2 MB is still less than 5 – 6 MB.
For those of you using WSUS standalone for your updates, here is a collection of tips and tricks:
Most managing solutions (SCCM/ConfigMgr, Intune, or just scheduled PowerShell tasks :) ) makes use of an agent type method for control, to make sure the computer can do the work when it’s capable of doing so (like being on the network, powered on etc.). However, sometimes you have to get some Ad Hoc work done quickly, on as many machines as possible at that moment, and for that PowerShell and CIM sessions can be very useful.
During MMS 2016 I demonstrated how to use a web service to query AD groups in order to install ConfigMgr Packages and Applications dynamically during OS Deployment, here is the code and sample scripts.
As you probably know, ConfigMgr Current Branch has a built-in task sequence template for Windows 10 Inplace-Upgrades. This template is used for Windows 7/8/8.1 to Windows 10 upgrades as well as Windows 10 to Windows 10 upgrades (when a new build is available).
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: