OPERATIONAL DEFECT DATABASE
...
...
After performing an in-place upgrade of the server hosting the Veeam Backup Enterprise Manager database from Server 2012 or 2012 R2 to Server 2016 or 2019, no connection can be made to the Veeam Backup Enterprise Manager console.
After an in-place upgrade to Microsoft Windows Server 2016 or Server 2019, the Netlogon service may not start due to the "Startup type" being set to "Manual" instead of "Automatic". You can find more about the issue here: Microsoft Article: Netlogon service doesn't keep settings after an in-place upgrade to Windows Server 2016 or Windows Server 2019
According to the Microsoft Article: This issue can be avoided by letting the setup process install the latest updates during the in-place upgrade. If the issue already occurs, to resolve this problem, change the Netlogon service Startup type to Automatic. To do this, follow these steps: Click Start, type services.msc in the Start Search box, and then click Services Desktop app. Locate and double-click Netlogon, and then click Automatic in the Startup type box. Click OK, and then start the Netlogon service. Although this action doesn't require a restart, we recommend that you restart the computer to make sure that all services that depend on Netlogon are started and correctly registered on the Network.
Click on a version to see all relevant bugs
Veeam Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
