Workflow won't launch anymore without session opened

[MutedNewt]

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

[Michael Niehaus]

Is this with Azure AD (Entra ID) Join?  Doesn't the staging account automatically sign into Windows at the end of the Autopilot process?  It should unless there was a reboot during the process.  

I've only seen the workflow run after the user (automatically) signs in, so I can't comment on whether something has changed there.

[MutedNewt]

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 !

[Sascha Warno]

Hub is showing as installed in the UEM console or is the device in the pending install of hub state?

[MutedNewt]

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

[Sascha Warno]

What environment are you on? And what version of Hub are you using? Multi User support came with Hub version 24.04., you can try with earlier versions. Multi User in console is only active after an upgrade to 24.06 and activation of Modern SaaS.

 

[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

[Sascha Warno]

Reached out internally, seems this is something fixed with an upcoming version of Hub.

[MutedNewt]

Did you have any infos on which version ? Or an estimated delivery date ?

But anyway, thank you for your answer !