Improve Client Upgrade Mechanism
There is SCCM CB 1806 (5.0.8692.1509) with the update "kb4462978" in the console installed.
When using automatic upgrade and package deployment to provide CM client version upgrades,
From the distribution point, although "client.msi" can be acquired, if "configmgr 1806-client-kb4462978-x64.msp" can not be acquired for some reason, a scenario occurs that results in "5.00.8698.1008" version did.
If the MSP file can not be obtained, CM client version upgrade is expected to fail, but the result is not "5.00.869. 1509" but the "5. 08. 692. 1008" version.
Success itself is a problem. The administrator misunderstands that the version upgrade of the CM client by the target version is successful.
As a workaround, for example, it can be avoided by including "configmgr 1806-client-kb4462978-x64.msp" in "client.msi".
If it is a version other than the purpose, we will ask for functional improvements that make it fail.