Tried to register for the forums and didn’t receive any emails (Hotmail, which is known to have such problems). Anyway, on the latest WSEE I note one new minor issue immediately after install & reboot:

• Event Viewer | Server Essentials | 1281 | Warning Alert: Restart is raised at SERVER. <Title> The server was restarted. <Description> The server was unexpectedly restarted.. <AdditionalInfo> .
  • Dashboard | Health Monitoring | This alert is either removed automatically after 24 hours, or it is removed when you enter a reason for the restart of the server when you log on.
    • Comments | It most definitely did not restart. I had previously configured the system to not prompt for a reason at logoff. The relevant Group Policy Object remains Disabled. Deleting the alert will cause it to repopulate on next Health Monitoring poll. 24 hours hasn’t passed since installation.

And two that had apparently escaped my notice for some time:

• EventViewer | User Device Registration | 307 | Automatic registration failed. Failed to lookup the registration service information from Active Directory. Exit code: Unknown HResult Error code: 0x801c001d. See http://go.microsoft.com/fwlink/?LinkId=623042
• Event Viewer | User Device Registration | 304 | Automatic registration failed at join phase.
  Exit code: Unknown HResult Error code: 0x801c001d
  Server error:
  Tenant type: undefined
  Registration type: undefined
  Debug Output:
  joinMode: Join
  drsInstance: undefined
  registrationType: undefined
  tenantType: undefined
  tenantId: undefined
  configLocation: undefined
  errorPhase: discover
  adalCorrelationId: undefined
  adalLog:
  undefined
  adalResponseCode: 0x0
  • Comments: I have no domain-joined devices. I have no Entrata configurations. I’m not sure why it’s trying to do this at all.

In unrelated news, for a few weeks I’d seen ConsistencyError popping up in Event Viewer. Running Client Backup Repair and Backup Cleanup today resulted in the last 5 years of retained backups going Incomplete, with only a specific smaller secondary drive from a Client Computer now marked Unsuccessful. No great loss, just thought it was interesting and that the world of home server admins might commiserate in pouring one out for the ruined data. At least there’s now more storage on my backup drive XD