How to change the default WMI timeout setting

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

How to change the default WMI timeout setting 2018-01-02T21:55:01+00:00

Hardware requirements for vScope Core

Depending on the size of the infrastructure to be discovered, the vScope server needs to be configured with the right hardware settings to run smoothly. Here is a list of suggested configurations of the vScope server. CPU cores 2-4 CPU cores recommended In most scenarios two cores will be more than enough. Disk Depending on

Hardware requirements for vScope Core 2018-02-14T12:21:09+00:00

How to speed up the Discovery

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

How to speed up the Discovery 2018-01-02T21:55:09+00:00

How to fix memory leakage in 2003 Servers

On a Windows Server 2003-based computer, you query user account information by using the Win32_UserAccount class in Windows Management Instrumentation (WMI). When you do this, a memory leak occurs in the Wmiprvse.exe process. This is not an issue related to vScope but to Windows Server 2003. In a domain that has many user accounts, the

How to fix memory leakage in 2003 Servers 2018-01-02T21:55:25+00:00

How to enable WinRM on Windows servers & clients

How to enable WinRM on Windows servers & clients About WinRM is a Microsoft implementation of WS-Management Protocol. Read more It allows for better inventory of systems running Windows compared to WMI and is relatively easy to setup. It can be done through a GPO in your Active Directory. How to enable WinRM

How to enable WinRM on Windows servers & clients 2018-01-30T10:58:27+00:00

How to enable WinRM in vScope Discovery Manager

Activating WinRM can significantly improve the performance of vScope discovery. This feature enables discovery to use either WMI or WinRM. When possible, vScope will use WinRM and WMI will only be used as a fallback when WinRM is not available. To enable WinRM discovery in vScope, do the following: Open the Discovery Manager Select a

How to enable WinRM in vScope Discovery Manager 2018-01-02T21:55:28+00:00

Changing RAM settings for vScope Core

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: -

Changing RAM settings for vScope Core 2018-01-02T21:55:30+00:00

How to set up discovery proxies

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

How to set up discovery proxies 2018-05-04T09:53:32+00:00

How to upgrade backend to Kevas2

vScope's database Generation 2 is a hybrid between RAM and disk. This database swaps data between the two states as needed. Hybrid database is significantly more RAM-efficient than the older in-memory technology. It is highly recommended to use the hybrid backend. Older versions of vScope can be upgraded by doing the following: IMPORTANT: All settings

How to upgrade backend to Kevas2 2018-01-02T21:55:46+00:00

vScope service has high memory consumption

Checking vScope RAM-consumtion vScope's memory usage can be viewed under About. The bar shows the actual database size as well as the Java virtual machine allocation (JVM). The JVM-value is what is shown in e.g. the Windows Task Manager. In-RAM or Hybrid Backend? vScope's database Generation 1 is built on In-Memory technology. All data, including

vScope service has high memory consumption 2018-01-02T21:55:50+00:00
Load More Posts