Forums on Intune, SCCM, and Windows 11

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!

SOLVED SCCM not showing correct version of operating system installed

  • Thread starter Thread starter jerkovm
  • Start date Start date
  • Replies Replies 8
  • Views Views 23K
Status
Not open for further replies.

jerkovm

Member
Messages
11
Reaction score
0
Points
1
I have been upgrading my systems to 20H2 from multiple versions. My issue is when I check the pc but doing resource explorer, it shows one version of windows installed but if I go to that pc it shows correct info by doing winvwer. Is there a way to force sccm to update collections to show correct information?
 
In resource explorer, under "Hardware" if you scroll to the last node under "Workstation Status" - is the "Last Hardware Scan(Client Local Time)" up to date?
Are you checking for OS ver under "Operating system" > "Version" in Resource Explorer?

Also, you first question point mentions two things - the resource explorer info and also
"way to force sccm to update collections"
Do you have a collection with a query rule based on the OS version - that is not adding these devices in?
How long has it been (on average, i.e. been a couple of days? not that should have to wait that long just curious)?
In resource explorer; if you check Hardware History instead of just hardware, what are the intervals like on the dates (may as well use Operating System node as the example), e.g. 2 days between them, daily, weekly etc. Just curious if the intervals seem long.

To be honest though a simple HW inv cycle should have taken care of this...
 
In resource explorer, under "Hardware" if you scroll to the last node under "Workstation Status" - is the "Last Hardware Scan(Client Local Time)" up to date?
Are you checking for OS ver under "Operating system" > "Version" in Resource Explorer?

Also, you first question point mentions two things - the resource explorer info and also
"way to force sccm to update collections"
Do you have a collection with a query rule based on the OS version - that is not adding these devices in?
How long has it been (on average, i.e. been a couple of days? not that should have to wait that long just curious)?
In resource explorer; if you check Hardware History instead of just hardware, what are the intervals like on the dates (may as well use Operating System node as the example), e.g. 2 days between them, daily, weekly etc. Just curious if the intervals seem long.

To be honest though a simple HW inv cycle should have taken care of this...
The date for the last hardware scan is 7-1-2021. I am checking OS under operating system > version in resource explorer. so the reason I mention resource explorer is just to let you know how I check the version. My main question is how to get sccm to show the correct Windows OS version. i do have a collection for each os version and these besides checking them from resource explorer also stay in the collection for the os version that is displaying in the resource explorer. most that I am trying to verify have been upgraded within the last 7 days. in the history, I see 4/21, 4/28, 5/12, 5/19, 7/1. Hope this helps
 
Hmmf... Do you use PowerShell / know how to use it with SCCM?

If so - if you know of a device where winver says it is 20h2 you can try running this command to see what comes back

Get-CmDevice -name "Hostname" | select -property Name, DeviceOsBuild

Should show the device and which OS it believes it is from SCCM side

If not let me know and I'll do a quick step by step (wont be many)
 
Hmmf... Do you use PowerShell / know how to use it with SCCM?

If so - if you know of a device where winver says it is 20h2 you can try running this command to see what comes back

Get-CmDevice -name "Hostname" | select -property Name, DeviceOsBuild

Should show the device and which OS it believes it is from SCCM side

If not let me know and I'll do a quick step by step (wont be many)
Hello,

That still shows the wrong version. i remoted in to this particular machine and ran winver and it shows 20H2
 
Run a FULL HW inventory and that will solve the problem.
 
Solution
Status
Not open for further replies.

Forum statistics

Threads
7,164
Messages
27,964
Members
18,256
Latest member
anonnnn

Trending content

Back
Top