MutedNewt

Our console is on version 24.2.0.13 (2402) Hub deployed to our laptop is on version (24.4.6.0) We can't try earlier version as the hub is automatically deployed from the console with the OOBE enrolment

Hi, Sorry didn't see your answer ! Yes, the HUB is showing installed. The only thing/difference we managed to investigate is that when Omnissa released the multiuser capability, then our workflow stops working without user session opened. We didn't manage to find anything on the logs, neither on console. So we think it relies on the new feature but we don't know if it's a feature or bug For now we are opening the staging user session for the workflow to work

We are doing offline domain join, and Entra comes with the Autopilot (Intunes) settings. The staging account doesn't automatically sign in, that never happened as soon as we set up the autopilot. But the workflow was working "outside" the user session. Thanks for you answer btw !

Hello, We register our workstations in Microsoft Autopilot, and the first time they start up we log in (on the “Welcome to Microsoft” window) with a staging account that has an automatically assigned workflow to prepare the workstation by applying the various settings and applications required. We've been preparing our Windows 10 workstations with a staging account and workflow for 2+ years now. Recently, the workflow wouldn't start unless the staging account session was open. Autopilot registration automatically enrols the workstation in Workspace One. Has the Intelligent Hub / Software deployment Agent been configured so that it no longer works without logging in? Or is this something that will be fixed in a future patch? Hoping you can help Sincerely