Keeping Task Sequences updated for OSD

[mconwell]

Is there a way to have my OSD task sequence update when a new version of an app is created by PmPC?

An example might help illustrate...

• OSD task sequence contains multiple apps we consider "core" apps.  For example, Zoom workplace x64
• PmPC recognizes a new version of a managed app and auto-publishes it as a ConfigMgr application
• At this point, the OSD task sequence is out of date unless it is manually updated to remove the old version of Zoom and include the new version of Zoom.

I'm looking to understand if step 3 can be automated and if so, how is this done. Probably more important how is this tested prior to releasing to production?  I'd hate to update a task sequence only to find out that one of the new apps turn out to be a "dud". 

What I would likely do manually (which is probably overkill):

• Make a copy of the task sequence
• Manually update the task sequence copy to remove the old app and include the new app
• Build a new VM using the copy of the task sequence - this tests a new deployment of the app. Test the app.
• Build a new VM using the older task sequence and then deploying the new version of the app using a patch (SUP/WSUS). Test the app. - this tests upgrading existing devices

Thoughts on if this can be done or how it can be done in a semi-automated way?

Thanks in advance.

[JustAnotherUser]

I don't think you can have manual testing and automated in-place upgrades for your OSD using built in functionality, but I'm not a super expert. I am a stickler for backing up task sequences before making changes, though.

 From here, Option 1:
https://patchmypc.com/base-install-update-options-explained

Task Sequences:
If you are referencing these Patch My PC managed applications within a task sequence, then you will always be deploying the latest available version of these applications which Patch My PC provides.


You can do most of it all w/ powershell though...probably. You can use Copy-CMTaskSequence but then you're going to need to assign deployments and such. You can use get-CMApplication and pull the date created paramater and a name wildcard to assign new apps but that's not going to be very fun to put together.

I would probably allow update in place but keep 1 retained copy, then set a scheduled task to copy your task sequence on some schedule so you always have a backup, and just roll back if something happens.

Alternatively you could use task sequence variables where your test OSD pulls all "AppTestVersion" or whatever variable applications, and set new versions to use that variable, then your Test OSD is always bleeding edge for test and you just delete the variable once your test is done, which you can also do from powershell.

Do you normally do a full test image for *every* app update for all of your apps? I test them after they're made then assign to the OSD once I know they're solid, personally---but I appreciate your desire for automation.

I guess alternatively you could do all of that with PowerAutomate as well, but permissions might get fun.