Install agent on a Windows Server VM using WSL2 - Precisely Data Integrity Suite

Data Integrity Suite
Product
Spatial_Analytics
Data_Integration
Data_Enrichment
Data_Governance
Precisely_Data_Integrity_Suite
geo_addressing_1
Data_Observability
Data_Quality
dis_core_foundation
Services
Spatial Analytics
Data Integration
Data Enrichment
Data Governance
Geo Addressing
Data Observability
Data Quality
Core Foundation
ft:title
Data Integrity Suite
ft:locale
en-US
PublicationType
pt_product_guide
copyrightfirst
2000
copyrightlast
2026

Install the Data Integrity Suite agent on a cloud-provisioned Windows Server 2022 virtual machine (AWS, Azure, or GCP) using Windows Subsystem for Linux 2 (WSL2). Because WSL2 requires Hyper-V, you must select a VM type that supports nested virtualization.

Choose a VM that supports nested virtualization

WSL2 requires Hyper-V, which depends on hardware virtualization extensions being available inside the VM. Standard virtualized instances do not expose these extensions. Select a VM type that supports nested virtualization from your cloud provider.

AWS

Standard Nitro instances (for example, m5, c5) do not expose VT-x to the Windows guest. Use bare-metal instances:

Instance vCPU RAM
c6i.metal 128 256 GB
m6i.metal 128 512 GB
r6i.metal 128 1,024 GB

OS image: Windows Server 2022 Base. OS disk: 128 GB minimum.

Azure

Nested virtualization is supported on Dv3, Ev3, Dsv3, Esv3, Dv4, Ev4, Dv5, Ev5 families and later. Older families (Av2 and similar) do not support it.

VM Size vCPU RAM
Standard_D8s_v3 8 32 GB (minimum)
Standard_D16s_v3 16 64 GB
Standard_E8s_v3 8 64 GB

OS image: Windows Server 2022 Datacenter: Azure Edition (Generation 2). OS disk: 128 GB minimum. The Azure Edition image has Hyper-V pre-validated for Azure VMs.

GCP

Nested virtualization must be explicitly enabled at VM creation time. It cannot be added to an existing VM.

Machine Type vCPU RAM
n2-standard-8 8 32 GB (minimum)
n2-standard-16 16 64 GB
c2-standard-8 8 32 GB

OS image: windows-server-2022-dc. Enable nested virtualization when creating the VM.

Minimum VM specifications

Requirement Minimum
Windows Version Windows Server 2022
vCPU 8
RAM 32 GB
OS Disk 128 GB
Nested Virtualization Required
Note: WSL2 allocates 50% of the host RAM by default. On a 32 GB VM, WSL2 receives approximately 16 GB, which is the minimum required by the agent preflight check. A VM with less than 32 GB will cause the memory check to fail.

Step 1: Connect to the VM and open PowerShell as Administrator

Connect to your VM using Remote Desktop (RDP). Once connected:

  1. Select Start.
  2. Search for PowerShell.
  3. Open the context menu for Windows PowerShell and select Run as administrator.

Step 2: Install WSL2 and Ubuntu

Note: On Windows Server 2022, the Windows Store is not available. The distro name Ubuntu-24.04 is not resolvable in this environment. Use the generic Ubuntu name instead, which installs the latest available Ubuntu LTS (24.04).

Run:

wsl --install -d Ubuntu

If the command fails because WSL features are not enabled, run these commands first:

Enable-WindowsOptionalFeature -Online -FeatureName VirtualMachinePlatform -NoRestart
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux -NoRestart

Restart the VM, then run the install command again:

wsl --install -d Ubuntu

After installation completes, set WSL2 as the default version:

wsl --set-default-version 2

Verify that Ubuntu is running under WSL2:

wsl --list --verbose

Expected output:

  NAME      STATE   VERSION
* Ubuntu    Running       2
Warning: The VERSION column must show 2 . If it shows 1, run: 
wsl --set-version Ubuntu 2

Step 3: Set up your Ubuntu user account

The first time you open Ubuntu, you are prompted to create a Linux username and password. This account is separate from your Windows credentials.

Open Ubuntu from the Start menu or run:

wsl -d Ubuntu

Follow the prompts to create a username and password.

Step 4: Verify resources inside Ubuntu

On a correctly sized VM (32 GB RAM, 8 vCPU), WSL2 receives sufficient resources by default. No .wslconfig file is required.

Check available memory:

free -h

Expected: Mem: 15Gi or higher.

Check CPU count:

nproc

Expected: 8 or higher.

If memory shows less than 15 Gi, create C:\Users\Administrator\.wslconfig on the Windows side with the following content:

[wsl2]
memory=16GB
processors=8
swap=0
networkingMode=mirrored
autoProxy=true

Then restart WSL2:

wsl --shutdown
wsl -d Ubuntu

Step 5: Verify that systemd is running inside Ubuntu

The agent installer registers k3s as a systemd service. Ubuntu 24.04 enables systemd by default in WSL2, so no additional configuration is required.

Inside Ubuntu, verify:

systemctl --no-pager status

Expected: output contains State: running.

If systemd is not running (Ubuntu 22.04 only), run the following inside Ubuntu:

sudo tee /etc/wsl.conf <<'EOF'
[boot]
systemd=true
EOF

Restart WSL2, then verify again:

wsl --shutdown
wsl -d Ubuntu

Step 6: Verify available disk space inside Ubuntu

The agent installs under /precisely. The preflight check requires at least 64 GB of free space on the Linux root filesystem.

df -h /

The Avail column must show 64 GB or more.

Note: The WSL2 virtual disk (ext4.vhdx) is stored on your Windows OS drive (typically C:\). If disk space is insufficient, ensure the Windows OS disk has at least 64 GB free. You may need to resize the OS disk for the VM from your cloud provider console and then extend the Windows volume.

Step 7: Download discli inside Ubuntu

wget https://cdn.cloud.precisely.com/agent-cli/discli
chmod +x ./discli
Warning: Do not run discli from a Windows-mounted path such as /mnt/c/ or /mnt/d/. k3s and containerd require a built-in Linux ext4 filesystem. Running from an NTFS-mounted drive causes overlay filesystem errors and the preflight check will block the installation.

If you transferred the binary from Windows via RDP file copy, move it into your Linux home directory:

cp /mnt/c/Users/Administrator/Downloads/discli ~/discli
chmod +x ~/discli

Verify the binary:

~/discli -version

Step 8: Install the agent

Run this command from your Linux home directory (~), not from any /mnt/* path.

Run the agent installation command generated for your agent instance from Data Integrity Suite. For the installation command and full instructions, see Install and download agent.