Everything, Everything

Xhaka hugs someone and gets a yellow card. Collins could have badly injured Iwobi following through on a strong tackle and gets nothing?!
10 hours, 48 minutes ago
Impressed by how quickly I can clone one SSD to another. Then realised I've saturated the SATA 2 connection and drives can go even faster.
14 days, 19 hours, 30 minutes ago
My @fitbit Charge 2 doesn't automatically show call notifications like my old Charge HR. I miss the old behaviour. https://t.co/MEB7tPq7qu
43 days, 9 hours, 22 minutes ago
Had to disable Windows Update service, reboot, and manually delete files to make WU work on Windows 10. I hope Server 2016 is more reliable.
44 days, 16 hours, 16 minutes ago
Configuring RDP Listener Certificates With Windows Server 2016
Saturday 22nd October, 2016 16:18
There are many things I like about Server 2016 (and Server 2012 R2), but the removal of the Remote Desktop Configuration Manager MMC snap-in that was really useful in Server 2008 (which used to run this web server for several years) makes it a lot more difficult to configure a different certificate for the RDP listener. Instead of a few clicks in a GUI you now have to find the SHA1 hash and use the command line (although you can do it by adding a registry key, but WMI is easier in my opinion).

I went with Method 1, Using Windows Management Instrumentation (WMI) script, to configure the use of my certificate on my shiny new VM running Server 2016. After identifying the SHA1 hash of the certificate, the following command can be used on newer versions of Windows including Server 2016 to replace the default self-signed certificate:

wmic /namespace:\\root\cimv2\TerminalServices PATH Win32_TSGeneralSetting Set SSLCertificateSHA1Hash="THUMBPRINT"

Not that you'll see the certificate, as I've locked down access to RDP to a handful of trusted IP addresses.
© Robert Nicholls 2002-2017
The views and opinions expressed on this site do not represent the views of my employer.