Restart mid-baseline for 24H2

Content Authoring
1

I am currently deploying 24H2 to our computers but am running into a unique issue.

We use 802.1x authentication and 24H2 has this amazing feature where internet stops working if you use 802.1x authentication. This is the issue:
https://www.reddit.com/r/sysadmin/comments/1fy95vz/win11_updates_break_8021x_until_gpupdate_happens/

To resolve the issue, I am deploying 24H2 as a baseline where the computer restarts during the 24H2 installation task using the restart command and there are post-restart steps that resolve the 802.1x issue. The 24H2 task is considered successful when it runs to completion however many computers are reporting Failed even though I have verified via logs that everything finished successfully. The only idea I have is that if you induce a restart using the restart command and the user closes the window then the action is considered Failed.

I am open to all ideas and can share anything from my baseline if needed.

2

You should look at the success criteria for the fixlet.
It can be:

  • fixlet no more relevant
  • all action script statement successfully executed
3

Yes if the system reboots in the middle of a running action, the action is considered Failed.
You would need to use the builtin action script command restart to perform a restart that BigFix is expecting, or a.post-action restart,.to avoid that issue.

4

I am using the restart command as the final line of my 24H2 install action. I think I’m going to take this approach instead:

  • Remove the “restart” command from the install action, instead I’ll just use “action requires restart”.
  • Use a separate open action that handles my restarts. This seems to be the best practice, we have been meaning to switch over to this anyways.
  • All post-install steps will have “not pending restart” as a relevance so they don’t run prematurely.

Early testing is promising.

2 Likes
5

I have the following as the last line of my Windows 11 24H2 install task:

action requires restart “ba2943a1f12ac2d61c423e1bccac5f945f645d3e”

The following task Wait for Restart has the following:
Relevance:

pending restart

Action Script:

pause while {pending restart}

Success Criteria:

This component will be considered fixed when the applicability relevance evaluates to false.

At this point it is waiting for my Restart Needed action to catch it. Is this really the best option for restarting mid baseline?

6

You could just have a task with the action script

restart 60

Which will trigger an OS restart with a maximum waiting time of 60 seconds if someone is logged in.