End users can connect to a server and use remote desktops and published applications. For troubleshooting purposes, end users can reset remote desktops and published applications. Connect to a Remote Desktop or Published ApplicationTo connect to a remote desktop or published application, you must provide the name of a server and supply credentials for your user account. The connection procedure is slightly different for administrators and end users, so refer to the section that applies to your role. Trust a Self-Signed Root CertificateSometimes, when connecting to a remote desktop or published application for the first time, the browser might prompt you to accept the self-signed certificate that the remote machine uses. You must trust the certificate before you can connect to the remote desktop or published application. Use Unauthenticated Access to Connect to Published ApplicationsIf you have an Unauthenticated Access user account, you can log in to a server anonymously and connect to your published applications. The connection procedure is slightly different for administrators and end users, so refer to the section that applies to your role. Connect to a Server in Workspace ONE ModeAn administrator can enable Workspace ONE mode on a Connection Server instance. Setting the Time ZoneThe time zone that a remote desktop or published application uses is set to the time zone in your local system automatically. Allowing H.264 DecodingWhen you use a Chrome browser, you can allow H.264 decoding in the client for remote desktop and published application sessions. Log Out or DisconnectIf you disconnect from a remote desktop without logging out, applications in the remote desktop might remain open. You can also disconnect from a server and leave published applications running.