Frequently Asked Questions2018-08-06T14:36:24+00:00
FREQUENTLY ASKED QUESTIONS

FAQ

If you can’t find what you are looking for, feel free to contact our support directly

For more technical support, have a look in the full Knowledge base

General questions

Short answer:

vScope is an inventory platform of IT infrastructure. It can discover and map dependencies between assets and resources from most well-known technical platforms within a datacenter such as VMware, Windows Server/Client, Oracle DB, Active Directory, IIS Microsoft SQL Server and more.

With access to such information you may use vScope for Documentation & Reporting, CMDB, Billing & Chargeback, Licensing, Configuration Analysis or Cost Management

Longer answer

vScope is licensed on a subscription based model requiring no upfront fees or additional costs.

Read more.

A Billable Unit is the metric of how many resource that vScope maximum can display. Every product has it’s own BU, making it easy to customize the license for any organization’s setup.

See the list of BU corresponding each product is here.

We offer all organizations running a vScope subscription (trials included) online support to everyone in the subscriber’s organization. Support can be contacted directly from your vScope installation, via email, the online support page, telephone/Skype/Voice and of course via your closes InfraSight rep.

The support includes:

  • Help with use cases and how-to:s in vScope to maximaze the value of your subscription
  • Technical questions related to setting up and configuring vScope
  • Guidance and suggestions from a vScope expert
  • Full access to online resources such as blogs, videos, knowledge base and much more
  • Automatic updates of vScope is always included

With a vScope subscription you are also able to purchase additional education in which we customize workshops for your organization’s needs.

The vScope platform is built to support input from an arbitrarily number of different sources, and put the pieces together into one unified vScope model/database. The list of probes is extended continuously.

See current probes.

vScope comes with an open REST API allowing any organization with a subscription to make use of the vScope data in other systems. This means that any system supporting import of data in formats such as CSV, json or XLXS can be integrated with vScope. Service Now, PowerBI, and Sharepoint are some examples of systems in which you can use vScope as the data collection engine.

If you want to learn more about integration, please read more on the following page:

Integrating vScope

Integrating vScope and ServiceNow

Integrating vScope and PowerBI

vScope communicates with the world using several different APIs and protocols. Here is a short guide into what ports that needs to be open in your firewall(s) to make vScope work.
– vScope Legacy is the name for the licensed functionality available in vScope up until version 2.x. vScope Legacy represents vScope as one (quite large) single product.

If you have come to this page, and you are already running an installation of vScope, you are most probably running vScope Legacy.

Read more.

InfraSight Labs always strive to keep your part of the maintenance of vScope to a minimum. One way is to automate the software updating process. When setting the Software Updates option (Under Settings/Software Updates) to “Releases Automatically”, vScope will automatically download and apply new versions of vScope when available. This setting is enabled as default and there is no need for the user to do anything.

software-updates-in-vscope

New versions are normally applied within 24 hours from release, but not during office hours.

Read about doing a manual update.

Privacy & Security

vScope uses credentials to log in to various components of your datacenter. The benefit is that no agents are needed, which is cost-efficient, safe and fast. All passwords are treated carefully to ensure highest security at all times.

  • Only vScope-Admins can view the Discovery Manager
  • When entering credentials, the password is never displayed – not even to Admins
  • Credentials are encrypted and stored in the vScope backend on the vScope server, on premise
  • Passwords must be re-entered e.g. to login on a server via RDP
  • Passwords cannot be retrieved from the API
  • vScope is read-only and will not perform any actions or write anything to the environment except for on the vScope-server itself

Account & Licensing

Have you been provided an activation code for a vScope license and now you are trying to find out where to use it? Here is the answer:

The code is used for licensing a vScope installation. This might be relevant if you want to license your Limited vScope, go from Trial to Licensed vScope or when upgrading your current vScope license. The code can be found under your organization’s account page. The code can be entered in two different views:

Use code for installation

When setting up a vScope for the first time, you will be given three options. One of these option says “I have a code”. This is the view in which you input the code and your vScope installation will be magically licensed!

Use code for existing vScope

Under the About page in vScope, you will find a “Activate New License” button. Click on it and enter the code in the input field that appears.

Every product added to the vScope Core platform has its own license limit (counted in Billable Units, BUs) which in a real context would be eg.

