Connect to Published Applications Using Unauthenticated Access

You can connect to published applications using an unauthenticated access account with Omnissa Horizon Client. The connection procedure is slightly different for administrators and end users, so refer to the section that applies to your role.

Procedure for End Users

Before you begin, get the following information from your administrator:

• Instructions about whether to turn on a VPN (virtual private network) connection.
• Name of the server on which you have unauthenticated access to remote applications.
• If the port is not 443, the port number to use for connecting to the server.
• An Unauthenticated Access user account to use for logging in anonymously, if necessary.
• Instructions about whether to select Unauthenticated Access in Horizon Client.

If your administrator instructs you to configure the certificate checking mode, see Setting the Certificate Checking Mode in Horizon Client.

1. If a VPN connection is required, turn on the VPN.

2. Search the applications for Horizon Client, and double-click the icon.

3. In the Horizon Client home screen, select File > Unauthenticated Access from the menu bar, if it is not already selected.

4. Connect to the Omnissa Horizon Connection Server that is configured for unauthenticated access.

   Option	Action
   Connect to a new server	Double-click the + Add Server button, or click New Server on the menu bar, enter the name of a server, and click Connect.
   Connect to an existing server	Double-click the server icon, or right-click the server icon and select Connect.

   You might see a message that you must confirm before the login dialog box appears.

5. In the Server Login dialog box, specify the unauthenticated access account to use.

   1. Select a user account from the drop-down menu of existing unauthenticated access accounts.

      The default user account has (default) displayed next to it.

   2. (Optional) Click Always use this account if you want to bypass the Server Login dialog box the next time you connect to the server.

   3. Click OK. The application selector window appears and displays the published applications that the unauthenticated access account is authorized to use.

   Note: If you selected the Always use this account option during a previous unauthenticated access login session, you are not prompted for the account to use for the current unauthenticated access session. To deselect this option, right-click the icon for the server in the Horizon Client home screen, and select Wipe Unauthenticated Account (<saved account name>) from the context menu.

6. To start an application, double-click the application icon.

   The application window appears.

   Note: If Horizon Client fails to connect to the remote desktop or published application through the Omnissa Horizon Blast protocol, a detailed error message is displayed on the user interface. An administrator can use the error message along with client log files to troubleshoot Horizon Blast connection failures.

7. Exit the application after you are done using it.

   The Disconnect from Session dialog box appears asking if you want to disconnect from the server.

If the session timeout specified by an administrator is reached, the session is automatically disconnected from the server.

Procedure for Administrators

Before you have end users access their published applications using unauthenticated access, test that you can connect to the published applications from a client device using an unauthenticated access user account.

First, verify that your unauthenticated access users are created in Omnissa Horizon Console. If the default unauthenticated user is the only unauthenticated access user, the Horizon Client connects to the Horizon Connection Server with the default user.

1. If a VPN connection is required, turn on the VPN.

2. Search the applications for Horizon Client, and double-click the icon.

3. In the Horizon Client home screen, select File > Unauthenticated Access from the menu bar, if it is not already selected.

4. Connect to the Horizon Connection Server that is configured for unauthenticated access.

   Option	Action
   Connect to a new server	Double-click the + Add Server button, or click New Server on the menu bar, enter the name of a server, and click Connect.
   Connect to an existing server	Double-click the server icon, or right-click the server icon and select Connect.

   You might see a message that you must confirm before the login dialog box appears.

5. In the Server Login dialog box, specify the unauthenticated access account to use.

   1. Select a user account from the drop-down menu of existing unauthenticated access accounts.

      The default user account has (default) displayed next to it.

   2. (Optional) Click Always use this account if you want to bypass the Server Login dialog box the next time you connect to the server.

   3. Click OK. The application selector window appears and displays the published applications that the unauthenticated access account is authorized to use.

   Note: If you selected the Always use this account option during a previous unauthenticated access login session, you are not prompted for the account to use for the current unauthenticated access session. To deselect this option, right-click the icon for the server in the Horizon Client home screen, and select Wipe Unauthenticated Account (<saved account name>) from the context menu.

6. To start an application, double-click the application icon.

   The application window appears.

   Note: If Horizon Client fails to connect to the remote desktop or published application through the Horizon Blast protocol, a detailed error message is displayed on the user interface. For more information on Horizon Blast connection failure errors, see Knowledge Base article 91013.

   The client log files include a tag called Blast_Connect_Failure_Alert on lines that contain specific error information about Horizon Blast connection failures. See Collect Horizon Client Log Information.

7. Exit the application after you are done using it.

   The Disconnect from Session dialog box appears asking if you want to disconnect from the server.

If the session timeout specified by an administrator is reached, the session is automatically disconnected from the server.