Windows Hello appearing for users when using Azure AD - Say "Goodbye" to Windows Hello

 Given the current state of the world, we have been migrating many clients to a Cloud based solution - predominately 365 with Azure AD; situationally dependant.

A bug bear is Windows Hello - if you're using Azure AD without intune or endpoint then this annoying feature will try and enable itself on your workstations and it's a total pain.

So here's a quick registry fix to get rid of it - no need to edit the local policy (this is the same). Just apply the reg and say Goodbye to Windows Hello

-- copy the below contents into a text file and save as a .reg --

Windows Registry Editor Version 5.00

; Created by: Des

; Created on: 21/04/2021

 

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\PassportForWork]

"Enabled"=dword:0

"DisablePostLogonProvisioning"=dword:0

NET::ERR_SSL_OBSOLETE_VERSION when browsing an SSL site in Apache

It would appear that today is the day Chrome has stopped supporting older versions of TLS and if you're running any legacy sites you may receive this error when browsing them:

NET::ERR_SSL_OBSOLETE_VERSION

To resolve you need to enable TLS 1.2 in your Apache SSL conf file

Find the httpd-ssl.conf file in your Apache folder and look for the following line:

SSLProtocol -all +TLSv1 +SSLv3

Add +TLSv1.2 at the end so it reads as follows:

SSLProtocol -all +TLSv1 +SSLv3 +TLSv1.2

Restart the Apache server 

Whether you want the other protocols still present is up to you of course!

Web pages not loading correctly on Vigor 2862 Ln LTE when using ADSL (ping spikes too!)

It's been a strange week; we've had 2 broadband migrations with problems. The first was a circuit moving from a VDSL to VDSL; for whatever reason it got regraded to ADSL. When migration was complete a new 2862 Ln was installed and from there the trouble began.

The second was ADSL to ADSL - when migration completed a new router was also installed, another 2862Ln for LTE backup

Web pages weren't loading properly, connections intermittent and strange ping spikes on the local network. 

It would apper that the 2862Ln routers come with ADSL settings set to PPPoE and an encapsulation type of LLC/SNAP unlike their 2862 counterparts which are PPPoA and VC-MUX

The fix, change them to the correct settings! It's very easy to miss though when you're so used to the normal kit being right :(

Creality Ender (Ender3 Ender-3) bootloader showing up in device manager as usb2.0-serial

I recently tried to install a bootloader on my Creality Ender 3 1.1.4 board. I followed an all in one raspberry pi method and after flashing plugged it into my PC to update the firmware.

However, the system couldn't find any device drivers to talk to the printer - it just kept showing up as a USB2.0-serial device

Thankfully someone on reddit (https://www.reddit.com/r/3Dprinting/comments/93zah2/so_i_just_bricked_by_ender_3_through_a_firmware/ TrueShoba) had a link to the below package, which once installed allowed me to flash the new firmware to the system

https://www.th3dstudio.com/knowledge-base/creality-printer-drivers-all-models/

thank goodness! I now have a Marlin 2.0 Ender 3 to play with :)

System Center 2019 DPM Data Protection Manager Bare Metal and System State constantly inconsistent

Deployed a new DPM agent to a Server 2019 machine however it would not keep the system state or bare metal recovery consistent. 

Turns out, I forgot to install the Windows Backup feature! Installed, and everything started working immediately. A quick fix, but hopefully this helps you. Nice and short this time, to the point.

Outlook 2016 Office 365 O365 showing recipients name in the to field

Had a weird little problem where one of our clients name was appearing in the To field in all her folders in Outlook 2016/Office 365

Reset the views, didn't fix it - all very strange

Eventually found under "Change View" that a new 4th View had been created called "Show To". Changing it back from this to "company" immediately fixed the problem and the "Show To" view totally disappeared from the list

Client couldnt tell me how it happened, but that seemed to fix it!

Adding L2TP VPN access to SBS 2011 as well as PPTP

Out of the box, Server SBS 2011 isn't enabled for L2TP VPN access, but it does support it. All you need to make are a few changes to Routing and Remote Access:

1. Open Routing and Remote Access under Administrative Tools
2. Go to "Ports", right click it and go to "Properties"
3. In this window, find "WAN Miniport (L2TP)" - it will say 0 in the number of ports column
4. Select it and click "configure" - tick the "Remote Access connections (inbound only)" box and increase the maximum number of ports (to the number of connections you need)
5. Now right click on the server name (local) and select "Properties"

6. Go to the "Security" and tick "Allow custom IPsec policy for L2TP Connection"
7. Int he box below, enter a preshared key. You will need to give users connecting to the network this key
8. Click OK and restart RAS
9. You now need to forward port 1701 from your router to the server (you can leave 1723 in place for PPTP, as both will work)

And thats it - you should now have working remote VPN access to your server using L2TP