FAQ

Blocking by firewalls can prevent JDisc Discovery from getting details from devices on the network. Either open the firewall for the discovery server and the required ports, or use separate installations on either side of the firewall.

Furthermore, you can define any number of IP address exclusion ranges. These are IP4 address ranges that are excluded from discovery.

JDisc Discovery can also ignore specific device types.

Yes, you may even schedule discoveries independently for different areas of your network. This is especially useful if your corporation has sites in different time zones.

JDisc Discovery offers the following types of schedules:

• Run once at a particular time
• Run recurring (e.g. every 2 hours)
• Run daily at a particular time
• Run weekly on a particular weekday / time
• Run monthly on a particular weekday / time

Furthermore you can define periods of inactive discovery (e.g. in times when backups are scheduled).

No, there is no need to install proprietary agents on the target computers. JDisc Discovery uses standard protocols to identify devices.

However JDisc Discovery can, if configured accordingly, deploy a temporary agent on Windows computers. This improves data quality in some cases (e.g. with Windows NT 4.0). For some data, however, the temporary agent is required.

Read more in our Agentless vs. Agentbased Discovery Tools Whitepaper.

For performance reasons, JDisc Discovery discovers devices in parallel. The number of devices to be discovered in parallel may be configured in the Discovery configuration.

Depending on device load, network speed and performance of the discovery server, JDisc Discovery can discover up to 1500 devices per hour.

Firewalls can block the access to WMI or remote registry on Windows computers and prevent getting detailed discovery information. JDisc Discovery offers the possibility to tunnel WMI and remote registry requests via its agents. That means that WMI requests are not executed remotely but by a locally installed JDisc Discovery agent. Local WMI queries are always possible without account. The same applies for registry accesses.

There are many things that can prevent JDisc Discovery from getting proper device details. Misconfigured user accounts or passwords, firewalls, or disabled protocols can for instance impact discovery results.

Therefore, JDisc Discovery features many built in troubleshooting technologies, starting from simple reports and leading up to a rule based analysis of possible problems and a quality meter. JDisc Discovery specializes in getting access problems identified and fixed as quickly as possible.

Refer to the “Discovery Scenarios” and “Troubleshooting” in our user manual.

If nothing helps, simply generate a Device Support ZIP file (refer to support video) and sent it to our support.

Each Microsoft Windows operating system comes with a built in tool called “wbemtest.exe”. Start the tool on the discovery computer by opening a command line first and then start the product “wbemtest.exe” from the command line. That’ll bring up the following Window:

Click the Connect button in order to establish a WMI connection. This opens a new Window where you can enter the connection details such as IP address, user name, and password.

Always use the form domainusername for domains or computernameusername for local computer accounts.

When the connection fails, then you’ll receive an error message. On a successful connection, the buttons within the tool’s main area will be enabled.

Recommended configuration:

Create a dedicated scan user in Active Directory for discovery tasks. This account is used by JDisc Discovery to access Windows systems and collect inventory data. The scan user does not need to be a member of the Domain Admins group and should not be granted domain administrator permissions.

Add the scan user to the local Administrators group on all Windows computers that should be discovered. This can be configured centrally through Active Directory Group Policy, so the required permissions are applied consistently across the relevant systems.

Configure the scan user in JDisc Discovery. A recommended approach is to create a new directory group and assign the scan user to the required part of the directory hierarchy. To do this, open the directory group configuration, switch to the Scope > Directory tab, and add the scan user to the appropriate Active Directory scope.

Our recommendation:

• Use the local built-in administrator user for discovery. You may have to activate it first, as it is mostly deactivated in the standard configuration.

Alternative:

• You can also use another local user who is a member of the local administrators group.In this case you will only get few device details, as this local user is restricted by Windows (Limited User Accounts / LUA). The reason for this is that a Limited User Account (LUA) cannot claim higher privileges from remote that are only granted interactively by the User Account Control (UAC).

Configure the user in JDisc Discovery:

• If each computer uses a different local user / password, select the respective Windows computer in one of the reports and then right-click the context menu: Manage> Change Accounts. There you then enter the user and the password in the lower two input fields (Admin / Root Account).

• If you use the same local user / password for all Windows computers, it is best to create a new network / range group and select the Accounts> Clients & Server> Windows tab. Now you can create the local Windows user by clicking the Add button.