License for Company A:

  • Virtualization, 50 BUs (45 units are discovered)
  • Server, 50 BUs (40 units are discovered)

Sometimes, you might accidentally exceed this limit for one or several products. For instance, Company A adds a new range in Discovery Manager which results in that additional servers are discovered. This causes the total number of discovered servers (BUs) increase from 40 to 180 (outside of the license limit)… Read more

vScope needs a valid licens fully function. The licenses are distributed via the License account service (you can access via http://account.vscope.net) and during setup your vScope installation will automatically connect and confirm its existens so it receives a valid licens. Smooth!

However, sometimes the vScope installation might not be able to reach the License account service. This can be due to that you vScope is installed in a closed network with no access to neither internet nor the License account service. In these cases, you will need to activate your vScope installation manually by uploading a license file locally on the vScope server. Here is how!

During the installation of a new vScope you might have noticed that you can choose to activate it with a code. This code is available whenever you have chosen to subscribe to a vScope license. This could either be during an assisted trial or for a full commercial license subscription

The code is provided to you either by a InfraSight representative or you can find it on the License account page. This is how you find it on your License account page

A Billable Unit is the metric of how many resource that vScope maximum can display. Every product has it’s own BU, making it easy to customize the license for any organization’s setup. Here is the list of BU corresponding each product
vScope is licensed on a subscription based model requiring no upfront fees or additional costs.

Read more here

Licenses are normally distributed via the Licenses & Billing Account. If the account is not available (e.g. due to firewall) a license file can be loaded manually instead. The manual license file can be retrieved from InfraSight Labs Support.

Follow this guide to add it manually

Licensing metrics from a vScope-installation is normally sent to InfraSight Labs in a so called heartbeat. Customers can easily retrieve this information from https://account.vscope.net. But there are times when one need to get the metrics in a raw format directly from the server. Here is how to do:
  • Go to vScope at http://[YourvScopeServer]/ui and log in with a vScope Admin-account
  • Then type in http://[YourvScopeServer]/rest/license
  • The license information is displayed
  • The detailed file called license.json can be saved using the Save button to the left

Installation & Setup

By adding your directory services to vScope’s discovery scope you will be allowed to build reports about user accounts, domains, groups or other information related to your directory service.

The short story – Adding directory service to Discovery Manager

Adding your directory service to the discovery scope is easy.

  1. Open the Discovery Manager
  2. Click + Add More
  3. Select your Directory service (Active Directory or LDAP)
  4. Enter Username, password Base DN (optional)
  5. Enter target=hostname/IP of you domain controller
  6. Click Next
  7. Finished!

If you stumbled on something related to “invalid credential” or are looking for more advanced information related to to discovery services, please read further here.

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

 vScope needs a valid licens fully function. The licenses are distributed via the License account service (you can access via http://account.vscope.net) and during setup your vScope installation will automatically connect and confirm its existens so it receives a valid licens. Smooth!

During the installation of a new vScope you might have noticed that you can choose to activate it with a code. This code is available whenever you have chosen to subscribe to a vScope license. This could either be during an assisted trial or for a full commercial license subscription

The code is provided to you either by a InfraSight representative or you can find it on the License account page. This is how you find it on your License account page

vScope Core is really easy to install and the process can be broken down into 2 steps.

Use this link to open guide in a new window

For vScope to be able to analyze your Azure Resource Manager environment you need to give vScope read rights to your subscription(s). This is done by creating an Azure application, generating a key and applying these to an Azure RM credential in vScope.

Follow this guide to get started using Azure Resource Manager with vScope. 

NOTICE:  vScope reach the Azure APIt through management.core.windows.net on port 443 (HTTPS). This needs to be open for this guide to work.
vScope support Discovery of SSH. It first runs “uname -a” to try to figure out nix-flavour of target system. After that it runs several commands and reads a few files. For commands it first checks if it’s available on the target system by issuing “command -v {cmd}” before it tries to run it. If not found this way it also looks for it under “/sbin” and “/user/sbin”.
If vScope receives “Permission denied” when trying to run a command it checks if current user is allowed to do sudo by issuing “sudo -v” if this succeeds it will retry original command with sudo “sudo {cmd} ”. If sudo check fails it will not try to use sudo for any of the following commands within the target session. For files it first checks if file exists with “test -f {file}”before trying to read it.

Please contact us via the Online Support form  for more information.

To install packages from InfraSight Labs repository, type the following commands in a console on the installation machine:

wget -O - http://vscope.net/debian/infrasightlabs.com.gpg.key | sudo apt-key add -
echo 'deb http://vscope.net/debian release main' | sudo tee /etc/apt/sources.list.d/vscope.list
sudo apt-get update
sudo apt-get install vscopeserver

After installation, continue setup in a browser at http://[server-name].

Automatic updates

InfraSight Labs always strive to keep your part of the maintenance of vScope to a minimum. One way is to automate the software updating process. When setting the Software Updates option (Under Settings/Software Updates) to “Releases Automatically”, vScope will automatically download and apply new versions of vScope when available. This setting is enabled as default and there is no need for the user to do anything.

software-updates-in-vscope

New versions are normally applied within 24 hours from release, but not during office hours.

Manual updates

Users may trigger the checking and the deployment for a newer version manually, by clicking on the green check-box icon on the About-page.

manualupdatevscope

If a new version is then available, the icon will turn orange. The new version will be downloaded, and the user will be prompted to restart vScope in a single click. vScope – in a newer version – will restart in an instant.

vScope settings

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

The default setting in vScope is to scan max 5 targets at the time. It is however possible to change the number of parallel discovery threads vScope should run, or even make vScope dynamically decide on the best number of simultaneous threads. Note that this adds extra load on the CPU.

Find out how to configure number of Discovery threads here

When vScope is running, open a browser and type in: http://[server name or IP-address]/apidoc/   (NOTE: make sure to add the trailing slash/)
vScope web GUI is by default reached through HTTP. To reconfigure the vScope web GUI to HTTPS, follow the steps below.

  • Stop vScopeServer service
  • Download, unzip and copy this Jetty.keystore-file to C:/vScopeData/configuration
  • Add the following lines in C:/vScopeData/configuration/config.ini

———
# enable SSL (default disabled)
org.eclipse.equinox.http.jetty.https.enabled=true

# set SSL port (defaults to 443)
org.osgi.service.http.port.secure=443

# Location of keystore containing SSL certificate
org.eclipse.equinox.http.jetty.ssl.keystore=C:/vScopeData/configuration/jetty.keystore

# Password for keystore
org.eclipse.equinox.http.jetty.ssl.password=vscopeserver
———

  • Add a # in the beginning of existing line “org.osgi.service.http.port” if you want to disable plain HTTP access)
  • Start vScopeServer service again
  • Open port 443 in machine Firewall (Windows Advanced Firewall)

Optionally you can generate your own self-signed certificate (if you have JDK tools installed):
keytool -keystore jetty.keystore -alias vscopeserver -genkey -keyalg RSA

If you want to create a SSL certificate signed by a trusted authority this can also be done (either you have you own CA or send a signing-request to a 3rd party CA). The resulting certificate can then be imported into jetty.keystore to be used by vScope server.

Troubleshooting

A vScope license is bound one single machine where vScope is intended to run. One of the parameters in determining a unique machine ID is mac addresses. On some platforms, there are situations where mac addresses change, e.g. when there is no network connectivity or network setting have changed (like adding or removing a connection). This can cause vScope to signal “Wrong License” even though there is an accurate license available.

If you do have this problem, please contact support@infrasightlabs.com for help.

In vScope. Settings -> Online Backup -> Upload Now.

A log will be sent to InfraSight Labs. Please write down a short description to your problem before submitting.

The easiest way to share logfiles with InfraSight Labs is to send them to us via vScope (Settings -> Online Backup -> Upload Now).

When this option is not available, the log file can be found here C:/vScopeData/log/debug.log

Miscellaneous

Sometimes adding targets to the Discovery Manager can be tedious work, especially if there are many targets to be added. A way around this is to import targets via the API.

This is done in two steps:

  1. Create a CSV file that contains one column for the IP range and one for the corresponding Note.
  2. Access the vScope API via http://[vscope-server-name]/apidoc/ and upload the CSV file

The API also provides additional options such as removing existing targets and fully replace the Discovery targets with the one’s included in the CSV.

Read more