Supported Operating Systems
- Windows 11
- Windows 10 Pro Builds 1607, 1703, 1709 (x86 or x64)
- Windows 10 IoT Enterprise
Microsoft .Net Framework Requirement
- .Net version 4.0 or higher installed on the endpoint. This is only required if you are using the QwickACCESS Remote Desktop Connection.
Java Requirement
- Java version 1.8 or higher, 32-bit edition
- IMPORTANT: Only the 32-bit edition of Java is supported even when installing QwickACCESS on 64-bit systems.
Supported Remote Access Clients
- Citrix: See the 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
Minimum Hardware Requirements
- Approximately 50 MB of free hard disk space
- A supported proximity card reader (see below)
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
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.