JDisc Discovery detects many SNMP based devices, but there are permanently new devices being released by different vendors. When there are major changes for current models or new vendors, then we need to implement the device support explicitly. We do that at no cost for our customers and the effort is usually very limited.

However, we need your support. We need a SNMP walk in a special format for the unknown devices. Once we have the SNMP walk, we can import the walk file into a SNMP simulator within our labs. This enables our development team to simulate your device within our network.

Download our SNMP Walk product in order to create the SNMP v1 walks in the required format. Submit the SNMP walk file to our support mail address support@jdisc.com.

When using SNMPv3, we recommend to download netsnmp and install it on your JDisc Discovery server and then

snmpwalk -O n -v 3 -a MD5 -A <auth-pwd> -u <user> -x DES -X <priv-pwd> <ip> .1

Usually within one or two weeks, we release a new build that includes the new devices.

Some commands require root privileges on Linux systems. JDisc Discovery can obtain these privileges either through the su command or through sudo, depending on the configured authentication method.

When sudo is used, the sudo configuration must allow the required commands to run with root privileges. For this configuration, the commands executed by JDisc Discovery as root must be known.

JDisc Discovery executes the following commands with root privileges:

Operating Systems

Root Commands for Linux

• /usr/bin/cat /proc/1/environ

• /sbin/ethtool <ifname> or /usr/sbin/ethtool <ifname>

• /sbin/mii-tool <ifname> or /usr/sbin/mii-tool <ifname>

• /usr/bin/find / -perm /111 -type f -print0 -xdev 2>/dev/null | xargs -0 file | grep executable | cut -d’:’ -f1 | xargs ls -l –time-style=long-iso

• /sbin/lsof -i -n -P or /usr/sbin/lsof -i -n -P or /usr/bin/lsof -i -n -P

• /usr/bin/pvecm status

• /usr/bin/clustat -x

• /usr/bin/cat /sys/devices/virtual/dmi/id/product_serial

• /usr/bin/df -lT

• /usr/sbin/smartctl -i /dev/<disk-device-name> or /sbin/smartctl -i /dev/<disk-device-name>

• /sbin/hdparm -I /dev/<disk-device-name> or /usr/sbin/hdparm -I /dev/<disk-device-name>

• /usr/sbin/dmidecode

