Let’s understand where all we can check and confirm is the exact site version numbers of Configuration Manager Current Branch. Which are the place in the Admin console you can check for the site version? And what is the difference between the version numbers in different places (well, yet to find out this)?
I have installed KB4567007 and fixed the post Stuck at Post Installation stuck issue with a restart. Now, the IT pros are confused why is it not updating the site version of Configuration Manager 2002?
Related Post – SCCM 2002 Known Issues Bugs Fixes | ConfigMgr
Version Number – Updates & Servicing Node
The SCCM Full Version = 5.00.8968.1031 as per the updates and Servicing node for this KB. However, there is no client version or client update for this KB.
- \Administration\Overview\Updates and Servicing
Version Number @ Admin Console
The version number – Site version = 5.00.8968.1000 after the installation of this hotfix for the ConfigMgr 2002 version. Obviously, there is no console update required for this KB4567007.
- Admin console –> About Configuration Manager
Site Version Number @ Site Configurations
The site version number shows at site configuration – the site is the same as the admin console about 5.00.8968.1000.
- \Administration\Overview\Site Configuration\Sites
Why? – Site Version Confusion
I think the KB article itself gives some hints about this site version confusion. As you can see below the only file version change is the SQL one. So, I assume that is why there is no change in the site version number.
But, I agree this doesn’t answer the question of why the site version (full version shows something different).
- SCCM Versions Numbers Build Client Console Updated List
- Version 2002 of Configuration Manager Installation Guide
- Possible Issues with SCCM 2012 to CB Current Branch Upgrade