Make ConfigMgr upgrade process resilient
As of now when an enterprise thinks of upgrade, we have only one thing to do before (TestDBUpgrade). This makes sure if the DB is upgradable. But what if the Upgrade fails at the next step (Copying files). We don't have an option to again run the upgrade only from that step and running from beginning will not work as DB is already upgraded it will fail to find some objects. If this is a CAS site this means you have to again go back to a previous version and recover it and make sure the sites in the hierarchy come out of the DRS issues which is a big task alone. So the ask is to either make the upgrade to continue from the steps that it failed after the DB upgrade or to create a tool which can verify the whole site for an upgrade success before we can actually do it.
Updating status to completed. This was addressed in SCCM 1606 production build, released yesterday