Error seen when attempting to open a web page that’s been secured by https with a certificate.
Your Connection isn’t private
Attackers might be trying to steal your information from {host-name} (for example, passwords , messages or credit cards)
Solution : ERR_CERT_WEAK_SIGNATURE_ALGORITHM
I had not seen this error for a while, and I was surprised I was seeing it now. It’s because the certificate that’s been used on the website is using SHA1 as its signature algorithm.
If you have purchased this certificate you will need to get it reissued, but chances are this is a self-issued certificate form Certificate Services. If that is the case, you need to update your certificate services form SHA1 to SHA256.
Error seen when attempting to open a web page that’s been secured by https with a certificate.
Your Connection isn’t private
Attackers might be trying to steal your information from {host-name} (for example, passwords , messages or credit cards).
Solution : ERR_CERT_COMMON_NAME_INVALID
This error confused me GREATLY because I generated that certificate, and I was pretty certain the common name was correct, so I double checked.
The truth is this error is VERY MISLEADING, the problem has nothing to do with the certificates Common Name (for the uninitiated, the Common Name or CN is a value within a certificate, that usually holds the ‘resolvable name’ of the website you are visiting i.e. on my certificate (above) you can see that’s www.petenetlive.com).
The certificate giving me the error in the picture above THERE NOTHING WRONG WITH THE COMMON NAME. The real reason that you are seeing this error is because there’s no entry in the Subject Alternative Name (SAN) value in the certificate. So I created a new certificate and copied that same value into both the common name and subject alternative name fields – like so.
If your certificate is publicly signed, then you will need to go back to the certificate vendor and have the certificate reissued with a subject alternative name. However, I issue these certificates internally from my own Certificate Services, so I just needed to add that like so.
Related Articles, References, Credits, or External Links
Whilst attempting to get a certificate from a Windows server running certificate services, I got the following error:
The request contains no certificate template information. 0x80094801 (-2146875391 CERTSRV_E_NO_CERT_TYPE) Denied by policy module 0x80094801, The request does not contain a certificate template extension or the Certificate Template request attribute.
Solution 0x800094801 Error
Well that’s a descriptive error, as this is a certificate request I’ve created on third party piece of hardware, I’m not surprised there’s no template information. The only way to specify which template you want to use for the certificate issued is to resubmit the command via command line.
Teams for Mac Spellcheck Not Working KB ID 0001842
Problem
I’m running Teams for Mac (Microsoft Teams Classic) and this has happened a couple of times now. My spelling is terrible, so I tend to just type furiously and then go back and fix my spelling mistakes. As with all ‘office based’ application it helpfully underlined all the typos in red, then USUALLY I can right click and correct them.
Each time it breaks I can see what has been misspelled but the right click menu does not appear, like so
Solution: Teams for Mac Spellcheck Not Working
The first time this happened I simply changed languages from English (US) to English (United Kingdom) and the problem went away. But it returned today.
I had to run the following command (Warning: This will drop all your Teams personal settings and you will need to re-authenticate). Firstly quit Teams if it’s still running, then execute the following command, (in Terminal)
If you have deployed an NPS Server on your network, there may be a time when you want to replace that server – if all its doing is NPS and its 2012 or newer I’d be tempted to simply in-place upgrade it, but some people are rigid in their beliefs that that is not a good idea. So in that case you need to migrate to a new server.
Solution : Migrate NPS Server
Locate NPS Server
Just in case you know you have an NPS server, but you don’t know what server it’s on, (or how many you have!) The simplest way to find out is to look in the RAS and IAS Servers group in AD.
You can use the following procedure on Server 2012 (and newer) If your source server is Server 2008 then you need to use the netsh method I’ll outline below.
Migrate NPS Server : Export NPS Settings PowerShell
Then simply copy that exported XML file to the new NPS server.
Migrate NPS Server : Import NPS Settings PowerShell
At this point I’ll assume that your target server is built, updated and domain joined. So we have three tasks, install NPS, authorise the NPS server in AD, then import the settings from the file you exported above. Note: There is no direct PowerShell command to authorise the new server in AD (at time of writing) So we need to use the netsh command to do that.
Then at this point I’d stop and disable NPS services on the old server and give everything a test. REMEMBER if you have RADIUS clients you may need to change the IP address that THEY are set to to the new NPS Server.
WARNING: If you are using authentication protocols that need certification like PEAP–MS-CHAP v2, PEAP–TLS, or EAP–TLS – AND your client are set to check the server’s identification (this is optional usually). Then check the new server has the correct certificates.
Migrate NPS Server (Server 2008)
On older OSs you don’t have the Export-NpsConfiguration and Import-NpsConfiguration PowerShell commandlets to use, so you have to use the netsh command instead.
This problem has jumped up through various iterations of Windows operating systems. You attempt to RDP to a machine; it connects but you simply get a black screen.
RDP Black Screen Solution
Over the years various ‘hotfixes’ were known to cause this, but before proceeding make sure both the machine you are connecting FROM and the machine you are connected TO are fully patched and updated.
Common troubleshooting dictates that your first step is to see if you can replicate the same problem from another machine, and if possible, from a different OS. below I’m attempting the same from my MacBook and getting the same result.
If something is happening on the target that is simply preventing the desktop from showing press CTRL+ALT+END, or CTRL+ALF+Fn+END (depending on your keyboard). Hopefully you should be able to now launch Task Manager > New > Run New Task > Explorer.exe > OK.
You can also try disabling ‘Persistent Bitmap caching’. On the Experience tab of you rdp dialog.
In the same dialog on the Display tab also try some low resolutions in case the target machine is confused about what to display on your remote session.
If it’s still not working the next most likely culprit is a display driver, Either update it or roll it back to a known good one, try this n the source and target machines. Note: if you see something like this – then the target machine may just need its VMware tools updating.
Finally try using a different RDP client for windows there’s the Remote Desktop Connection Manager, and on a mac theres the Microsoft Remote Desktop app.
Did none of these work for you? or if you have a better solution post it below and Ill update the post accordingly.
Related Articles, References, Credits, or External Links
