Troubleshooting

How to reduce long Discovery times

Long discovery times is most likely caused by a faulty Discovery Manager setup. Before we start to optimize the discovery time, we first need to understand how a discovery is performed. How the discovery work Since vScope runs without the use of agents, the discovery starts off by pinging all IP addresses that are defined […]

Wrong/missing patch date for machines in vScope

You might sometimes experience that Windows Patch Date tag does not show the same value as shown on the server. This is most likely due to an error in WMI on the target computer. In general, start off by confirming that the machine has been inventoried by the latest discoveries. Confirm this by adding the […]

Common email server errors

By integrating an email server to vScope you can notify users about eg. changes in reports, alerts or whenever a report is shared with the user. If the integration fails, administrators in vScope will receive an email containing a detailed issue description (this email is sent by using InfraSight Labs’ default email server). Here are […]

How to confirm WMI access through DCOM and WinRM

Ways to access WMI vScope accesses WMI on a target machine in two ways. DCOM (the default way) Executes queries remotely High Round-trip time (RTT) between vScope and target machine times affects scan time negatively WinRM (recommended) Executes queries locally on target machine High Round-trip time (RTT) between vScope and target machine does not affects […]

SCCM information is missing in vScope

Using a domain administrator you should have sufficient rights to inventory the SCCM server through WMI. If you are using a non-admin and are not getting any SCCM Site data in vScope you might have a permission problem. Make sure the following values are enabled under ‘Hardware inventory’ in the SCCM: Operating System (Win32_OperatingSystem) Serial Number […]

vScope’s communication with InfraSight Labs

vScope requires Internet connectivity to communicate with InfraSight Labs’ support systems License & Billing account: https://account.vscope.net/… (HTTPS, TCP 443) vScope software updates: https://dist.vscope.net  (Dynamic IP, CDN Amazon CloudFront) Service functions like Online support/Secure upload and license heartbeats: https://status.vscope.net/… (HTTPS, TCP 443) If you are using vScope’s default mail server for email settings you will also need to […]

Error Message ‘User Already Exists in Active Directory’

When creating a new local vScope user you might get error message “User Already Exists in Active Directory”. This means that vScope have found a user with the same Email address in the integrated Active Directory/LDAP and can’t create a new one. To add the person you can either: Use a different email address or… […]

VMware Uptime/Last Boot Is Missing

vScope uses the property bootTime to retrieve runtime information provided by the API. If you are missing values for VM Uptime and VM Last Boot vScope cannot properly fetch bootTime from the API. Ensure permission settings and that VMware API is configured properly.

Can’t Log in to vScope

I can’t log in with a local vScope account Make sure that your login credentials are correct. If you’ve forgot your password you can click “Forgot your password” on the log in screen. If the Email is incorrect you’ll get an error message in the down bottom corner. Please contact your vScope administrator if you […]

Lost LDAP/AD Integration

Changes to the host or base DN in your LDAP/AD can cause the integration with vScope to be lost. To set it up again you’ll need to log in with the local vScope adminstrator account and redo the LDAP/AD integrations set up. Ask your vScope administrator for help. Please contact the vScope Support if you […]