This Script will trigger the Baseline (Based on the Baseline Name input) then report compliance and if non-compliant, what rule was non-compliant. In this example, I'm triggering the baseline "WaaS Pre-Assessment". The script does several things.. Triggers Machine Policy & Waits 2 Minutes Gets the Baseline Information from WMI If the Baseline is in WMI, ... Read moreRun Scripts: Trigger Baseline Evaluation
Goal: Trigger Task Sequence remotely via Run Script. Allows you to trigger on one computer or several. *The Policy for the Task Sequence most already be on this machine. Type the Package ID for the Task Sequence you want to trigger on the machines: You can Hover over for more info: The Return information is ... Read moreRun Scripts: Trigger Task Sequence
So you're using at Task Sequence to deploy something other than an Operating System, but it's really important, and you want the popups for "High Risk" like you do with in place upgrades. NOTE: Setting "High Risk" on your TS Properties will move the Deployment in the software center from the Applications Tab, to the ... Read moreTask Sequence Deployment - Popups
I blogged awhile back about how we were pre-caching drivers... and it worked... until it didn't. Bug: after updating driver source and bumping content, we had issues. So we re-worked it and modified the idea to use, as Mike calls it, "The Magic Policy". This is ALL Mike's idea, no credit of my own, he's ... Read moreDriver Pack Mapping and Pre-Cache v2
As mentioned in Previous Post, we've had upgrades fail due to non-standard path variables. I've created a CI that captures the path and looks for specific things then reports Compliant, or reports the issue, which we track with reports. We use this in our PreAssessment / PreFlight Rules, so if this is Non-Compliant, it prevents ... Read moreCI to Monitor Path Variable