[German]Today a short collective post about remote support (Quick Assist) in Windows and Intune. As of April 21, 2022, a certificate for Quick Assist in Intune expired and there were certificate warnings. This should have been fixed by now. In addition, there appear to be issues with remote support in Windows when TLS 1.x is turned off. Here's a quick overview.
Quick Assist is the English-language name for the remote support included in Windows and in Intune. Microsoft has published the article https://support.microsoft.com/en-us/windows/solve-pc-problems-over-a-remote-connection-b077e31a-16f4-2529-1a47-21f6a9040bf3 on the topic. The Windows Quick Assist (Remote Assist) app lets people get or provide PC support over a remote connection.
Quick Assist certificate expired
It already came to my attention yesterday on Twitter – in the following tweet, Kevin Odom got in touch and asked if anyone else had received a warning about an expired certificate.
Several affected people came forward and confirmed this. Paul Winstanley also posted a corresponding observation on Twitter.
he InTune support team then opened a support case IT362654 at aka.ms/MEMSHD and later wrote that a fix had been rolled out, meaning they had issued a new certificate. Subsequent tweets reflect that.
If anyone was affected, it wasn't you. So Quick Assist should work again.
Quick Assist problems with TLS 1.0/1.1 disabled
The following tweet from blog reader Karl came to my attention on Twitter. Remote support doesn't work on Windows 11 either – although Microsoft claims that the problem is fixed.
There is only the error message that Quick Assist is not available as a service and to try later. Karl points out that remote support will no longer work if only Transport Layer Security protocol version 1.2 or higher is allowed for security reasons. TLS 1.0, after all, is considered insecure. Microsoft has published the article Solving the TLS 1.0 Problem, 2nd Edition on this security issue as of 4/21/2022. So if someone has problems with Quick Assist, check this point as well. By the way, Microsoft has not yet responded to the above tweets. Can anyone follow up on this.
Cookies helps to fund this blog: Cookie settings