eriheart.blogg.se - Winmerge vs beyond compare

You can also see in this example that the CCMCache size was less than the desired 25GB, so it set it to 25GB for you. In the Console, 1607 Machine, it has run the PreCache TS, but not the 1803 Upgrade (as showing by the Execution History).

This will log everything locally on the machine and on a server share ( See previous post for more details)įeel free to modify to fit your needs.

Will try to Trigger again with updated policy.

Checks if same Task Sequences are available.

If the Services were Reset, it rechecks.

Resets the CM Client & TS Services to clear out any running TS.

If Machine has not already upgrade to the build you specify in Parameter (ex 1803).

Report Provisioning Mode Status and Remediate.

Report Status & Startup Type of CCMExec & SMSTSMGR.

Delete Execution History of those PacakageIDs.List Execution History of those PackageID.Based on PackageID’s you’d put in parameters.Find Task Sequences Available to Machine.Disk Size & Free Space & Run Cleanup if less than 20GB Free.

Report CMCache Size & Fix if less than 25GB.TSIPUPackageID = Package ID of your IPU TS.TSPCPackageID = Package ID of the PreCache TS.This is another potential fix to help you retry running a TS. DeleteExecutionHistory = It will find any Execution History for the PackageIDs you’ve specified, then delete them.This will not run even if set to true if already upgraded ($CurrentBuild = $BuildNumber) Default = False ForceTriggerTS = Will kick off the PreCache or IPU TS, if both are available, IPU wins and will kick off.ScriptLogging = Do you want it to log localling and on the server? Default = True.ForceTSReset = This will force resetting of the CCMExec & SMSTSMGR services & process, effectively killing off a running (hung) TS.Reports the Parameters you’ve specified.The Script itself is like 75% functions, then 25% running actions. So I’ve cleaned it up, and stripped out a bunch to make it more generic to work in any environment. The other one includes a lot more logic for remediation based on our WaaS Process Registry Keys that get created during the process. So this script is just a part of one that I’ve developed for using at WF.