Task Sequence Hacks

I seem to have a fair amount of ConfigMgr Task Sequence “Hacks” so far and I wanted add some structure to my site. This is the landing page. 

Gather No More – Using Dynamic Task Sequence Variables in ConfigMgr

Update 09/14/2020 – You can download the Gather Light Task Sequence from the Community Hub now! https://communityhub.microsoft.com/item/7812 Update 02/21/2020 – I added a new section with a Gather Task Sequence. Check out the DIY Gather in the Task Sequence section below. It even has a GIF (unlike Software Center!) If you’ve used the Microsoft Deployment…

Continue Reading Gather No More – Using Dynamic Task Sequence Variables in ConfigMgr

Using SCCM Task Sequence Variables as Scripts

The more I dig in to SCCM/ConfigMgr, the more cool things I find. Every time I read a new post blog about things people have done with their Task Sequences, I get inspired to try more things. One of those things is setting Task Sequence variable values from the output of a script. At this…

Continue Reading Using SCCM Task Sequence Variables as Scripts

Dynamically Updating Unattend.XML during an OSD Task Sequence using MDT Variables and ZTI Scripts.

While trying to set the KeyboardLocale in my ConfigMgr/SCCM Task Sequence, I found that my settings weren’t getting updated during the Task Sequence. I used to think that custom Unattend.XML that you include in your Task Sequence would be used as-is. I was wrong. I did a bit of digging and here’s what I discovered.…

Continue Reading Dynamically Updating Unattend.XML during an OSD Task Sequence using MDT Variables and ZTI Scripts.

Triggering ConfigMgr Client Actions from a Task Sequence

This week, we were working on testing Windows 7 to Windows 10 In-Place Upgrades and ran into an issue where our clients weren’t updating their Operating System version in the ConfigMgr console. After some helpful responses on Twitter, I was able to add a client action trigger step to the end of my Task Sequence.…

Continue Reading Triggering ConfigMgr Client Actions from a Task Sequence


Fatal error: Uncaught GuzzleHttp\Exception\ClientException: Client error: `POST https://dc.services.visualstudio.com/v2/track` resulted in a `400 Invalid instrumentation key` response: {"itemsReceived":1,"itemsAccepted":0,"errors":[{"index":0,"statusCode":400,"message":"Invalid instrumentation key"}]} in /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/application-insights/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php:113 Stack trace: #0 /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/application-insights/vendor/guzzlehttp/guzzle/src/Middleware.php(66): GuzzleHttp\Exception\RequestException::create(Object(GuzzleHttp\Psr7\Request), Object(GuzzleHttp\Psr7\Response)) #1 /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/application-insights/vendor/guzzlehttp/promises/src/Promise.php(203): GuzzleHttp\Middleware::GuzzleHttp\{closure}(Object(GuzzleHttp\Psr7\Response)) #2 /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/application-insights/vendor/guzzlehttp/promises/src/Promise.php(156): Guzzle in /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/application-insights/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php on line 113