Question regarding not pending restart relevance

Usage and Config Patch
1

(imported topic written by SystemAdmin)

I have a question regarding not pending restart relevance.

I understand the not pending restart relevance included in fixlets, but can someone explain what the not pending restart plus the sha1 number means?

For example: not pending restart “b95337473099eb18e3a9e9cb5abacc04bf76512b”

Why not just no pending restart? What does bigfix do differently when you include the sha1 number?

It only seems to be used with Windows 7 and Windows 2008. Why?

Thanks for clarifying this,

Scott

1 Like
2

(imported comment written by BenKus)

I am trying to remember all the details exactly… Here goes:

  • We had an issue with some newer MS patches that wouldn’t update any of their files or a reg key until after restart.
  • This caused an issue where you would apply the Fixlet, but it would stay relevant until you restarted the computer (which is annoying and might lead you to continually reapply the Fixlet).
  • We wanted to make the Fixlet go unrelevant immediately after you applied the Fixlet…
  • But… if we used “not pending restart”, then the Fixlet would go unrelevant if the computer needed a restart for any reason (very annoying!)
  • To try to solve all these issues, we invented a technique to have a “named pending restart”, which we usually use the sha1 of the patch file to avoid conflicts.
  • So the Fixlet will only go unrelevant pre-restart if the pending restart with the unique name was

Does that make sense? Are you sorry you asked? :slight_smile:

Ben

1 Like
3

(imported comment written by SystemAdmin)

Wow…maybe I am :slight_smile:

Thanks for the response Ben.

Scott

1 Like