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 […]

McAfee Virus Scan Causes Errors During Discovery Process

Summary During the discovery of your environment, vScope utilizes VB script to perform certain functions. If you have MacAfee VirusScan installed on the machine running vScope, it might interfere with the discovery process. Symptoms may be error dialogs mentioning “cscript.exe” and faulting module ‘ScriptSn’. Problem The following or similar error is displayed during the discovery […]

vScope Service Has High Memory Consumption

Checking vScope RAM-consumtion vScope’s memory usage can be viewed under About -> vScope in settings. 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. Changing the RAM for vScope If the memory consumption is too high […]

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 a […]

Changing RAM Settings for vScope

It might be necessary to update the RAM settings for vScope to optimize performance. The initial RAM setting that vScope uses is set during the installation and controls how much of the system RAM that vScope is allowed to use. vScope will always benefit from adding more RAM to the server but sometimes it is […]

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 Go to […]

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 Speed up the Discovery

vScope’s automatic inventory 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 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 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 WinRM is enabled by default on Windows Server 2012 R2 but […]