---
title: "System and Software Requirements"
slug: "qa-to-vdi-to-windows-system-software-requirements"
updated: 2026-10-09T18:52:06Z
published: 2026-10-09T18:52:06Z
canonical: "healthcare.rapididentity.com/qa-to-vdi-to-windows-system-software-requirements"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://healthcare.rapididentity.com/llms.txt
> Use this file to discover all available pages before exploring further.

# System and Software Requirements

## Operating System
* Windows 11
* Windows 10 Pro Builds 1607, 1703, 1709 (x86 or x64)
* Windows 10 IoT Enterprise

***

## Domains
The QwickACCESS (QA) client software can be installed on a system that is <u>not</u>  joined to a Windows domain, or on a system that is joined to a Windows domain. Domain-joined or not, you must specify which Windows domain(s) that QA should use. **This is a required setting and QwickACCESS will not work properly unless the correct domain or domains are specified.** 

In a single domain environment, you would only specify the name of the domain that contains the users that will use QA. 

In a multi-domain environment you would specify two or more domains that contain the users that will use QA. QA will display the specified domain names to the user in a drop-down list (which they can select) when registering their badge. 

:::(info) (ℹ️ Domain Configuration)
The order in which multiple domains are listed to the user can be modified in the [configuration tool](/v1/docs/qavw-general).
:::


***

## System Requirements
* Approximately 50 MB of free hard disk space
* .Net version 4.0 or higher
    * Note: This is only required if you are using the QwickACCESS Remote Desktop Connection.
* Java version 1.8 or higher (32-bit edition)
    :::(Warning)
    ⚠️ Only the 32-bit edition of Java is supported even when installing QwickACCESS on 64-bit systems.
    :::

* A supported proximity card reader (see below)

***

## Supported Remote Access Clients
* **Citrix:** See the [Citrix Support Matrix](/v1/docs/qavw-citrix-support-matrix) for details.
* **Microsoft:** Remote Desktop Protocol 7.1, 8.0, or 10.2
* **VMware:** Horizon Client version 4.0.1, 4.2, 4.3, 4.4, 4.5, 4.6, 4.6.1

***

## Supported Proximity Card Readers
* RFIDeas RDR-6082AKU
* RFIDeas RDR-7082AKU (not to be mixed with 7582 readers) - see WARNING
* RFIDeas RDR-7582AKU (not to be mixed with 7082 readers) - see WARNING
* RFIDeas RDR-80582-AKU Universal Prox readers
* RFIDeas RDR-60D2-AKU USB Dongle

:::(Warning) (⚠️ Mismatched Readers)
It's recommended to have the same type of reader across the organization, as readers will read the card data differently, making the system think that it is a new card that must be registered.

**Example:**
A user registers their badge on an endpoint that has a 7082 reader. If they move to another endpoint with a 7082 reader, they will badge in without issue.

If they move to a different endpoint with a 7582 reader and attempt to badge in, they will be prompted to register their card. If they re-register their card with the 7582 reader, the user can  badge-in on 7582 readers but will be prompted to register on a 7082 reader endpoint, and the cycle would continue.
:::