SCCM | Intune | Windows 365 | Windows 11 Forums

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

PENDING Client mismatch - Primary Site server vs Endpoints

blueWaterbaboon

New Member
Messages
2
Solutions
1
Reaction score
0
Points
1
Is this normal behavior for SCCM upgrades? I notice my SCCM Priamary site servers show client agent version 5.00.9128.1007, while all the other clients are getting updated to 5.00.9128.1030. Should this just sit and marinate for a while to complete? Upgrade was completed yesterday afternoon. We did the 2403 upgrade, then shortly after maybe an hour or so, we installed the KB28204160 Hotfix Rollup. Been almost 24 hours since, but the primary site server agent hasn't updated. Is there a way to get it updated manually on the primary site server somehow? One would think the primary site server would have been the first agent to get updated during the install and post-install tasks. And I didn't get any errors during the install and post install steps of the upgrade or the KB hot fix install.
Thanks!

1733854994560.png

1733855049718.png

Here below, I do see it's 'In Progress' to get updated from the Production client deployment.
1733855063531.png
 
Solution
Is this normal behavior for SCCM upgrades? I notice my SCCM Priamary site servers show client agent version 5.00.9128.1007, while all the other clients are getting updated to 5.00.9128.1030. Should this just sit and marinate for a while to complete? Upgrade was completed yesterday afternoon. We did the 2403 upgrade, then shortly after maybe an hour or so, we installed the KB28204160 Hotfix Rollup. Been almost 24 hours since, but the primary site server agent hasn't updated. Is there a way to get it updated manually on the primary site server somehow? One would think the primary site server would have been the first agent to get updated during the install and post-install tasks. And I didn't get any errors during the install and post...
Is this normal behavior for SCCM upgrades? I notice my SCCM Priamary site servers show client agent version 5.00.9128.1007, while all the other clients are getting updated to 5.00.9128.1030. Should this just sit and marinate for a while to complete? Upgrade was completed yesterday afternoon. We did the 2403 upgrade, then shortly after maybe an hour or so, we installed the KB28204160 Hotfix Rollup. Been almost 24 hours since, but the primary site server agent hasn't updated. Is there a way to get it updated manually on the primary site server somehow? One would think the primary site server would have been the first agent to get updated during the install and post-install tasks. And I didn't get any errors during the install and post install steps of the upgrade or the KB hot fix install.
Thanks!

View attachment 6795

View attachment 6796

Here below, I do see it's 'In Progress' to get updated from the Production client deployment.
View attachment 6797
Seems to be a latency issue. It eventually updated and is now matching the KB patch level. Just took its sweet time. For anyone else wondering. One would think the Primary Site server would have been the first to get updated w/the client agent. ‍♂️
 
Solution
Back
Top