Windows Out of Box Experience (OOBE)/Autopilot
As of version 2312.1.2 the UEM Agent is able to detect the Windows OOBE which is used during Autopilot or after being cloned and prepared with sysprep.
While the Windows system is in the "OOBE Mode" where the machine gets prepared for the first logon, the UEM Agent will just download assigned software, but will not install it. So the software installations by the UEM Agent will not conflict with Windows Autopilot.
In addition the UEM Agent will switch to its so called "OS Mode" right after the Windows "OOBE Mode" finishes to start and continue software installation until the assignments are fulfilled - in the same way the UEM Agent does when using a "classic" OS provisioning. A possible logged on user will see a small installation window, so he is informed that installations take place.
The OOBE detection must be activated by using the Parameter OOBE="true" when installing the UEM Agent via MSI.
Troubleshooting
No "OOBE Mode" log messages are visible in EMC.
If the UEM Agent detects changes to the "OOBE Mode" it sends log messages to the backend. Usually the messages are overwritten by the latest state. "OOBE Mode" and "OS Mode" are in the same category of "Agent Installation Status" and will update each other.
In order to see the timing behaviour and to ensure, that OOBE was detected, use the Rollout Coordination or switch off "Overwrite logs" in DB Util.
In addition the UEM Agent logs mode changes in its internal/local log file to be found under %ProgramData%\Matrix42\Logs\UAF.