Help Center Home > Troubleshooting KB > Troubleshoot: Provision New Users on Device Login

Troubleshoot: Provision New Users on Device Login

This article covers fixes to common issues that occur with Self-Service Account Provisioning or with the Sign in with JumpCloud flow that this feature enables on devices.

I am receiving the error “User account already exists on this device” when trying to Sign in with JumpCloud.

This error appears because the username matches an existing local account and is preventing sign in.  Self-Service Account Provisioning is only available for new accounts on a device. 

The updated login window is preventing some users on macOS devices from signing in.

To restore the original login window, disable Self-Service Account Provisioning in the JumpCloud Admin Portal. See Disabling Self-Service Account Provisioning. 

On macOS devices, WiFi disconnects or asks for the pre-shared key even though I’ve applied the Wifi Configuration Policy in JumpCloud.

To resolve this issue, ensure your WiFi Configuration Policy is set to Join Network Automatically. See Create a Mac or iOS WiFi Configuration Policy to learn more.

PIN sign in is blocked on Windows devices.

You can check if PIN sign in is blocked on a Windows device by viewing the Windows Registry:

  1. Open the Windows Registry Editor (regedit) as a Local Administrator on the impacted device.
  2. Navigate to the following location: HKLM\Software\Policies\Microsoft\Windows\System\AllowDomainPINLogon.
  3. If AllowDomainPINLogon does not exist, or the DWORD value is "0" then PIN sign in is blocked. Modifying the DWORD value to "1" will allow PIN sign in.

Important:
  • Proceed with caution when using the Registry Editor.
  • A device restart is required to apply any changes to the registry.
Back to Top

Notebook IconLearn More

Provision New Users on Device Login

Still Have Questions?

If you cannot find an answer to your question in our FAQ, you can always contact us.

Submit a Case