Client

With 2X ApplicationServer you can manage the 2X Client settings for all the users on the network that connect to any server currently in the Farm. By adding 2X Client Policies you can group your users using different policies and push different 2X Client settings and options to the users depending on the policy.

This is only available for 2X Clients installed on Windows (including Windows CE and XP Embedded).

To add a new policy, click on ‘Add...’ from the 2X Client Management tab.

Start by giving the new policy a name in the ‘Policy’ field.

If you want to use LDAP to add users and groups to the policy, check ‘Use LDAP mode when adding Users & Groups.

Click on ‘Add...’ to add users or groups to the 2X Client Policy. Once all the users have been added, you can configure the ‘Connection Properties’ and ‘Options’ that will be pushed to the users’ 2X Client.

Please refer to the 2XClient For Windows manual for more information about the options available on the 2X Client.

2X ThinClientOS can be distributed to thin clients on the network, using 2X ApplicationServer.

Thin clients are able to connect through a 2X Secure Client Gateway to download and install 2X ThinClientOS over PXE. Make sure that PXE booting is enabled on the 2X Secure Client Gateway.

Please refer to the ‘Network’ section for more information on how to enable PXE booting for thin clients.

Thin Client Installer must have at least one (1) 2XOS added to its list for it to be able to make the OS available to thin clients.

To add an OS click on ‘Manage 2XOS...’button.  

Note:  2X ApplicationServer supports 2XOS v6.3 and above.

From here you can add different versions of 2XOS by clicking on ‘Add...’.

Browse for the 2XOS ZIP file (which can be downloaded from the 2X website) and allow the application to add the OS to the list of thin client operating system.

The first OS that is added will be considered to be the default OS, but as you add more to the server, the default OS can be changed by selecting the OS and clicking on ‘Set Default’.

A filter can be used to allow or deny thin clients to boot with 2X ApplicationServer. Select whether to allow or deny connections from the ‘Action’ option.

Enter a ‘Filter Name’ so the filter can be easily recognizable.

Enter the ‘MAC address’ of the thin client(s) you want to allow or deny.

A wildcard can be used when entering a MAC address.
i.e.  If you enter “AF-4B-24-??-??” the filter will consider all the thin clients that have a MAC address starting with AF-4B-24.

The default 2XOS is select in the ‘Operating System’ option but you can change it to any 2XOS added to 2X ApplicationServer.

Select the correct input devices to be used with the filter. These settings are pushed to the thin client so the user does not have to worry about setting the mouse or keyboard layout.

ACPI Auto On: This option enables the auto configuration of your device using the data integrated in the system.

ACPI Always On: This option enables ACPI regardless of any configurations present on the device.

ACPI Compatibility (Do Not Manage Interrupts): This option enables the hardware using the data provided by the motherboard but uses baseline defaults to configure them for use.

ACPI Compatibility (Balance Interrupts): This option enables the hardware using the data provided by the motherboard together with what was detected by the OS drivers.

ACPI OFF: Disable the ACPI feature if your motherboard does not support a correct ACPI implementation due to incompatibility with the Linux Operating System. Baseline defaults will be used instead using legacy standard initialization.

‘Legacy Linux Loader (LILO)’ should be enabled if you thin client does not support the GRUB boot loader.

Enable ‘Monitor Probing’ to automatically detect the display resolution.