Skip to content
vScope Support Page

System Requirements

This is a reference for sizing and prerequisites. For install steps, see the Quickstart or detailed platform guides.

Specs at a glance

Section titled “Specs at a glance”
ScopeCPURAM for vScopeTotal server RAMStorage (SSD)Notes
Minimum (small labs, ≤5k assets)2 vCPU8 GB16 GB60 GBFor evaluation/small envs
Recommended (most envs, 5–20k assets)4 vCPU16 GB24 GB120 GBScale RAM/CPU with asset count
Larger (>20k assets)8+ vCPU31 GB48 GB200+ GBAdd disk if keeping long history

Platforms

Section titled “Platforms”
  • Windows (recommended): Full feature set, including Windows discovery via WMI.
  • Linux (.deb): Supported; Windows discovery via PowerShell/WinRM (no WMI).
  • Docker: Supported; same limitation as Linux (no WMI); mount persistent storage.
  • Kubernetes: Deploy the Linux container with persistent storage; use PowerShell/WinRM for Windows targets (no WMI).

Container sizing

Section titled “Container sizing”

All examples set the maximum Java heap explicitly with -Xmx, paired with a container memory limit that leaves headroom for the JVM memory outside the heap.

RoleContainer memoryMaximum Java heap
Server24 GB16 GB
Discovery proxy6 GB4 GB

Docker sets the limit with --memory; Kubernetes sets resources.limits.memory. If you change either value, change the other in step: an -Xmx above the container limit is terminated by the runtime (OOMKilled) rather than reported as a Java out-of-memory error. The Kubernetes server example also requests 4 CPU cores and a 120 GiB persistent volume.

Size the heap for your workload. vScope is I/O intensive, so leave capacity for OS disk caches and other processes on the host.

Network access

Section titled “Network access”
  • The vScope server must reach all targets (platforms, networks and assets) you plan to inventory.
  • Allow required ports on the host and path to targets; see Ports used by vScope.
  • If activating online or updating, allow outbound HTTPS to vScope services (or follow offline licensing).

Storage growth

Section titled “Storage growth”
  • By default, vScope records and saves 60 months of history which affects the storage growth
  • More assets/tags/history increase disk use. SSD is strongly recommended in larger environments and many expected users.
  • Retaining long history or enabling many trackers increases write load and space needs – plan extra headroom.

Licensing

Section titled “Licensing”
  • Online activation during first sign-in. Offline environments require a license file; see Register License.

Install references

Section titled “Install references”