SCCM DB Missing Operating systems table

Kaan Akyuz 1 Reputation point
2020-12-14T15:32:36.627+00:00

Hi,

Following tables doesn't contain Windows 10 OS versions like 1809, 1909 etc. but contains 1709 and 1803 data.

Is this a WMI issues on client sites or something else ?

vSMS_WindowsServicingStates

vSMS_WindowsServicingLocalizedNames

Windows for business Windows Client for IT Pros User experience Other
Microsoft System Center Other
0 comments No comments
{count} votes

5 answers

Sort by: Most helpful
  1. XinGuo-MSFT 22,226 Reputation points
    2020-12-15T06:23:55.783+00:00

    Hi,

    Please try the following SQL query:

    SELECT A.name0,
           A.user_name0,
           A.client_version0,
           D.caption0,
           A.build01,
           A.osbranch01,
           B.NAME,
           B.state,
           C.value,
           C.localeid,
           D.installdate0,
           A.operating_system_name_and0
    FROM   v_r_system A
           LEFT OUTER JOIN vsms_windowsservicingstates B
                        ON B.build = A.build01
                           AND B.branch = A.osbranch01
           LEFT OUTER JOIN vsms_windowsservicinglocalizednames C
                        ON B.NAME = C.NAME
           LEFT OUTER JOIN v_gs_operating_system D
                        ON A.resourceid = D.resourceid
    WHERE  A.build01 LIKE '10.%' 
    
    
    select * from vsms_windowsservicinglocalizednames
    
    select * from vSMS_Win10Dashboard
    
    0 comments No comments

  2. Kaan Akyuz 1 Reputation point
    2020-12-15T07:51:01.32+00:00

    Hi,

    Thanks for your reply.

    Result is almost same mine.
    My point is some data missing like when i run following queries.

    select * from vSMS_WindowsServicingStates

    Windows10U5RTM 0 10.0.17134 2
    Windows10U4RTM 0 10.0.16299 2
    Windows10U4RTM 1 10.0.16299 2
    Windows10U3RTM 0 10.0.15063 3
    Windows10U3RTM 1 10.0.15063 3
    Windows10U2RTM 0 10.0.14393 3
    Windows10U2RTM 1 10.0.14393 3
    Windows10U1RTM 0 10.0.10586 4
    Windows10U1RTM 1 10.0.10586 4
    Windows10U0RTM 0 10.0.10240 4
    Windows10U0RTM 1 10.0.10240 4
    Windows10LTSB2016RTM 2 10.0.14393 2
    Windows10LTSB2015RTM 2 10.0.10240 2
    Windows10Insider 0 10.0.16353 1

    select * from vSMS_WindowsServicingLocalizedNames

    Windows10U0RTM 1507 1033
    Windows10U1RTM 1511 1033
    Windows10U2RTM 1607 1033
    Windows10U3RTM 1703 1033
    Windows10U4RTM 1709 1033
    Windows10U5RTM 1803 1033
    Windows10LTSB2015RTM 2015 LTSB 1033
    Windows10LTSB2016RTM 2016 LTSB 1033
    Windows10Insider Insider Preview 1033

    vSMS_Win10Dashboard

    10.0.14393 2 2 Windows10LTSB2016RTM
    10.0.16299 0 2 Windows10U4RTM
    10.0.17134 0 2 Windows10U5RTM
    10.0.17763 0 NULL Other
    10.0.17763 2 NULL Other
    10.0.18363 0 NULL Other

    0 comments No comments

  3. XinGuo-MSFT 22,226 Reputation points
    2020-12-15T08:34:44.327+00:00

    What's your SCCM version?

    Here are my results:

    48159-capture.png

    0 comments No comments

  4. Kaan Akyuz 1 Reputation point
    2020-12-15T12:14:44.96+00:00

    Configuration Manager 2006

    if you ask about hotfix is not installed.
    https://support.microsoft.com/help/4575789

    0 comments No comments

  5. XinGuo-MSFT 22,226 Reputation points
    2020-12-16T02:25:03.373+00:00

    Based on the current situation, we recommend you try to perform SCCM Configuration Manager site reset to recreate the tables.

    How to Perform SCCM Configuration Manager Site Reset

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.