vScope can use WMI (Windows Management Instrumentation) to discover information from Windows operating systems. Using the protocol can result in latency issues and slow down the Discovery in vScope. To not stall the Discovery, WMI has in vScope a timeout of 15 minutes. This means that if the WMI discovery of a resource is not finished
Integrating vScope with your organization's directory service allows you to reuse domain accounts to login to vScope. When integrationg with larger domains it might take vScope some time to authenticate and resolve the group membership of users. In order to speed up the authentication you can set the method of how vScope resolve the membership.
Integrating vScope to your AD/LDAP service let you reuse domain user accounts directly in vScope without having to manually add them. To be able to use this feature you will need to set up authentication for the directory service in vScope. This is how it is done: 1. Enter authentication details Start by going into
This is a step-by-step guide to setup Microsoft Internet Information Server (IIS) as a Reverse Proxy in front of vScope to support SSO (Windows Authentication). 1. Install IIS via Server Manager -> Manage -> Add Roles and Features Select Web Server (IIS) Role Select sub role: Security -> Windows Authentication 2. Enable Windows Authentication on
The vScope discovery runs without the use of any agents. The default discovery settings are set to run once a day and are configured to the size of a datacenter of up to 400-500 units. If you want to increase the discovery scope of vScope (eg. add discovery of large client networks) you might want
The minimum set of roles and privileges required to scan Oracle Database are: Role: SELECT_CATALOG_ROLE Why: Allows the user to read information about the database, users and their privileges. How to apply: ALTER USER "USERNAME" DEFAULT ROLE "SELECT_CATALOG_ROLE"; System Privilege: CREATE SESSION Why: Allows the user to connect (create a session) to the database.
Sometimes it might be necessary to change the RAM settings to optimize the vScope performance. This can be done by either: Run installer Stop the vScope service Run the latest installer of vScope (found Here) Start the vScope service again From the register Stop the vScope service Run regedit.exe and search for the key: -
vScope searches ranges using ping- and port scan methods. vScope's normal behavior is to first try ping. If ping does not return any response, vScope continues to test a few commonly used ports. To disable vScope's port scan fallback, do the following: Stop vScope Server service Open the file C:vScopeDataconfigurationconfig.ini (This file may be on
Migrating the vScope installation can be done in two different ways. Both instruction sets will migrate all configurations and settings of vScope including history, Discovery scope, users, presets, Tracker profile settings etc. Notice that migrating an installation with Kevas1 to a vScope installation running Kevas2 will not include history (as described in Switching to Hybrid
Proxies are used to make discovery in network zones where the main vScope might not have full access on all relevant ports, such as a DMZ, a customer network or another closed network. vScope proxies communicate with the main vScope over one single port. You can use as many proxies as you wish. Prepare