If you use the baseline media for version 1606 from the October 2016 release, the independent prerequisite check evaluates the site for upgrade to both the Current Branch and the Long-Term Servicing Branch (LTSB) of System Center Configuration Manage.
Because some features are not supported by the LTSB, you might see entries in the If you plan to upgrade to the Current Branch, errors for the LTSB edition can be safely ignored.
Disable database replication before you: Reconfigure software update points that use NLBs: Configuration Manager cannot upgrade a site that uses a Network Load Balancing (NLB) cluster to host software update points.
We had to role back the service pack to get reporting to work. Update: Also checked SMS_Installed Executable in hardware inventory classes, restarted smsexec, forced hardware inventory cycle and within a few hours I had full sotware inventories populating!
My clients are reading the Inventory info as this log entry proves: Collection: Namespace = ; Query = SELECT __CLASS, __PATH, __RELPATH, ARPDisplay Name, Channel Code, Channel ID, CM_DSLID, Evidence Source, Install Date, Install Directory Validation, Installed Location, Install Source, Install Type, Language, Local Package, MPC, Os Component, Package Code, Product ID, Product Name, Product Version, Publisher, Registered User, Service Pack, Software Code, Software Properties Hash, Software Properties Hash Ex, Uninstall String, Upgrade Code, Version Major, Version Minor FROM SMS_Installed Software; Timeout = 600 secs.
They only apply if you plan to upgrade to the LTSB.
Later, when you run Configuration Manager Setup to do the upgrade, the prerequisite check will run again and evaluate your site based on the branch of System Center Configuration Manager you choose to install (Current Branch, or LTSB).