All Axel terminals support ICA/HDX (Xenapp)

The key question is which Citrix Infrastructure are supported.

Citrix offers the following types of connection :
  • TCP/IP: now considered obsolete, based on UDP,
  • TCP/IP + HTTP: a method that uses XML port 80 of a Citrix server (for MetaFrame, Presentation Server and XenApp)
  • WEB Interface:  method which used HTTP/HTTPS and provides support for MetaFrame, Presentation Server, XenApp and  XenDesktop
  • StoreFront: similar to  WEB Interface but also supports VDI-in-a-Box.

AX3000 M80 and M85 support all the above.
AX3000 M70 et M75 only support 'TCP/IP' et 'TCP/IP + HTTP'.

We select the functions and features that are applicable to our product and thin clients, so we cannot claim to be fully compatible with any specific versions of ICA, but we endeavor to keep the client fully up to date.

For example our current client (March 2014) connects to Citrix version7.5 (including Storefront)

The M8x terminal does not have a full browser, but has specific http(s) support to connect to WI or Storefront

WEB Interface
A PNAgent website is created on the Citrix server and the terminal is simply pointed at this website.
The terminal automatically appends the server name/IP address with the default path to find the config.xml file ('/Citrix/PnAgent/config.xml', though this can be overwriten if a non default path is used.)

For example – for non default location :
https://mycitrix.domain.com/Citrix/MonDossier/Config.xml

StoreFront
With the 1236d firmware (or later), the StoreFront connection is supported. Only the server URL is needed:
https://mycitrix.domain.com

With a former firmware, this is very similar to WEB Interface with the additional feature that the client can't automatically locate the StoreFront name. So the full path must be entered. For example if the storefront is called "MyStoreFront", the URL to enter will be :
https://mycitrix.domaine.com/Citrix/PNAgent/MyStoreFront/Config.xml

Citrix session
A Citrix session is established to either a server or published application.
Up to 6 sessions can be defined.

Citrix Applications Desktop
This allows the thin client to authenticate against a Citrix server (WEBInterface or StoreFront) and to retrieve the icons for published applications. These icons are displayed on the terminal’s desktop over a secure connection.
When an icon is clicked a Citrix connection is established  to the application, either creating a new session or an existing session depending on the whether the second application is on the same server as the first application.

Note: these two connection types can coexist.

Microsoft servers allow the redirection of certain terminal resources (printers, USB, audio, smart cards, etc). Once redirected the resource is only available to the user of the thin client.

The server contains several drivers for generic classes of peripherals. You cannot add other drivers (Exception: see “other” below)

Note: By default all redirection is disabled. The administrator can specify in the set-up which resources are redirected.

Printer (serial, parallel , USB and network)
Redirecting a printer simply requires that the Microsoft driver for this printer is installed on the server. Just specify the name of this driver at the set up of the terminal.

Smart card reader
The reader must be PC/SC CCID compliant .

Storage devices ( USB flash drive , hard disk , CD / DVD ... )
A storage device can be redirected providing the filesystem is
- FAT ( 12, 16 or 32)
- ISO9660

Audio
A USB audio device must be used (including USB to phono convertors) .
Audio (recording and playback ) is supported by the models 80 and 85 80WMS and Windows 2008R2 server or higher.

COM ports
Serial ports ( AUX1/AUX2 ) Can be redirected to the Microsoft server. They are then seen as standard COM ports . (USB to serial converters are supported

Other
Other devices (webcams, scanners, smartphones, etc) are supported by 'USB port forwarding'. With this method the thin client maps the USB device to a user installed driver on the Microsoft server.
USB redirection is supported by the models 80, 85 and 80WMS.
For RDS/TSE, a W2012R2 server is required.
For Citrix, XenDesktop is required (not supported with XenApp).

Axel thin clients support the following types of printers:
 - Serial and parallel,
 -  USB
 -  Network: defined by their IP address and TCP port (default 9100).

There are two types of configuration, applicable to all printer types:
   - The printer is redirected within the session (TSE/RDS or Citrix)
   - The thin client acts as a network print server (independent to any sessions)

1 - Redirection within the Session (TSE/RDS or Citrix)

The redirected printer is private to the user and is automatically created when the session is established and removed when the session is closed.

To configure a redirected printer (for example USB):
Enter the set-up and go to [Configuration]-[Ports]-[Logical Ports USB]-[USB1]
Enable  'Redirection RDP/ICA'  and under "Printer Settings" :
 • Printer Name: enter name of the printer
 • Printer  driver: enter name of the printer driver.
   Note: The driver must be installed on the server - and the spelling in the terminals setup of the driver name must be exact.
 • Time_out value (sec): This parameter represents the time after which a printer error (no paper, printer busy) is sent to the server.
 • Cache printing options: Various printer settings can be saved locally on the terminal and sent to the server if required (passwords, default printer settings etc)
 
2 - Using the Thin Client as a Printer Server

In this case the printer is available to all network users as soon as the terminal is powered on.
 
The printer entry must be created on the Microsoft server using the "Add printer wizard".

To configure the terminal (for example with a USB Printer):
Enter the set-up and go to [Configuration]-[Ports]-[Logical Ports USB]-[USB1]
Service = set to LPD.
Port Name = enter name for printer

On the Microsoft server create an 'LPR Port'  which will require the IP address/DNS name of the thin client and the "Port Name"  as entered in the terminal as above

1 - The screen stays black saying  ' Connecting to…' for 20 seconds, then the session closes.
This indicates that the IP address of the Citrix server is unreachable.
Check the IP address or routing tables in the thin client.
 
2 - Citrix session closes immediately
Possibly the TCP port is not available on the Citrix server side (firewall issue using HTTP as opposed HTTPS... ).

After log-off, the RDS or Citrix session does not close (a blue screen is displayed)

Explanation:
The session is not closed by the server because there is a process still running, and the process prevent the session from closing
 
Solution:
The first step is to identify the process that does not terminal with the 'task manager'.
This process must be added to the list of processes that Windows can ' kill ' if necessary.
This list is accessible via the registry. If the process is called 'myprocess.exe', add a REG_DWORD (value 0) called 'myprocess.exe' to [HKEY_LOCAL_MACHINE]-[System]-[CurrentControlSet]-[Control]-[Terminal Server]-[SysProcs].

Explanation:
The terminal intercepts certain key combinations for its own local operation (eg <Ctrl> <Alt> <Esc> to enter the set-up).
Common key combinations such as <Alt><F1> to <Alt><F6> are used to change sessions. This is why <Alt><F4> does not work in the session, as it is used to hotkey to session 4.

Solution:
Change the session "introducer key"
Enter the set-up and go to [Configuration]-[Terminal]-[Local Desktop] and choose a different value for the introducer. For example change to "Cntl" - than <Cntl><F4> will change session, leaving <Alt><F4> for Windows to process