ComputerMan

 Yes, we are still doing the occasional P to V conversion from hardware Windows Server to Hyper-V VM! You can still use Mark Russinovich's PtoV converter to do this, Sysinternals Disk2VHD. After you have done the P-toV the hardware, create a new VM in Hyper-V using Generation 1 machines. When booting, you need to create a BCD / Boot partition. Boot into recovery mode using the same Windows Server ISO, and boot to the CD/DVD. Select Recover and Command Prompt. Then type: bootrec /fixmbr bootrec /fixboot bootrec /rebuildbcd After that, you can boot again to the C drive.

 Windows Server Servicing stack 10.0.17763.2170 rebooted our server automatically, no warnings. The process C:\Windows\system32\svchost.exe (xxxxx) has initiated the restart of computer xxxxx on behalf of user NT AUTHORITY\SYSTEM for the following reason: Operating System: Service pack (Planned)  Reason Code: 0x80020010  Shutdown Type: restart  Comment:  Thanks Microsoft. It wans't planned. More downtime caused by your automatic reboots.

If you enable Barracuda Cloud-to-Cloud backup, you might come across this error when trying to set it up: AADSTS7000112: Application '3450a114-871f-4057-b591-f0a8e3c50287'(Cloud-to-Cloud-Backup) is disabled. and if  you log into Azure AD and try the command: (Get-MsolServicePrincipal -AppPrincipalId 3450a114-871f-4057-b591-f0a8e3c50287).accountenabled you get the result $false. Then you can enable Barracuda Cloud-to-cloud Backup by typing: Get-MsolServicePrincipal -AppPrincipalId 3450a114-871f-4057-b591-f0a8e3c50287 | Set-MsolServicePrincipal -AccountEnabled $true