I would like to propose a future enhancement for the OpenIntune Baseline script Trigger-PostOOBEUpdates.ps1.
At the moment, the script triggers the following actions after Autopilot deployment:
Microsoft Defender signature update
Store app update scan
Windows Update scan
It would be very useful if the script could also trigger an Intune device sync as part of the post-OOBE updates.
This would help ensure that devices check in with Intune again immediately after the update actions, so newly assigned policies, applications, and configuration changes can be picked up without additional delay.
I also wanted to ask whether there was a specific reason why an Intune sync was not included in the current version of the script. Was this omitted on purpose, for example due to timing, dependency, or reliability concerns?
From my perspective, adding an Intune sync step would make the post-OOBE process more complete and improve the overall provisioning experience.
I would like to propose a future enhancement for the OpenIntune Baseline script Trigger-PostOOBEUpdates.ps1.
At the moment, the script triggers the following actions after Autopilot deployment:
Microsoft Defender signature update
Store app update scan
Windows Update scan
It would be very useful if the script could also trigger an Intune device sync as part of the post-OOBE updates.
This would help ensure that devices check in with Intune again immediately after the update actions, so newly assigned policies, applications, and configuration changes can be picked up without additional delay.
I also wanted to ask whether there was a specific reason why an Intune sync was not included in the current version of the script. Was this omitted on purpose, for example due to timing, dependency, or reliability concerns?
From my perspective, adding an Intune sync step would make the post-OOBE process more complete and improve the overall provisioning experience.