Device Scout System Requirements

This document helps you to properly size a deployment environment for the Device Scout.

Hardware Requirements

The following Microsoft Windows platforms will support the Device Scout, in both 32-bit and 64-bit versions. For production deployments, we recommend a server platform.

• Microsoft® Windows Server 2022
• Microsoft® Windows Server 2019
• Microsoft® Windows Server 2016
• Microsoft® Windows Server 2012 R2
• Windows 8.1, Windows 10, Windows 11

The Device Scout platform should be sized according to its intended use. The table on the following page provides basic sizing guidelines based upon the size of the planned discovery environment and the number of active output devices.

The processor requirements are stated in terms of single-core CPUs. For the purposes of installing the Device Scout, multiple-core CPUs can meet multiple-CPU requirements. For example, a dual-core CPU running at 1.2 GHz or higher will meet the requirements of 2 single-core 1.2 GHz CPUs.

Environment	Recommended Platform
Scan size: up to 5,000 IPs Devices: up to 500	Small system CPU: 2 x 1.2GHz or greater (32 or 64 bit) RAM: 2GB Free space: 20GB 100 Mbps network interface
Scan size: 5,000 – 10,000 IPs Devices: 500 – 1,000	Medium system CPU: 2 x 1.2GHz or greater (32 or 64 bit) RAM: 4GB Free space: 20GB 100 Mbps network interface
Scan size: 10,000 – 20,000 IPs Devices: 1,000 – 2,000	Large system CPU: 2 x 1.2GHz or greater (64 bit) RAM: 4GB Free space: 40GB 1000 Mbps network interface
Scan size: over 20,000 IPs Devices: over 2,000	Consult Pharos Systems International

Software Requirements

The Microsoft® .NET Framework 4.6.1 or higher must be installed. If it is not already installed, it is installed automatically during the Device Scout installation process.

The Device Scout can coexist with other .NET frameworks installed in parallel.

Installing in a virtual environment

You can install the Device Scout in a virtual environment. The system requirements listed above are measured in physical hardware. If you are installing in a virtual environment, convert the requirements to virtual resource equivalents per your virtual platform’s conversion guidelines.

Installing along with other network discovery tools

You can install the Device Scout in an environment with other network discovery applications. In this scenario, the hardware requirements should be treated as additional to the hardware requirements of any other applications that will run in parallel.

Scanning multiple network segments

If you are installing multiple Device Scouts to scan different network segments, you must install each Device Scout on its own virtual machine. Multiple Device Scouts cannot be installed within the same operating system.

Network Requirements

• Secure Printers must be able to reach the Device Scout Fully Qualified Domain Name on port 4321.
• Make sure the Device Scout is in the same Windows domain as the client computers (users workstations) at the time of install.
• Ensure Windows firewall rule is applied.
• Proxy server name if required to access the internet.
• Administrator access to the Windows server where the Device Scout will be deployed.
• TLS v1.2 must be enabled.
• The Device Scout must be able to communicate with the cloud APIs to (1) upload collected device data and (2) download application updates and configuration settings.
• The Web proxy server configuration (server, port, user credentials) is known, if required to access the Internet (cloud).
• For Windows systems, end point protection (antivirus) software must trust the Device Scout and Local Connector executable (exe) files and dynamic link library (dll) files within this directory path and all its subfolders:
  • C:\Program Files (x86)\PharosSystems\DeviceScout
  • C:\Program Files (x86)\PharosSystems\Sentry Print Service
• End point protection (antivirus) software must trust the Windows services for the Device Scout and Local Connector:
  • Pharos Device Scout Service

  • Pharos Systems Sentry Print Service

• The Device Scout must be able to communicate with network printers to collect device data.
• When using the Local Connector configuration, the Device Scout must be able to communicate with network printers to (1) secure integrated printers and (2) authenticate users. If Active Directory is the authentication provider, the Device Scout must be (1) joined to an on-premises Microsoft Active Directory domain and (2) joined to the same domain as Print Scouts (print user workstations).
• The following network ports must be open:
  • Outbound (Device Scout connecting to the cloud API endpoint):
    • 443 TCP (TLS v1.2)
  • Outbound (Device Scout connecting to the HP integrated printer):
    • 443 TCP (TLS v1.2)
    • 7627 TCP (TLS v1.2)
    • 161 UDP (SNMP)
  • Inbound (HP integrated printer connecting to the Device Scout):
    • 4321 TCP (TLS v1.2)
  • Outbound (Device Scout connecting to the KM integrated printer):
    • 80 TCP (HTTP)
    • 50003 TCP (TLS v1.2)
    • 161 UDP (SNMP)
  • Inbound (KM integrated printer connecting to the Device Scout):
    • 4321 TCP (TLSv1.2)
    • 50004 TCP (TLSv1.2)
    • 50006 TCP (TLSv1.2)
  • Outbound (Device Scout connecting to the Lexmark integrated printer):
    • 443 TCP (HTTP)
    • 161 UDP (SNMP)
  • Inbound (Lexmark integrated printer connecting to the Device Scout):
    • 4321 TCP (TLSv1.2)
  • Outbound (Device Scout connecting to the Ricoh integrated printer):
    • 443 TCP (TLS v1.2)
    • 51443 TCP (TLS v1.2)
    • 161 UDP (SNMP)
  • Inbound (Ricoh integrated printer connecting to the Device Scout):
    • 4321 TCP (TLSv1.2)
  • Outbound (Device Scout connecting to the Xerox integrated printer):
    • 443 TCP (HTTP)
    • 161 UDP (SNMP)
  • Inbound (Xerox integrated printer connecting to the Device Scout):
    • 4321 TCP (TLSv1.2)
  • Outbound (Device Scout connecting to the Canon integrated printer):
    • 8443 TCP
  • Outbound (Device Scout connecting to the Toshiba integrated printer):
    • 49630 TCP
    • 50083 TCP