It has certainly been a good twitter-week with many interesting announcements and discussions (if you’re not on twitter, get on twitter). One discussion that stood out was a question about running WinSAT formal being needed for Windows 10 Deployments.
For what feels like the tenth time, Microsoft is changing their terminology/strategy around Windows 10 updates. Below is a recent thread covering the topic (thanks to Ami Casto (@AdaptivaAmi) and SystemCenterDudes (@scdudes) for making me aware of the changes):
Johan has done a great job creating the Hydration kit but I had the need to do some customizations. Johan did a write-up on which files needed to be changed (here) but that’s a lot a manual work which I really recent 😉
No, really, don't add the Intune client software to your Windows 7 reference image, install at deployment time instead via the task sequence.
Earlier today I got a question on how to remove the default Windows Store and Mail icons from the taskbar in Windows 10 v1703.
Yet another late night working with a set of VMs, exported out of one standalone lab environment into another.
When creating reference images for Windows 10 or Windows 11, Sysprep is very likely to fail if the machine has Internet access, and have enough time to start updating it's built-in applications, or install new ones as part of the consumer experience feature. This post is about preventing that from happening, and is a companion to my guides on building Windows 10 and Windows 11 reference images.
When build lab and proof-of-concept solutions in a virtual environment it's very useful to also have a virtual router to enable multiple networks to connect, and to simulate a larger environments. For example to do lab setups like below:
Here is a step-by-step quick guide on building the perfect Windows 10 v1703 reference image using MDT 8443.
To have a ConfigMgr environment coexist with another PXE environment, like WDS or just a 3rd Party PXE Server, you need to make some changes to the ConfigMgr boot image.
Written Matthew Teegarden (@TheEmptyGarden).
A little while back I had to do a presentation about what options that are available from Microsoft to manage Windows PCs, and to summarize, there are only two (sort of): ConfigMgr or Intune (standalone), or combining ConfigMgr and Intune (the hybrid model). Anyway, when preparing the presentation I spent some time on testing the standalone Microsoft Intune solution, and quickly run into a question: Should you, or should you not, use the Intune client software ?
In Windows 10 you have the option of creating provisioning packages to apply settings/configurations to a machine. For example upgrading a machine running Windows 10 Professional to Windows 10 Enterprise. Now, to apply a provisioning package, you can either do it automatically in WinPE via DISM.exe, or later in the running Windows operating system by double-clicking the provisioning package and walk through a quick wizard.
Windows 10 updates, both the scheduled updates from Microsoft as well as updates of Windows 10 apps, can put a significant load on your network. At least if you compare it with what a Windows 7 client does. Add that to all you normal deployments, images, applications etc. and you’ll find yourself running down the hallway, chased by folks from the network group 🙂
A quick update on SQL Server 2016 changes that are helpful for ConfigMgr Current Branch installations.
Back in December, the ViaMonstra hydration kit was updated to support Server (and SQL) 2016. You can follow the post here to set it up. We get a lot of questions offline about customizing the kit, so here is a summary of customization.
Default behavior for failed deployments in ConfigMgr is for the error box to stick around for 15 minutes before rebooting. That’s plenty of time if you have nothing better to do than watch progress bars and wait for failures. But what if you have work to do and you need the error to stick around a bit longer?
In ConfigMgr Current Branch v1610 Microsoft added in a new feature called Peer Cache. It had previously had a few guest appearances in the Technical Preview branch, but now finally made it to the shinier branch, e.g. Current Branch. Anyway, this feature is designed to help reduce the network impact of delivering content to clients in distributed environments, and works with the package types that ConfigMgr supports (updates, legacy packages, applications, images etc.).
A very shiny week turned into even shinier with the release of Windows ADK (10) Insider Preview v15021.