Today’s onboarding scene: Users are already set up in our IdP, laptops are ready, and when the users are having network issues, they couldn’t login into the device. And we ended up manually creating accounts on a bunch of devices just to get people signed in. It works, but it feels like we’re doing the same job twice.
What are you all doing to avoid this “manual local account phase” during rollout?
22 Views
This happens a lot when teams go cloud-first, but Windows still needs a proper local profile to exist on the device. Manual account creation doesn’t scale, and it’s also messy because everyone ends up using different naming styles. One month later you’ll find accounts like tempuser, tempuser2, finaltempuser_real, and you’ll wonder who created them and why.
Exactly. And the worst part is it’s not just an onboarding annoyance.
Manual local accounts become a long-term headache because:
So yeah, it’s better to get ahead of it early.
This is where IdP to local account provisioning helps. Instead of creating local accounts manually, the local account can be provisioned automatically based on the IdP identity and applied consistently across devices. So, when the device network goes offline, the user might be able to sign in with this kind of feature. Hexnode has a help doc that walks through the full setup here IdP to local account provisioning.
Don't have an account? Sign up
