M
M
mrkotovsk12021-10-05 12:28:41
remoteapp
mrkotovsk1, 2021-10-05 12:28:41

How do I get Windows to verify the authenticity of a self-signed certificate?

on the connection broker server, the rd web access service is also deployed, where a self-signed certificate was created using Windows, everything opens in the browser named connection broker-a / rdweb and remoteapp shortcuts are available.
But by adding to the Control Panel\All Control Panel Items\Remote Connections this error occurs on the desktops and RemoteApp applications, I
615c1ade9816f978499602.jpeg

tried manually on the client PC to add the certificate to the trusted ones - it did not help
On other resources, this topic is very vaguely covered

Answer the question

In order to leave comments, you need to log in

2 answer(s)
R
res2001, 2021-10-05
@mrkotovsk1

Try adding the certificate to Personal, Trusted People, or Trusted Device
In general, don't use a self-signed certificate.
Raise your CA. Generate a CA certificate, and a server certificate that will be signed by the CA certificate. On clients, install the CA certificate in the root trusted certification authorities and you will be happy.
You can use the built-in Certificate Authority in Windows Server, or use openssl.
Another option is to relax the client's certificate verification. I think somehow this should be done in Windows, perhaps through the registry or GPO. But I wouldn't do it.

A
Alexey Dmitriev, 2021-10-05
@SignFinder

Add it to Trusted Root Authorities\Trusted Root Certification Authorities for the Local Computer account.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question