Windows 10: How do I force the self-signed certificate generated by vmms.exe to use both the hostname...

I have a new install of hyper-v on windows 11 Enterprise. I am able to launch Hyper-V manager as a local administrator and connect to the server by selecting local computer. I can create a new hyper v guest but when I try to open the direct console I can't connect as the certificate presented only allows the FQDN and the hyper v manager seems to be attempting the connection using only the hostname. I have no idea how it got into this state. I have removed and readded the hyper-v feature several times and it is consistent.

:)

 

How to add self-signed certificate to my PC?

My PC is Windows 10 Pro x64 and I have Edge and Chrome browsers installed.

I installed my firewall's Certificate Authority into the windows certificate store by going to MMC, adding Certificates, and adding it to the Trusted Root CA. I now see my firewall root CA as (firewallCA).

Now I created a CNAME in my DNS to access my firewall as fw.example.com which only resolves internally. I then generated on my firewall a self-signed certificate. Once created, I downloaded the certificate and also added it to the MMC->Certificates.

I can now open IE or Edge and go to https://fw.example.com and not get a certificate error. However, if I use Chrome, I still get the error. I went to the Chrome advanced settings and see the firewallCA listed, but not the self-signed cert. I guess I have to add it manually, but I want it to apply to any user on this PC. How can I add the self-signed cert to Chrome for all users?

 

self signed certificate expired in domain controller, please call us

• the self signed certificate expired in domain controller, please call us