I have iOS devices which are in DEP. I want this to enroll the devices in Workspace with a staging user. Then with the Hub applications (pushed with VPP) i want to register the device on a user.
Below a video showing this flow and the VMware documentation.
In the past we also had this working in this way. However, this is not working at the moment. Whatever we have tried, once we open the 'Hub' App on the device there is no possibility to log in and / or register the device for a user.
Single User – Stages device for a single, known user.
Only staging users are available as Default Enrollment User options. Once the end users open the AirWatch Agent, they must enter their credentials to enroll the staged device. Then the device details update in the AirWatch Console and the device is associated with that end user. ^ This does not work (anymore).
We use the 'Default Staging User'. If we create a new user with the staging options: Enable Device Staging: Enebled, Single User Devices: Enabled and Single User Devices: Advanced - Enroll on behalf of another user. We can not select this user in the DEP configuration. Maybe there is also something what is going wrong here.
Are there more who experience problems with this? Or does it just works?
We are running on-prem 18.11
Hi Ben ,
I have no issues with DEP and staging, neither with Advanced staging on behalf of a specific user.
What do you mean with ' We can not select this user in the DEP configuration' ?
Following the steps in the youtube video, where exactly are you stuck?
ok, i think i figured it out. use 2 dep profiles and assign one with a staging (no authentication) to the 2nd one, keeping the first with regular authentication. make sure the user selected in the 2nd one has multi-user set in the profile under staging in Airwatch.
seems to work so far.
I'm a little confused. My setup requires a single DEP profile with a staging account with Single User Staging enabled. No authentication is required during staging, and user simply enters his/her AD credential to log into the Hub app which then associates the device accordingly in AirWatch console. This has worked for me for years.
I implemented similar setup for multi-user devices which provide even better ROI since anyone with an AD account can log into the Hub app on the device and use it. Once he/she finishes, they simply log out and another user can then log in the same way.
so it sounds like you have set 'no authentication' at the dep profile level. I have set this so i can do custom enrollment with terms and conditions. so now i have 2 dep profiles set (1 with authentication prior to displaying home screen, and 1 set to no authentication with a staging user with properties multi-user staging) . this allows default 95% of our fleet to be enrolled when delivered to end user single use, and the other ones can be assigned the second dep profile prior to delivery as a multi user device. seems to work so far, only a bit of delay auto apps on log out / logon . and once the devices are wiped, they get back to the multi user.