Last updated on: March 10th, 2021
I can’t log in with a local vScope account
Make sure that your login credentials are correct. If you’ve forgotten your password you can click “Forgot password” on the login screen.
If the email is incorrect you’ll get an error message in the down bottom corner. Please contact your vScope administrator if you can’t remember your Email address.
I can’t log in with an LDAP/AD account
Check that your login credentials are correct, these are the same as your normal Active Directory account. If you still can’t log in it may the cause of:
- Your LDAP/AD credentials have changed
- The administrator in vScope has changed the group mapping settings for the LDAP/AD integration and your AD group no longer have access to vScope
- The LDAP/AD integration is lost
Contact your vScope administrator for more information.
I’m locked out from vScope
The main reasons you can’t access vScope is:
- The Active Directory connection has been lost.
- Changes have been made to the AD group with access to vScope.
The first thing to look for is a local vScope administrator account. One is always created when vScope is installed.
The Active Directory connection has been lost
One way to access vScope if the AD connection has been lost is to log in to vScope with a local admin account. One is always created when vScope is installed and more might’ve been created by vScope administrators.
Look for any recent changes to the Active Directory or in the firewall rules on the vScope server. Has the domain controller been moved or changed hostname? Is the service account used for the AD integration been disabled for some reason?
Changes have been made to the AD groups
Deleted AD groups happen. If your permission group to vScope has been deleted you can simply restore it. Also, ensure that your user account is still in the group.
No one can access vScope and we can’t find the local administrator
Contact the vScope support at firstname.lastname@example.org.