CHAI DART™ — Assessment Prerequisites

Requirements for Running Discovery & Assessment  ·  2026 Edition  ·  General Distribution
"Stop Modernizing in the Dark. Start with Truth."

At a Glance

Ensure the following are in place before starting a DART assessment project.

CHAI Host

  • CHAI appliance deployed & running
  • Reachable over HTTPS (port 443)
  • Valid CloudHedge license active

Source Hosts

  • Linux: SSH port 22 open
  • Windows: WinRM HTTPS port 5986 open
  • Outbound HTTPS (443) back to CHAI host
  • Supported OS version (see §3 & §4)

Credentials

  • SSH key or password (Linux)
  • Local/domain admin account (Windows)
  • Stored in CHAI Vault before discovery

1. CHAI Host

DART discovery runs from the CHAI appliance. The appliance must be fully deployed and operational before any assessment project is created.

Note: CHAI host installation and deployment prerequisites are covered in a separate document — CHAI Installation & Deployment Prerequisites. Ensure that document's checklist is complete before proceeding.

Hardware Requirements

MachineOSCPU & RAMDisk Space
CHAI™ Appliance Ubuntu 16+  /  RHEL 7.6+, 8.x 4 cores · 16 GB RAM (minimum) 50 GB for /opt  ·  100 GB for /var

2. Linux Source Hosts

Supported Operating Systems

OSSupported Versions
Red Hat Enterprise Linux7.x, 8.x
Ubuntu16.04 and above

Resource Requirements

ResourceMinimum
CPU4 cores
RAM8 GB
Disk — /home> 500 MB
Disk — /opt> 2 GB (must have executable permissions)

SSH & Access Requirements

RequirementDetail
SSH daemonSSHD must be running and accessible on port 22
AuthenticationUsername + SSH private key, or username + password
User privilegeThe SSH user must have passwordless sudo access for DART tools (see below)
CallbackOutbound HTTPS port 443 must be open back to the CHAI appliance

Sudoers Configuration

Add the following two entries to /etc/sudoers (replace <ssh-user> with the actual SSH username):

# Allow DART tool execution without password
<ssh-user> ALL=(ALL) NOPASSWD:/opt/.ch-tools/*/*/*, /opt/.ch-tools/*/*, /bin/mkdir

# Disable requiretty — CHAI connects remotely without a real terminal
Defaults:<ssh-user>    !requiretty
Both entries are required. Missing the !requiretty line will cause discovery to fail even if sudo permissions are correct.

Supported Application Servers (Non-X-Ray Discovery)

For the following Java application servers, DART reads configuration directly — no X-Ray probes required:

Oracle WebLogic 12.1.3 / 12.2.1.4 IBM WebSphere 8.x / 9.x Apache Tomcat 7 / 8 / 9 / 10 JBoss EAP 6.1


3. Windows Source Hosts

Supported Operating Systems

OSSupported Versions
Windows Server2012 R2, 2016, 2019, 2022

Resource Requirements

ResourceMinimum
CPU4 cores
RAM8 GB
Disk (C:\)> 20 GB free

Prerequisites Checklist

RequirementDetail
PowerShellVersion 3 or above — verify with $PSVersionTable.PSVersion
Admin credentialsUser account must have local Administrator or domain Administrator rights
Execution PolicyLocalMachine scope must be RemoteSigned (see below)
WinRM / port 5986WinRM HTTPS enabled with self-signed SSL certificate on port 5986
UAC bypassRequired for local accounts only — not needed for domain/AD accounts (see below)
AntivirusAdd winchtoolpy.exe to the antivirus exclusion list
CallbackOutbound HTTPS port 443 must be open back to the CHAI appliance

Step 1 — Set Execution Policy

Run in PowerShell as Administrator. Check current policy first:

Get-ExecutionPolicy -List

If LocalMachine shows Undefined, set it to RemoteSigned:

Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope LocalMachine

Step 2 — Configure WinRM

Download and run the CloudHedge-provided script as Administrator. It automatically enables PSRemoting, configures Basic authentication, generates a self-signed SSL certificate, and opens port 5986:

.\ConfigureRemoting.ps1

Step 3 — UAC Remote Restriction Bypass (local accounts only)

Skip this step if using domain or Active Directory accounts. For local administrator accounts, run as Administrator:

Set-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System" `
  -Name "LocalAccountTokenFilterPolicy" -Value 1
Not required for domain accounts. Only apply this setting when using a local Windows administrator account.

4. Network & Ports

Required Connectivity

DirectionFromToPortPurpose
OutboundCHAI HostLinux source hosts22 (SSH)Discovery & X-Ray probes
OutboundCHAI HostWindows source hosts5986 (WinRM HTTPS)Discovery
InboundLinux source hostsCHAI Host443 (HTTPS)Data callback
InboundWindows source hostsCHAI Host443 (HTTPS)Data callback
Project limit: Each DART project supports up to 50 hosts (Linux and Windows combined). Plan projects accordingly for large estates.

5. Credentials & Vault

All credentials must be stored in the CHAI Vault before running discovery. Credentials are never stored in plaintext.

Credential TypeUsed ForDetails
SSH private keyLinux host accessPreferred over password auth; stored per project in Vault
SSH username/passwordLinux host accessAlternative to key-based auth
WinRM credentialsWindows host accessLocal or domain administrator account; stored in Vault

Credentials are added via CHAI UI → Project → Vault before initiating discovery. A single set of credentials can be shared across all hosts in a project, or set per-host.


Pre-Assessment Checklist

CHAI Host

Linux Hosts

Windows Hosts

Project Setup


For licensing, image registry credentials, or deployment assistance — contact your CloudHedge account team.
Migrate Anything. Modernize Everything. Break Nothing.