- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Stop Intelligent Hub from asking to sign in
We have some drop-ship provisioned machines that are currently assigned the staging user. They are intended for public use.
However, every time someone logs in, the Intelligent Hub pops up, and asks them to sign in. How can this be stopped? Most users can't sign in anyway, so it leads to a dead end.
Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@eg2428 the answer depends on if the machines are joined or not joined to a domain and how the staging is configured and also how the devices are configured for public use (assuming shared use where users are not logging in).
If you just want to present some apps, then I would enrol the devices to a user not staging user, that is dedicated for the task. We sometimes refer to this user as a service account. The service account user would have the apps and profiles required to support its use and I would also use the kiosk profile to force control over the desktop/shell.
Have a look here for examples of kiosk profiles - https://github.com/helmlingp/WS1UEM_CustomKiosk
Phil
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Phil,
Thanks for writing. These machines are joined to the domain, and were set up with dropship provisioning from the factory, assigned to a staging user. We want users to have the full desktop experience, so unfortunately kiosk mode can't be used. There is also a local computer account that can be used in case a user doesn't have an AD account.
For local and domain accounts, is there any way to avoid the popup, without using kiosk mode? When you say "how staging is configured" what settings can we look at?
Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ok so if they are domain joined and have line of sight to a DC when logging in, then Hub should not popup as Hub matches the user in AD to the logged on user. There are potential complications on the staging user and how auth is setup, such as whether you have WS1 Access in the auth flow.
On staging user, find the user in Accounts > Users > Advanced and look at the staging config (screen capture of one of mine attached).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Phil,
Thank you, I can confirm our staging account settings look just like yours.
For our local Windows account, if we create a basic account with the same name in Workspace ONE, would it then be able to link the device to our basic Workspace ONE account? Or do local Windows accounts _require_ being enrolled under a domain user account?
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If the devices are domain-joined and have a clear connection to a domain controller during login the hub should not trigger a popup. This is because the Hub matches the user in Active Directory to the logged in user provided there are no issues with the staging user or authentication setup including the presence of WS1 Access in the authentication flow. To inspect the staging user locate the user in the Accounts section then navigate to Users and access the Advanced settings. You can refer to the attached screen capture for an example of the staging configuration. read blog ff advance server download latest ob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
only Active Directory users are silent enrolled (no HUB popup). Like Emad said, we match the local logged on user account to a user in the directory that is configured in UEM, if no match then we popup and ask for creds.