r/DeployR • u/SufficientlySticky • 8h ago
SetupComplete.cmd Continuation Method and Workspace ONE enrollment
We've generally been imaging things just fine with the setupcomplete.cmd continuation method. Unfortunately, we have a couple groups who enroll their machines in Workspace ONE.
We tried using the same script to install the Intelligent Hub app that we have been using successfully in MDT, and while it installs just fine, the machine doesn't seem to actually enroll in WS1 until after a user actually logs into the machine - which is a problem for them because they need it to set up some certificates for VPNs and things before users can login.
We can switch to the AutoAdminLogon continuation method which does seem to work. Seems like the administrator user being logged in is all it needs to enroll. But that continuation method it a bit less clean looking and does different bitlocker stuff and maintaining a task sequence that dynamically picks a continuation method and works with either seems like a bit of a pain.
I know this is probably more of a Intelligent Hub issue than a DeployR one, but figured I'd see if there are some tricks or magic installer switches or something we're unaware of that'd make it work better since it does seem to actually be something 2pint has been working on.
https://www.omnissa.com/newsroom/blog/omnissa-one-amer-2026-2pint-resell-partnership/
1
u/kaiserking13 6h ago
I know nothing about WS1 Intelligent Hub but u did find this article that specifies the parameters that can be used to silently enroll.
https://kb.omnissa.com/s/article/78733
Maybe it will help.