gwblok – GARYTOWN ConfigMgr Blog

Create Scheduled task to run action in future (Now+XX time)

December 14, 2018December 14, 2018 by gwblok

Ok, so I couldn’t think of a great title, but basically this will allow you to run any action in the future, 15 minutes, 30 minutes, 5 days, whatever you want. Why? Because you can. I’ve used this to have actions run post task sequence, either to assist in a rollback, or trigger additional tasks. ... Read moreCreate Scheduled task to run action in future (Now+XX time)

Task Sequence Variables

December 16, 2018December 13, 2018 by gwblok

Recently at MMS Desert Edition, I was talking with Jörgen Nilsson (ccmexec.com) and he said they had posted a PowerShell replacement for the MDT Gather step. I spent the next hour searching for it, just to find it hadn’t been posted.. Jörgen & Johan Schrewelius just thought they had posted it. They quickly posted it ... Read moreTask Sequence Variables

Scripts Node: Task Sequence Info & Remediation.

December 12, 2018September 4, 2018 by gwblok

So this script is just a part of one that I’ve developed for using at WF. The other one includes a lot more logic for remediation based on our WaaS Process Registry Keys that get created during the process. So I’ve cleaned it up, and stripped out a bunch to make it more generic to ... Read moreScripts Node: Task Sequence Info & Remediation.

Run PowerShell ISE as System to Test scripts… From Software Center

December 13, 2018September 4, 2018 by gwblok

Yet another post caused by my recent rebuilding of my lab from scratch after I totally hosed my last CM Server. This time I’m documenting (blogging) a few additional things. So you write a lot of scripts for ConfigMgr? Notice that they sometimes don’t perform quite as expected because they run as system instead of ... Read moreRun PowerShell ISE as System to Test scripts… From Software Center

Scripts Node, Add Local & Network Logging to Script

September 3, 2018September 2, 2018 by gwblok

This is basically two posts in one, add logging to your scripts in the script node, and Get Service Windows Info, check if you have any deployments being squashed by too restrictive Services Windows, and remove the service windows if you want to. Why add logging… several reasons, to know what the script did, to have a “paper trail”, and helps with troubleshooting. I’ve added logging to my scripts for accountability as well. I have it log to a network share because I’m not local admin on the boxes I’m running the scripts on, so having a central share to collect the scripts is very important to me when I’m troubleshooting issues.

The reason I wrote this script was because we've run into machines that would never run the Upgrade because they would return with a status message "deployment will never run, too restrictive of service window". We do not check the box on our deployments to run outside of a Service Window, as we want to respect what the Business Unit have said are their approved times to service machines. However there are times when the windows are just too small for the time we've specified in our TS, or someone created a local service window manually, using a tool like Client Center, to accomplish a one-off task and never cleaned it up. So I created a script that would read the execmgr.log file, search for a restrictive window issue, then delete them (based on parameters). You can search for Local Service Windows or Server Side (Collection) Service Window and delete those, or choose Delete all service windows. Common Sense Warning: Use with Caution, and Test please. This script is deleting Service Windows which restrict installs / reboots from happening all willy nilly. If you start removing those restrictions… well.. you get it.