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
Select the VM configuration based on the workloads that the agent runs. Use the base minimums for agent workloads that do not include Profiling or Data Quality rules. If the agent runs Profiling or Data Quality rules, use the higher workload-specific minimums.
| Requirement | Base agent minimum | Profiling and Data Quality minimum |
|---|---|---|
| Windows Version | Windows Server 2022 | Windows Server 2022 |
| vCPU | 8 | 16 |
| RAM | 32 GB | 64 GB |
| Storage | 128 GB OS disk | 500 GB |
| Nested Virtualization | Required | Required |
Step 1: Connect to the VM and open PowerShell as Administrator
Connect to your VM using Remote Desktop (RDP). Once connected:
- Select Start.
- Search for PowerShell.
- Open the context menu for Windows PowerShell and select Run as administrator.
Step 2: Install WSL2 and Ubuntu
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
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
For the base agent configuration, WSL2 receives sufficient resources by default on a VM with 32 GB RAM and 8 vCPU. No .wslconfig file is required. If the agent runs Profiling or Data Quality rules, provision the VM according to the higher workload-specific minimums in Minimum VM specifications.
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. This preflight requirement is separate from the 500 GB storage minimum for Profiling and Data Quality rules in Minimum VM specifications.
df -h /
The Avail column must show 64 GB or more.
Step 7: Download discli inside Ubuntu
wget https://cdn.cloud.precisely.com/agent-cli/discli
chmod +x ./discli
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.