question

GerardIgoe-4365 avatar image
0 Votes"
GerardIgoe-4365 asked saldana-msft edited

TaskSquence Deployment Scheule- changing expiration date

Hello
What happens when I change the "expire" date on a task sequence? Will need to clear the cache or the sccm client just sees I edit the expire date?

mem-cm-generaloffice-deployment
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

JasonSandys-9892 avatar image
0 Votes"
JasonSandys-9892 answered

Just a couple of supplemental comments here:

  • Task Sequences don't have expiration dates. Deployments (of task sequences and other objects) do.

  • The expiration of a deployment is completely unrelated to cached content on a device.



5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

GaryBlok avatar image
0 Votes"
GaryBlok answered

After you make the change, the next time clients with that deployment request a policy update, the machines will know when it expires.
No need to clear cache or do anything extra
in these cases, I'd recommend creating a test deployment to your test collection and just try what you're wanting to to try, so you can see exactly what will happen.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

SimonRenMSFT-3639 avatar image
0 Votes"
SimonRenMSFT-3639 answered GerardIgoe-4365 commented

Hi,

Thanks for posting in Microsoft MECM Q&A forum.

Based on my experience, we don't need to do anything else, the client will automatically get the changed task sequence a certain time later -- next client policy polling interval (60 minutes by defaul).

Task Sequences and everything in them are part of the machine policy delivered to targeted systems. If we make a change to a TS, then the system needs to update its machine policy but this will automatically happen by itself eventually.

By the way, if we make a change to the source files or any content referenced in the task sequence, those need to be redistributed manually. The distribute content option on right click of task sequence is just a simple way to distribute all referenced content within the TS -- it does not distribute the TS in any way.

However, if you would like to be SURE that you are executing the latest changes, you can add a version number to the name of the task sequence, that way, if you made changes to task sequence v1.0, increment the version number by one and you should see task sequence v1.1 after the next client policy polling interval. This ensures that your clients have the latest policies for this deployment (sometimes there's a delay depending on hierarchy).

Thanks for your time.

Best regards,
Simon


If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

ok looks like it worked! I was concerned since I predownloaded some updates and wondered if I need to clear the persistent cache first to get the new changes. IE date

0 Votes 0 ·
GerardIgoe-4365 avatar image
0 Votes"
GerardIgoe-4365 answered

ok Task sequence executed last night as planned with new expiration date. thank you!

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.