Here we collect more technical questions related to vScope.

Integrating vScope with ServiceNow

vScope is based on a unique data collection engine that not only gathers and structures data. It also automatically correlates resources from several different technologies into a virtual map showing the complete datacenter set up. You can then browse this map in vScope's intuitive UI. Another great way to make use of vScope's data collection

Integrating vScope with ServiceNow2018-01-15T07:55:33+00:00

How to retrieve vScope licensing information from API

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

How to retrieve vScope licensing information from API2018-01-02T21:54:56+00:00

Supported algorithms for SSH

The SSH probe in vScope supports the following algorithms when connecting to Linux/Unix machines during discovery: Ciphers aes{128,192,256}-{cbc,ctr}, blowfish-{cbc,ctr}, 3des-{cbc,ctr}, twofish{128,192,256}-{cbc,ctr}, twofish-cbc, serpent{128,192,256}-{cbc,ctr}, idea-{cbc,ctr}, cast128-{cbc,ctr}, arcfour, arcfour{128,256} SSH Probe also supports the following extended (non official) ciphers: camellia{128,192,256}-{cbc,ctr}, camellia{128,192,256}-{cbc,ctr}@openssh.org Key exchange diffie-hellman-group1-sha1, diffie-hellman-group14-sha1, diffie-hellman-group14-sha256, diffie-hellman-group15-sha512, diffie-hellman-group16-sha512, diffie-hellman-group17-sha512, diffie-hellman-group18-sha512 diffie-hellman-group-exchange-sha1, diffie-hellman-group-exchange-sha256, ecdh-sha2-nistp256, ecdh-sha2-nistp384, ecdh-sha2-nistp521, curve25519-sha256@libssh.org SSH Probe also supports the following extended (non official) key exchange algorithms: diffie-hellman-group14-sha256@ssh.com, diffie-hellman-group15-sha256, diffie-hellman-group15-sha256@ssh.com, diffie-hellman-group15-sha384@ssh.com, diffie-hellman-group16-sha256, diffie-hellman-group16-sha384@ssh.com, diffie-hellman-group16-sha512@ssh.com, diffie-hellman-group18-sha512@ssh.com Signatures ssh-rsa, ssh-dss, ecdsa-sha2-nistp256, ecdsa-sha2-nistp384, ecdsa-sha2-nistp521, ssh-ed25519 MAC hmac-md5, hmac-md5-96, hmac-sha1, hmac-sha1-96, hmac-sha2-256, hmac-sha2-512

Supported algorithms for SSH2018-01-02T21:54:59+00:00

How to discover directory services with vScope

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. Open the Discovery Manager Click

How to discover directory services with vScope2018-10-02T12:46:03+00:00

Common error codes for Active Directory authentication

Common error codes for Active Directory authentication vScope supports both Discovery of and integration with the Active Directory. If something goes wrong you will be prompted with an error message that can give you a hint of the cause to the issue. The error messages might look something like this: INVALID_CREDENTIALS: 80090308: LdapErr: DSID-0C09042F,

Common error codes for Active Directory authentication2018-08-21T12:03:48+00:00

Verify WMI access for a regular non-admin domain user

Verify WMI access for a regular non-admin domain user This is a guide on how to enable and test WMI access with a regular domain user without generic admin rights. Make sure you have followed the steps in the KB Setting up WMI-access through AD & GPO. This ensures that you have configured DCOM access,

Verify WMI access for a regular non-admin domain user2018-08-21T12:09:50+00:00

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 setting2018-01-02T21:55:01+00:00

Adding Amazon Web Services (AWS) to vScope

Sign in as Admin on the AWS Console page Under AIM, create a new user called eg. "vscope" with Access Type "Programmatic access" On the second step of Add user, select "Attach existing policies directly" and check AWS-inbuilt policy "ReadOnlyAccess" Copy "Access key ID" and "Sercret access key" and input in the Discovery Manager

Adding Amazon Web Services (AWS) to vScope2018-10-02T12:49:57+00:00

How to change group nesting settings for LDAP/AD integration

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.

How to change group nesting settings for LDAP/AD integration2018-01-02T21:55:03+00:00

How to activate an offline vScope installation

We recommend you to run vScope on a server with internet access in order to automatically receive updates and fixes from our license server. However it is sometimes inevitable to install and run vScope on a server in a closed network. In order to run such offline vScope you will have to activate the installation with

How to activate an offline vScope installation2018-01-02T21:55:03+00:00
Load More Posts