• /usr/bin/ls -ald /proc/*/exe

• /usr/sbin/qm list

• /usr/sbin/qm config <vmid>

• /usr/bin/lxc-ls –version

• /usr/sbin/runuser -l <username> -c ‘lxc-ls’

• /usr/sbin/runuser -l <username> -c ‘lxc-info -n <vmname>’

• /usr/sbin/runuser -l <username> -c ‘lxc-attach -n <vmname> ifconfig’

• /usr/bin/docker psd

• docker ps -a –format “{{.Names}}”

• docker inspect <containername>

• /usr/bin/cat /var/lib/pacemaker/cib/cib.xml

• /usr/sbin/crm_mon –as-xml

• mokutil –sb-state

• mokutil –list-new

• mokutil –list-delete

• virsh -r list –all

• virsh -r dumpxml <vmname>

• yum history

• yum history info <id>

• yum check-update

• chage -l <username>

• apt update
  but only when apt is used (e.g. on Debian).

Additional Root Commands for Citrix Xen Server:

• /opt/xensource/bin/xe host-list params=uuid,address,hostname

• /opt/xensource/bin/xe vif-list params=vm-uuid,MAC,device

• /opt/xensource/bin/xe pool-list

• /opt/xensource/bin/xe vm-list params=name-label,networks,power-state,is-control-domain,resident-on,affinity,uuid,parent

• /opt/xensource/bin/xe snapshot-list params=uuid,snapshot-of,name-label,name-description,is-a-snapshot,snapshot-time,parent

• /opt/xensource/bin/xe snapshot-list params=uuid,name-description

Root Commands for Mac OSX

• sysctl net.inet.ip.forwarding

• sysctl net.inet6.ip6.forwarding

• otool

Root Commands for AIX:

• no -a

Root Commands for Solaris:

• find / -perm -og+rx -type f -print0 -xdev 2>/dev/null | xargs -0 file | grep executable | cut -d’:’ -f1 | xargs ls -l –time-style=long-iso

• /usr/cluster/bin/cluster list

• /usr/cluster/bin/clinterconnect status

• ndd -get /dev/ip ip6_forwarding

• ndd -get /dev/ip ip_forwarding

• ndd <network_device> link_autoneg

• ndd <network_device> link_duplex

• dladm show-dev

• dladm show-phys

• df -lk

• /opt/SUNWldm/bin/ldm list-domain -o network -p <ldom_name>

• /opt/SUNWldm/bin/ldm ls

• virtinfo -a

Root Commands for HP-UX

• lsof -i -n -P

• /opt/propplusSUNWldm/bin/cprop -detail -c “Memory”

• diskinfo <diskfile>

• /opt/hpvm/bin/hpvmstatus -P <vmname> -Vldm ls

• virtinfo -a

Software

Some root commands are related to specific software items. This section lists the commands which are independent from the underlying Unix operating system.

Root Commands for Apache JBoss

• <jbossinstalldir>/bin/standalone.sh –version

• cat <jboss_componentsfolder>/WEB-INF/web.xml

• cat <jboss_componentfolder>/META-INF/application.xml

• <jbossinstalldir>/run.sh -version

Service Guard Cluster

• /usr/sbin/cmviewcl -v

IBM DB2

• <installdir>/adm/db2licm -l

• db2ls -c

Oracle WebLogic

• cat <installdir>/config/config.xml

• cat <middleware-path>/domain-registry.xml

• cat <installdir>/inventory/ContentsXML/comps.xml

Oracle Database

These files are read to locate Oracle databases on Unix/Linux.

• “/etc/oratab”

• “/var/opt/oratab”

• “/var/opt/oracle/oratab”

• “/etc/opt/oratab”

• “/etc/oraInst.loc”

• “/var/opt/oracle/oraInst.loc”

Postgres

• cat <datadir>/postgresql.conf

Several prerequisites must be met for a successful discovery of the network topology.

• Switches and routers must be managed devices. This means that they must support SNMP and provide access to the required SNMP information.
• Switches and routers must support either CDP (Cisco Discovery Protocol) or LLDP (Link Layer Discovery Protocol). These protocols provide information about direct network connections between devices. Without CDP or LLDP information, the switch topology cannot be discovered reliably. The devices must expose this information through the corresponding MIBs.
• To assign end devices to switch ports, the switches must support the Bridge MIB. The Bridge MIB contains the forwarding table of the switch. This table lists the MAC addresses learned on each port. Without Bridge MIB support, end devices cannot be mapped to the switch ports.
• The assignment of end devices is based on MAC addresses detected within the network. It is therefore essential that the MAC addresses of all relevant devices can be identified during discovery.

The IP Scanner guide provides a comprehensive overview of IP scanners, including their core concepts, operating principles, supported technologies, and typical use cases. It explains how IP scanning helps identify active devices, collect network-related information, and support network inventory and discovery processes. The guide also describes the technical methods used by IP scanners and outlines their relevance for accurate and efficient network analysis.

JDisc Discovery classifies a device as an “Unidentified Device”, if the IP address replies, but none of the protocols succeed in obtaining further information. In this case, we know that a device with a specific IP address exists, but we don’t have any further information about the device.

JDisc Discovery sammelt unterschiedliche Daten für unterschiedliche Geräte. Nahezu vollständig werden Windows Rechner ab NT 4.0, IBM AIX, Sun Solaris, Linux, HP-UX und MAC OS X Rechner identifiziert. Wir können jedoch nicht garantieren, dass wir die folgenden Informationen für alle Geräte sammeln können. Die Unterschiede in Modellen, Betriebssystem-Version und Konfiguration ist einfach zu gross.

Volle Details:

Hardware

• Modell
• Hersteller
• Typ
• Seriennummer
• Artikelnummer
• Prozessoren
• Speichermodule
• Festplatten
• Grafikadapter und angeschlossener Monitor

Software

• Betriebssystem Version
• Patch Level (Service Pack)
• System Typ (x64, x86, ia64, …)
• Installationsdatum
• Uptime
• Eindeutige OS ID
• Locale
• Liste der installierten Applikationen
• Liste der Applikationsinstanzen (beispielsweise Oracle oder MS SQL Server Instanzen)
• Liste der installierten Patches
• Liste der installierten Services
• Firmware Nam
• Firmware Version
• Firmware Datum
• eindeutige Firmware ID

Konfigurationsdaten

• Netzwerk Schnittstellen mit MAC, IP Adressen und Hostnamen
• Konfigurierte Partitionen und Laufwerke
• Aktuell angemeldete Benutzer, Liste der lokalen Benutzer und eine Historie der zuletzt angemeldeten Benutzer
• Virtuelle Computer mit ihren physikalischen Hosts
• Active Directory Zuordnung für Windows Computer
• Windows Domain Zuordnung für Windows Computer

JDisc Discovery is not limited to a specific manufacturer or to a particular device type. Our goal is to support virtually any device that is connected to the network. However, different devices divulge different sets of information. Therefore, it is not possible to get the full set of information for all devices. JDisc Discovery gets very detailed information for computers running with the most common operating systems.

However it gets only basic information (model, brand, serial number, IP address) for other SNMP based devices such as switches and routers.

Detailed network documentation information is available for:

• Windows computers with Windows NT 4.0 and above
• HP-UX workstations and servers
• Oracle Solaris workstations and servers
• IBM AIX workstations and servers
• Linux computers
• VMware ESX(i) servers
• MAC OS X computers

Basis identification is available for:

• SNMP based devices (such as routers, switches, network printers)
• IP phones

In case a new device has been discovered, which JDisc Discovery doesn’t recognize yet, please contact support@jdisc.com . We are able to integrate most of the new devices very quickly into our tool.

Linux computers are secured by default. In many cases, SSH is the only protocol available to access a Linux computer. Unfortunately, SSH does not provide any device information. Therefore it is impossible to identify a device with SSH as sole access protocol if there is no possibility of logging in with valid access credentials.

However you can activate remote login (“active” is the default value in the standard configuration) and define valid accounts and passwords. JDisc Discovery uses them to connect to the computers via SSH and to discover information details via system commands. Refer to “Discovery Scenarios” in our User Manual.

The main reason why you cannot install JDisc Discovery on a Linux/Unix operating system is that many protocols that are required to discover Windows computers (such as WMI) are not available on the Unix platform. However, this does not affect the capability of JDisc to properly discover Linux and Unix computers.

Yes, you can. Simply select the “User interface only” option during the installation process. The user interface communicates with the server via RMI (Remote Method Invocation) on a configurable port. Refer to the administration guide for more details on how to configure RMI ports.

No. JDisc Discovery’s installation procedure includes an embedded prostgres database. There is no need to setup a separate database server!

For some reason there are problems with an unregistered vbscript.dll on some Windows systems. This leads to installation error 2738 when the installation procedure tries to run VisualBasic scripts to configure the application. JDisc Discovery makes use of VisualBasic scripts to configure the software.

First, check that the vbscript.dll is not registered:

Make sure that vbscript.dll is not registered in HKEY_CURRENT_USER (HKCU) by checking the following registry key:
HKCUSOFTWAREClassesCLSID{ B54F3741-5B07-11CF-A4B0-00AA004A55E8}.

Remove this key, if it exists in HKEY_CURRENT_USER.

Secondly, re-register DLL vbscript.dll:

1. Start a command prompt in Administrator mode (Start/All Programs/Accessories/ right click on Command prompt, select “Run as Administrator”)
2. cd %systemroot%system32
3. regsvr32 vbscript.dll (you should see a dialog stating that the registration succeeded)
4. Try re-installing JDisc Discovery

JDisc frequently updates its software. We distinguish between minor updates with smaller enhancements and bug fixes and major release updates. Our smaller upgrades do not get a new version number, but a new build number. Major upgrades do get a new version number (e.g. 2.9). Our license files are still valid when upgrading to new builds within the same version. However, when you upgrade to a new version (e.g. from version 2.8 to 2.9), then you need a new license file. If you have a support contract, then you’ll get it at no cost by sending your license request file to support@jdisc.com .

1. Installing Upgrades when the current installation has at least 4.0

Version 4.0 comes with an improved setup procedure which is able to backup the database and the license file during the upgrade process. However, we recommend to create an archive prior to start the upgrade process.

1. Create a temporay backup folder outside the JDisc installation directory.
2. Archive your database:
   Select the Administration > Database > Archive Database menu item and archive your database. Make sure to enable the option “include passwords within the archive”. Otherwise, you will need to re-enter them after restoring the database. Store the file in your temporary backup folder. Remember the encryption password. You will need it again when restoring the database.
3. Archive your license file:
   The license file stays valid when upgrading between different build numbers of a single version. Copy the “license.txt” file from your installation directory to your temporary backup folder.
4. Start the setup.exe from within the download ZIP.
5. Follow the instructions.

2. Installing Upgrades when the current installation has version 3.4 or earlier.

In order to install minor upgrades (without a version change), you should perform the following steps:

1. Create a temporay backup folder outside the JDisc installation directory.
2. Archive your database:
   Select the Administration > Database > Archive Database menu item and archive your database. Make sure to enable the option “include passwords within the archive”. Otherwise, you will need to re-enter them after restoring the database. Store the file in your temporary backup folder. Remember the encryption password. You will need it again when restoring the database.
3. Archive your license file:
   The license file stays valid when upgrading between different build numbers of a single version. Copy the “license.txt” file from your installation directory to your temporary backup folder.
4. Stop all JDisc Discovery services from the service control manager.
5. Uninstall the software and all Add-Ons
   Uninstall the complete software by uninstalling the add-ons first and then uninstalling the core product.
6. Even if the uninstallation procedure asks for a reboot, the reboot is not required.
7. Install the new version
   Install the new version and the add-ons as required.
8. Restore the license file
   Copy the saved license file from step 3 to the installation directory and overwrite the existing license.txt file.
9. Restart our Discovery Services
   Restore the JDisc Discovery service in order to force a reload of the license file.
10. Check the license status from the Help > License Info dialog.
11. Stop the application
    Open the User Interface und stop the application via Administration > Stop Application.
12. Restore the database
    Use Administration > Database > Restore Database in order to restore the archived database.
13. Start the application
    Start the application again with Administration > Start application.

3. Upgrading to a new version

An upgrade to a new version requires a new license file. Use the instruction from 1, but skip step 2 and replace step 6 by requesting a new license file and installing it.

JDisc Discovery comes with an embedded database. When installing the software on a client computer, a personal firewall might block the traffic between the discovery and its embedded database. We always recommend to install the software on a server operating system (Windows 2003 Server or above), since client operating sytems are limited regarding the number of network connections.

By default, Product uses the Windows ProgramData directory for storing its database. However, the ProgramData directory is by default on the C: drive which is often used for the operating system only.

Always create an archive of your existing database first before you modify any database files!

Follow the steps below in order to move the database to another location or drive.

• IMPORTANT: Create an archive of your database first!
• Stop all JDisc Discovery services (including the database service) from the services control panel
• Enable Show hidden files in the Windows file explorer
• Navigate to c:ProgramData and copy the JDisc folder to the desired location.
• Finally, we need to configure the database service to use the new location. Open regedit and navigate to HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesJDisc Discovery5.0Database. Edit the entry ImagePath and adjust the path behind the -D option. This is the path to the actual database files. It must end with db with possibly trailing backslashes.
• Reboot your server in order to use the new service settings
• Finally, we test whether everything is working fine by renaming the old directory. So just rename c:ProgramDataJDisc to c:ProgramDataJDisc.old.
• Restart the JDisc Discovery services again from the service control panel.
• Try to log-on. If you can logon, then everything works fine and you can finally delete the old database folder c:ProgramDataJDisc.old.

Error Message:
“Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item.”

This error may occur due to security restrictions on your system. Please check the following points to resolve the issue:

• If you are using Windows Defender, open
  Windows Security → Virus & threat protection → Protection history
  and check for any suspicious or blocked entries that may relate to the setup file.

• Windows ASR (Attack Surface Reduction) rules may prevent the installation. You can temporarily exclude the installation folder using the following PowerShell command:Set-MpPreference -AttackSurfaceReductionOnlyExclusions “C:\Temp”(Replace C:\Temp with the folder where you have extracted the JDisc Discovery ZIP file.)

• Additionally, ensure that the ZIP file containing JDisc Discovery is unblocked before extracting it.

To do this, right-click the ZIP file, select Properties, and if the option Unblock is available, check it and confirm. Then extract the ZIP file and run setup.exe again.

In some cases, a personal firewall prevents the JDisc Discovery server from connecting to the embedded Postgres database.

If you have installed the software but you cannot connect to the server via the user interface for more than 5 minutes, then disable the firewall, uninstall the software, and reboot. Perform a reinstall with the personal firewall turned off.

In any case, we recommend to install the software on a server operating system (Windows 2003 Server or above).

Up to version 3.4
You can install JDisc Discovery on any Windows operating system, starting with Windows XP and above.

Starting with 4.0
Starting with JDisc Discovery 4.0, the product is a 64 bit application which can be installed on 64 bit operating systems only (starting with Windows 2008 or Windows Vista).

Important:
We strongly recommend installing JDisc Discovery on a server operating system since Microsoft has introduced a connection limit on their client operating systems starting with Windows XP SP2! This significantly impacts the discovery process and overall operation of JDisc Discovery.

Up to version 3.4
You can install JDisc Discovery on any Windows operating system, starting with Windows XP and above.

Starting with 4.0
Starting with JDisc Discovery 4.0, the product is a 64 bit application which can be installed on 64 bit operating systems only (starting with Windows 2008 or Windows Vista).

Important:
We strongly recommend installing JDisc Discovery on a server operating system since Microsoft has introduced a connection limit on their client operating systems starting with Windows XP SP2! This significantly impacts the discovery process and overall operation of JDisc Discovery.

The WebService registers its SOAP interface on port 9000 (can be changed in the configuration file) after one minute when the service gets started. You might check the web service by calling the following URL from any browser:

http://<JDiscDiscoveryServerIP>:9000/InventoryLogon?wsdl

When the service is active, then the URL returns the XML description of the logon web service SOAP interface. When the URL returns an error, then the web service is not active. Check the logs (logs folder) for error messages.

No!

The WebService implements access to some JDisc Functionality using a SOAP interface on port 9000. However, with the new GraphQL-based API, the SOAP service is obsolete. I-Doit can access our GraphQL-API to perform the same tasks as with the WEB Service starting with i-doit Release 22.

Simply change the protocol in i-doit to HTTPS and use port 443 and then i-doit will use the GraphQL API and you can uninstall the obsolete WEB Service Add-On.

The GraphQL-API offers two major advantages:

• It is using HTTPS by default (as with the WEB Service, HTTP was used by default)
• It is a modern and powerful API that lets you automate everything in JDisc.

The free WebService add-on offers an interface to initiate specific actions or configurations via a SOAP API. The SOAP API is mainly used by our strategic partners which integrate specific JDisc funktionality into their solution.

Yes, you can install as many discovery servers as you want as long as the total number of devices does not exceed the total number of devices purchased.

We are pleased to generate a demo license for more than 25 devices for a fixed period for free! This allows you to test our software intensely in your network.

First, generate a license request file by opening the licensing dialog from the Help > License Info menu. Click on the “Request License” button and save the license request file on your hard drive. After having ordered the software, send this file to our Sales (sales@jdisc.com).

You have free support during the evaluation phase. So feel free to submit your questions to our support ticketing system. On request, we will also review your configuration and data during a short online session (usually 30 minutes to one hour) at no cost..

Please let us know in this email how many devices per operating system you do have in your network. This does not need to be a concrete number. A rough estimation is absolutely sufficient:

1. Number of Unix systems (HP-UX, AIX, Solaris)
2. Number of computers with Linux, VMWare, MAC OS X
3. Number of switches and routers and of computers with a Windows operating system
4. Number of any other devices (such as network printers, scanners, …)

We will sign the license and return it to you. Save the license.txt file in the installation directory, overwriting the existing file.

Restart the JDisc Discovery Windows service in order to reload the license.

Finally, check the license status from Help > License Info.

Many organizations face the same challenge: IT environments grow over time, new systems are added, old ones are retired, and the exact number of devices is often unknown. That is why JDisc Discovery uses a flexible credit-based licensing model instead of rigid per-device licensing.

How the Credit System Works

JDisc Discovery is licensed using credits. Each discovered device consumes a certain number of credits based on its device type or operating system. Whether a system is a physical machine or a virtual machine does not matter.

Devices without an IP address do not require any credits. This includes monitors, webcams, and similar peripherals. Docker containers and other container technologies also do not consume credits.

Maximum Flexibility for Your Organization

A license includes a defined number of credits. These credits can be used for any supported devices within your network. If devices are removed from the JDisc database, the associated credits become available again and can be assigned to other systems.

This allows your license to adapt to changes in your IT environment. Whether you add new systems, replace existing hardware, or restructure parts of your organization, your credits remain flexible and reusable.

Easily Scalable Licensing

Your licensing requirements may change over time. For this reason, JDisc licenses can be expanded at any time by adding additional credits.

If your long-term requirements decrease, the license can also be reduced at the next renewal period. This can be particularly useful after organizational changes, such as the sale of business units or subsidiaries.

Not Sure How Many Credits You Need?

This is a very common situation. Many organizations do not have a complete overview of their IT assets before performing their first inventory. As a result, determining the appropriate license size can be difficult.

To solve this challenge, we offer an extended evaluation license that allows you to scan your entire network.

This provides two important benefits:

1. You can verify that JDisc Discovery meets your technical and operational requirements.
2. You can accurately determine your licensing needs because all devices in your environment have been discovered and classified.

This gives you a complete overview of your IT infrastructure and provides a reliable basis for sizing your future license.

Transparent Licensing Without Surprises

The JDisc credit system allows you to license exactly the systems you need to manage. The allocation of credits is transparent, easy to understand, and highly flexible. This creates a fair and predictable licensing model that grows with your organization.

Would you like to determine your licensing requirements or request an extended evaluation license? Contact us today. We will be happy to assist you personally and help you find the right licensing model for your environment.

Rules for the licenses:

• Every device with an IP address (including virtual machines) counts as one device
• Devices with multiple IP addresses (e.g. routers) count as one device
• Management boards for servers count as separate devices
• For virtual machines the respective OS counts

However, there are some exceptions to those rules:

• Devices that are not identified do not count for the license (Unidentified devices, unknown SNMP devices)
• Devices without an IP address (local printers, monitors, etc.)

JDisc Discovery’s device type filter can already exclude those devices that are not relevant for the licensing at the start. This saves you license cost, discovery time and network bandwidth!

We offer different license models serving your purpose best:

1. Perpetual license
   A perpetual license can be purchased once and has no time limit. Our optional support contract allows you to keep the software up-to-date. This license model is useful for IT organizations that plan to use our software on an ongoing basis.
2. Project license
   A project license is useful for IT service providers or IT organizations, if the software is used only for the duration of a single project. Project licenses can be purchased on a monthly basis and are a cost-effective alternative to the perpetual license or annual subscription.
3. Annual subscription
   In case the purchasing costs exceed your budget or you prefer a yearly fee, our annual subscription might be right choice for you!

Change the value for the registry entry “JVMCustomParameters” below

• HKLM\SOFTWARE\JDisc Discovery x.y\InventoryService64

Add the value “-Xmx2048M ” to the parameter (see screenshot below).

In some cases, the value of 2048M might be to large for your installations. In this case, the discovery process will not start. Reduce the value and then try it again.

The settings for the database cache are located within the file “postgresql.conf” in the “<installdir>dbdata” directory. Open the file with an editor and search for the setting “shared_buffers”. Increase the value from 128MB for instance to 512MB (see screenshot below).

Restart the “JDisc Discovery Database” service in order to refresh the settings.

All reports can be exported either to CSV (comma separated values) or Microsoft Excel documents. Use the icons in the toolbar of the report window.

JDisc Discovery has a powerful grouping concept. Groups can be defined in a hierarchical manner, plus conditions for groups can be defined. Whenever a device is discovered, it is matched against the group conditions. On success, it will be automatically assigned to the group. There is no manual interaction involved apart from defining the conditions.

The group conditions include:

• Matches for network membership
• Matches for membership in an IP address range
• Matches for a Windows domain membership
• Matches for membership within organizational units of a Microsoft Active Directory
• Hostname matches
• Manufacturer matches
• Device model matches
• Device types matches

You can schedule automatic export of nearly all reports. For this, you schedule the time and the target directory for your reports. JDisc Discovery executes those reports automatically and stores them under  the defined target directory.

JDisc Discovery offers a powerful report generator. You can use it to generate your own individual reports by:

1. defining the relevant attributes
2. defining possible restrictions on attributes
3. defining the appearance / sequence of the columns in your individual report.

You can use nearly all device properties (such as model, manufacturer, applications, etc.) in our custom reports.

Consider, for instance, that you would like to replace your slow old PCs with new ones. Therefore, you are looking for all laptops with a processor speed less than 1 GHz. Limiting the device type to “Laptop” excludes all devices which are not classified as laptop. Limiting the processor speed to “<1 GHz” excludes all modern laptops.

Custom reports can be saved for later re-use.