- The JumpCloud agent will appear to start and then stop almost immediately
- The system may or may not show up in the JumpCloud Console
- The JumpCloud agent log will show something similar to the following:
2016/07/14 10:19:49  [INFO] User management not starting - host is part of a Windows domain 2016/07/14 10:19:49  [PANIC] : caller 'user_management.go:133' attempted to stop when we're not stoppable (stateVal=0) 2016/07/14 10:19:49  [ERROR] (main.serviceManagerStart) ERROR OCCURRED: [PANIC] : caller 'user_management.go:133' attempted to stop when we're not stoppable (stateVal=0) goroutine 34 [running]:
This is by design. Currently the JumpCloud agent is not supported when a system is joined to a domain. When the system is joined to the domain, this indicates the desired user management method is Active Directory and the agent is stopped to avoid conflicts.
To manage the system using the JumpCloud agent, unjoin the system from the domain, verify the agent starts and the system populates in the Systems records in the admin console.