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.
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.
If Sign in with JumpCloud doesn't appear on the Windows login window, check the following:
- Ensure Self-Service Account Provisioning is enabled for Windows devices, either globally in the Admin Portal under Device Settings or via a policy.
- See Enable Self-Service Account Provisioning.
- See Create a Windows Self-Service Account Provisioning Policy to learn how to create a policy for specific Windows devices or device groups.
- Ensure the required Microsoft Visual C++ (x64) dependencies are properly installed on the device in C:\Program Files and not Program Files(x86). To verify:
- In Windows Settings > Apps > Installed Apps, ensure Microsoft Visual C++ Redistributable (x64) is installed.
- Verify the presence of the following directions:
- C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App
- C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App
To resolve missing dependencies, run C:\Program Files\JumpCloud\dependencies\DependencyLoader.exe to ensure the device meets all requirements.
You can check if PIN sign in is blocked on a Windows device by viewing the Windows Registry:
- Open the Windows Registry Editor (regedit) as a Local Administrator on the impacted device.
- Navigate to the following location: HKLM\Software\Policies\Microsoft\Windows\System\AllowDomainPINLogon.
- 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.
- Proceed with caution when using the Registry Editor.
- A device restart is required to apply any changes to the registry.