Windows Server Essentials 2016 In-Place Upgrade

If anyone else is dumb enough like me to in-place upgrade their 2012 R2 Essentials install to 2016 Essentials, then there's some extra steps you'll need to take:

• After the first reboot, log in, try to open the Dashboard, then leave the login for 30-45 minutes. This should be long enough for .NET Framework to compile the necessary assemblies. Don't try anything else at this point. Reboot.
• Get the latest Cumulative Update installed by downloading it from the Windows Update Catalog. Most of the problems I encountered were due to way too many bugs shipped with the RTM build.
• C:\ProgramData\Microsoft\Windows Server\Logs needs Modify access for the NetworkService account
• You may need to reinstall the Essentials Connector for all clients, but especially for an On Premises Exchange Server. You'll also want to disable then enable the Exchange Server Integration.
• You'll need to make a backup of HKLM\SOFTWARE\Microsoft\Windows Server
• You'll then need to change the assemblies version from 6.3.0.0 to 10.0.0.0 under this key (i.e. look for Version=6.3.0.0 and change to Version=10.0.0.0)
• You'll need to restore the Disabled Tasks under Microsoft\Windows\Windows Server Essentials
• Backup Cleanup, Consistency Check, Macintosh Status Check and Save CEIP Data all have invalid Triggers and Actions
• You'll need to get these settings from a clean 2016 Essentials install

Set Up a Sophos Access Point on a Sophos Firewall in a Different Subnet

My first experience with a Sophos Access Point was a painful affair, as the Access Point (an AP55) was on a subnet sitting behind a separate router and the subnet’s DHCP server wasn’t the XG Firewall.

After way too much mucking around I finally came across the following article:
How to troubleshoot registration issues for the Sophos Access Point

The upshot was to add Option 234 to the DHCP scope, with Option 234 pointing to the IP address of the XG Firewall you want the Access Point to register with.

For completeness I also placed the Access Point onto the same subnet as the XG Firewall and it also failed to register with the XG Firewall, as the DHCP server for the subnet was a Windows server. After adding Option 234 to the DHCP scope the AP55 showed up on the XG Firewall.