Connecting to a Remote Host

The Trusted Zero Client can connect to any Windows, Linux, or macOS host with an Anyware agent installed, as well as Amazon WorkSpaces desktops. Connections can be made directly (client direct to host), or brokered through Anyware Manager, an Anyware Connection Manager, or Omnissa (VMware) Horizon using both PCoIP and Blast protocols.

Note: Support for Failover Gateways

The supports failover Security Gateways in a Connection Manager and Security Gateway deployment. If the primary gateway used to establish a PCoIP session fails unexpectedly, the session is automatically transferred to the next available gateway.

Session failover is only available if failover gateways are configured on the machines where the Connection Manager and/or Security Gateway are installed. No additional configuration is required on the HP Anyware Clients.

Instructions for configuring failover gateways is available in the topic "Configuring Failover Security Gateways" of the Connection Manager and Security Gateway Administrators' Guide.

Creating Your First Connection

Important: Connections are policy-controlled

The ability to create and modify connections may be limited or removed by your deployment administrators. If these views are not available, they have been preset on the Anyware Trust Center and you can skip to Connecting to a Session.

The first step is to create a connection between your Trusted Zero Client and your remote desktop. This connection is made either to your connection broker, for managed deployments, or directly to a remote host.

1. Launch the Trusted Zero Client.

2. If this is your first connection, the Trusted Zero Client will prompt you to create one:

   

   Click Add a new connection, and proceed to the next section.

Creating a New Connection

Important: Connections are policy-controlled

The ability to create and modify connections may be limited or removed by your deployment administrators. If these views are not available, they have been preset on the Anyware Trust Center and you can skip to Connecting to a Session.

Create a new connection by clicking + Add a new connection at the bottom of the Connect pane. You can add as many connections as you like.

1. In the Add New Connection pane, there are two fields to provide:

   

   • Host Address or Registration Code: Enter the address of the remote system you want to reach (you should have this information from your system administrator). This field accepts IP addresses, domain names, and registration codes, as in these examples:

     • An IP address: 123.456.789.012
     • A FQDN: remote-desktops.example.com
     • A registration code: a1b2c3!@#

     For Anyware connections using a connection broker (such as Anyware Manager or Leostream), this value will be the address (or FQDN) of the broker.

     Note: Amazon WorkSpaces registration codes

     If you are connecting to an Amazon WorkSpaces desktop, provide your WorkSpaces registration code in this field.

     Note: Omnissa Horizon connections via PCoIP or Blast

     To connect to a Omnissa Horizon broker, provide the address of the Horizon Connection Server in the Host Address or Registration Code field.

   • Connection Name (optional): If desired, provide a name for this connection. This can be anything; you will use this name to select this connection in future sessions. You can always change it later.

2. Click Add connection.

Once this is done, your connection will appear as a button in the desktop selection list.

Connecting to a Session

1. If you have created at least one connection, the Trusted Zero Client will now look something like this:

   

2. Click the name of the connection you want. Next, provide your username and password:

   

   Note: About authentication credentials

   For managed connections, the authentication screen and validation that happens here is provided by Anyware Manager or by your connection manager. The credentials are supplied to you by your system administrators, and are usually your corporate credentials.

   For direct connections where no broker is present, use the credentials for your user account on the remote machine.

3. If configured, you will see a Multi-Factor Authentication (MFA); the actual display shown will depend on your MFA provider and your IT policies. Follow the prompts provided in your interface.

   

4. Once your credentials are accepted:

   • If you have a single desktop available, your connection credentials will be used to automatically log into it and your session starts immediately.

   • If you have multiple desktops available, the shows you a list of desktops. Click the desktop you want to connect to.

     

     Tip: Managing desktops

     You can change the labels that appear in this list to make them easier to identify, and may be able to remotely restart them as well (if supported). See Managing Desktops for instructions.

Once you have selected your desktop, you will be connected to it and your remote session will begin. The first time you connect to a desktop, there may be a slight delay before the connection is active.

There may be a delay of a few seconds before you have control of your mouse and keyboard; this is normal.

Connecting to Amazon WorkSpaces

Amazon WorkSpaces connections use the same process described above. Provide your registration code in the Host Address or Registration Code field, and the Trusted Zero Client will recognize it as a WorkSpaces registration code and handle it appropriately.

Connecting to Omnissa Horizon

Omnissa Horizon connections use the same process described above. Provide the address of your Horizon Connection Server in the Host Address or Registration Code field, and the Trusted Zero Client will recognize it and handle it appropriately. By default, the connection will be made using the Blast protocol.