Category Archives : Help pages RSS feed for this section

Connecting to Active Directory (LDAP)

By connecting vScope to Microsoft Active Directory, you can collect Users, Groups, Group Policies, Organizational Units, and Devices, to enrich your inventory even further. vScope uses the LDAP protoc...

Connecting to Microsoft SQL

Adding Microsoft SQL to vScope unlocks information from Microsoft SQL servers in your IT environment. The data source includes asset types such as Database Systems, Databases, User Accounts, and Jobs....

Create recovery user account

recovery.username= USERNAME recovery.password= PASSWORD recovery.licenseid= Contact Support for License Instance ID The license instance id requirement is a safety measure to make sure that you know e...

Connecting to Nutanix Prism Central

Integrate vScope with Nutanix Prism Central to collect information about VMs, clusters, storage, and more. The information is automatically cross-referenced with other data sources such as SCCM, Windo...

How vScope runs WMI scripts

vScope collects information from Windows operating systems using various WMI scripts, utilizing VBscript. The scripts can be run from the vScope server using plain WMI, or locally on the target machin...

Clear disk space for vScope

Due to vScope keeping track of any historical changes in your IT environment, the disk usage of the vScope installation will increase the longer you run vScope. By default, vScope will prune historica...

Creating a group or permission mapping from SSO

Using SSO, you can rely on external authentication methods in vScope. Once configured, you can use the external identity provider (IDP) to assign vScope users permissions and/or groups. If you have no...

Setting up Azure Single Sign-On (SSO)

Configuring Single Sign-On (SSO) to use Azure as an identity provider (IDP) to vScope allows you to use enhanced security features, eg. MFA (Multi-factor authentication). Azure can be used to handle a...

vScope and Apache Log4j (CVE-2021-44228)

Summary vScope is not using Log4j2 vScope is not using JNDI or JMSAppender …and is not affected by neither CVE-2021-44228 nor CVE-2021-4104. Background A flaw was found in the Apache Log4j logging l...