Sometimes, 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.
Chrome gives you the option to trust the self-signed certificate permanently. If you do not trust the certificate permanently, you must verify the certificate every time you restart your browser.
- If the browser presents an untrusted certificate warning, or a warning appears stating that your connection is not private, examine the certificate to verify that it matches the certificate that your company uses.
You might need to contact your system administrator for assistance. For example, in Chrome, you might use the following procedure.
- Click the lock icon in the address bar.
- Click the Certificate information link.
- Verify that the certificate matches the certificate that your company uses.
You might need to contact your system administrator for assistance.
- Accept the security certificate.
In Chrome, you can click the Advanced link on the browser page, and click Proceed to server-name (unsafe).
The remote desktop or published application starts.