Arm version of Hub stored on console(s) for auto deployment during enrollment?

[ZombieKiller]

During a windows autopilot OOBE enrollment, the Hub should auto deploy from the console. That has always worked fine for an x86/x64 bit version of windows. Now with the Arm version of windows, I'm finding no matter what console I try this on, the Hub won't deploy and it just stays in a "pending hub" state and the enrollment doesn't finish. If I grab the arm version from getws1.com or getwsone.com and manually install it, everything finishes up just fine. Any idea why?

[Michael Troelstrup]

For a work-around, you can upload both versions of the hub in your environment and then make specific smart groups to target the ARM hub version for the ARM devices. 

[ZombieKiller]

Except that until the Hub makes it onto the device and is installed, nothing is deployed from the console. So, even if I manually upload the Hub for deployment, since the Hub isn't deployed during enrollment, it won't go out. It's a chicken and egg problem.

[Michael Troelstrup]

Hey, 

I got some more info on this. Do your settings match the screenshot ? The device should be sampled then the correct installer should be pushed down. 

[ZombieKiller]

Yep, it does match. Like I said, enrollments with an x86/x64 chip, the Hub auto deploys out just fine. It's when the device has an ARM chip that it hangs. There was a known issue on this: https://kb.omnissa.com/s/article/93527 that was supposedly fixed on the 2308 console.

And at least IMO it has come back.

Edited September 27 by Zombie

[Michael Troelstrup]

Hey, 

I have a ticket open for this and will keep you updated as well.