Monitroing Windows 10 OS Upgrades in Configuration Manager

jaybird283 561 Reputation points
2021-04-06T17:32:26.64+00:00

Hi, i am a bit new to SCCM/MCM and have been using it to push out In-Place OS upgrade task sequences. It's working darn near flawlessly. The only issue i have is i can't figure out a good way of monitoring the progress and was hoping for some pointers.

I can go into the monitoring section of the console and see my deployments and various Message ID's and can click on those for more information on the steps that have been performed so far. but the issue i am seeing is that our old client management tool is reporting the machines as being upgraded LONG before the SCCM/MCM console is. It seems to take a extremely long time for them to me marked as "Success". i have also been trying to look at the operating system build number column but it's also taking a long time to update.

So i guess i have two questions. should i shorten the hardware inventory to report the latest "Operating System Build" sooner? and is there a better way of monitoring progress of OS upgrade deployments? Feel free to tell me i am doing it wrong :)

Microsoft Configuration Manager Deployment
Microsoft Configuration Manager Deployment
Microsoft Configuration Manager: An integrated solution for for managing large groups of personal computers and servers.Deployment: The process of delivering, assembling, and maintaining a particular version of a software system at a site.
907 questions
Microsoft Configuration Manager
0 comments

4 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Rahul Jindal [MVP] 9,241 Reputation points MVP
    2021-04-06T22:28:03.85+00:00

    The deployment status is not dependent on HW, but if you are looking for a quick turn around this for reporting purposes then see if you can add a wmi trigger for sending HW inventory at the end of your IPU TS. Also, you can look at creating a custom report based on status messages.

    1 person found this answer helpful.
    0 comments
  2. Garth Jones 2,071 Reputation points
    2021-04-07T00:05:17.83+00:00

    There are two issues...

    1. Status is taking a while to update.
    2. Build number takes a while to update.

    So there are two different answers

    1. Depending on exactly where you are looking the status message are updated on a schedule...
    2. This is a loaded question as it will depend on exactly where you are look at this data. It will be hardware inv. Or heartbeat discovery.
    1 person found this answer helpful.
    0 comments
  3. jaybird283 561 Reputation points
    2021-04-07T19:35:55.267+00:00

    Thanks for the replies! Those are a few good options to try.

    Just curious. how do you all Monitor your deployments? Do you look at the deployment monitoring or do you create collections and watch machines fall out of them as they are upgraded?

    0 comments
  4. jaybird283 561 Reputation points
    2021-04-09T19:19:54.327+00:00

    @Kalyan Sundar That was super helpful. that's a great way of monitoring. i love it. thanks for sharing. just an FYI, the first article you referenced got me 90% of the way there. but i think his message ID (401) might not have been right with newer versions. i ended up using the query from the second link instead.

    and in case that link isn't accessible in the future. here is the query. (Just modify your Task Sequence ID)

    select SMS_StatusMessage., SMS_StatMsgInsStrings., SMS_StatMsgAttributes.*, SMS_StatMsgAttributes.AttributeTime
    from SMS_StatusMessage
    left join SMS_StatMsgInsStrings
    on SMS_StatMsgInsStrings.RecordID = SMS_StatusMessage.RecordID
    left join SMS_StatMsgAttributes
    on SMS_StatMsgAttributes.RecordID = SMS_StatusMessage.RecordID
    where SMS_StatMsgAttributes.AttributeValue = "TP10000B" and SMS_StatMsgAttributes.AttributeTime >= ##PRM:SMS_StatMsgAttributes.AttributeTime##
    order by SMS_StatMsgAttributes.AttributeTime
    DESC

    0 comments