Requirements
  • 04 Mar 2024
  • 2 Minutes to read
  • Contributors
  • Dark
    Light
  • PDF

Requirements

  • Dark
    Light
  • PDF

Article summary

Before deploying QwickAccess for IGEL version 1.3.0 to your organization, please ensure your environment meets or exceeds the minimum hardware and software requirements listed below.

IGEL Endpoints

QwickAccess for IGEL version 1.3.0 supports endpoints running IGEL OS version 11.09.100 and above, but not version 12, along with a version of IGEL Universal Management Suite (UMS) that is compatible with your chosen IGEL OS version, and a UMS Client version that is compatible with IGEL UMS. The IGEL Enterprise Management Pack is not required.

RFID Readers

QwickAccess for IGEL only supports RFIDeas readers such as WaveID Solo or WaveID Plus readers. The form factor of the reader doesn’t matter, but the reader will need a USB connector (not virtual COM) that is compatible with your IGEL endpoint. Also, since QwickAccess for IGEL doesn’t use the optional keystroking feature of a reader, we suggest buying readers without the keystroking feature because they may be less expensive.

Following are a list of readers that are known to work with QwickAccess for IGEL and also cover a very large number of badge technologies. This list is not exhaustive, however.

RFIDeas WaveID Solo: RDR-8082-AKU
RFIDeas WaveID Plus: RDR-80582-AKU

RFID Badges

You will need an appropriate number of RFID badges (or other RFID devices such as cards, key fobs, wristbands, etc.) which will work with your chosen RFID reader. Please contact RFIDeas if you help with this.

ExactAccess* Server

QwickAccess for IGEL requires the services of ExactAccess Server, specifically the ProxCard Server Service and Remote Authentication Service. Please see the system requirements for ExactAccess Server.

* ExactAccess

ExactAccess is the Enterprise Single Sign-On (ESSO) solution offered by Identity Automation which can be deployed on its own or in conjunction with QwickAccess for IGEL

Citrix Workspace app and Citrix VDI*

Since the QwickAccess for IGEL application leverages the version of Citrix Workspace app that comes preinstalled on IGEL endpoints and doesn’t directly interface with Citrix VDI, QwickAccess for IGEL automatically supports what ever version of Citrix VDI that is supported by Citrix Workspace app. Furthermore, Citrix specifies that the Citrix Workspace app is compatible with all supported versions of Citrix products. This means that if your version of Citrix VDI is supported by Citrix, then it is supported by QwickAccess for IGEL.

* Citrix VDI

In this document the term, “Citrix VDI” refers to Citrix Virtual Apps and Desktops, Citrix DaaS, and all related Citrix infrastructure.

(Optional) Epic Hyperdrive*

If your organization hosts Epic Hyperdrive on Citrix and publishes it to your IGEL endpoints, QwickAccess for IGEL can provide secure badge workflows for this configuration. This configuration requires that the EpicAuth for Hyperdrive Plugin* be installed on your Citrix servers, and QwickAccess for IGEL must be configured to support shared Hyperdrive sessions.

* Hyperdrive

Hyperdrive is an Electronic Medical Record (EMR) or Electronic Health Record (EHR) application provided by Epic Systems.

* EpicAuth for Hyperdrive Plugin

The EpicAuth for Hyperdrive Plugin is offered by Identity Automation and provides enhanced authentication workflows for Epic Hyperdrive.


Was this article helpful?