If you have an Unauthenticated Access user account, you can log in to a server anonymously and connect to your published applications.
Before you have end users access a published application with the Unauthenticated Access feature, test that you can connect to the published application from a client device. You might need to specify a server and supply credentials for your user account.
By default, users select the Log in anonymously using Unauthenticated Access setting from the Options menu and select a user account to log in anonymously. A Horizon administrator can configure group policy settings to preselect the Log in anonymously using Unauthenticated Access setting and log in users with a specific Unauthenticated Access user account.
Prerequisites
- Perform the administrative tasks described in Preparing Connection Server for Horizon Client.
- Set up Unauthenticated Access users on the Connection Server instance. For information, see "Providing Unauthenticated Access for Published Applications" in the Horizon Administration document.
- If you are outside the corporate network, verify that your client device is set up to use a VPN connection and turn on that connection.
- Verify that you have the fully qualified domain name (FQDN) of the server that provides access to the published application. Underscores (_) are not supported in server names. If the port is not 443, you also need the port number.
- Configure the certificate checking mode for the certificate presented by the server in Horizon Client. To determine which mode to use, see Setting the Certificate Checking Mode in Horizon Client.
- (Optional) Configure the Account to use for Unauthenticated Access and Log in anonymously using Unauthenticated Access group policy settings to change the default Unauthenticated Access behavior. For information, see Scripting Definition Settings for Client GPOs.