question

jaybird283-2674 avatar image
0 Votes"
jaybird283-2674 asked jaybird283-2674 edited

Monitroing Windows 10 OS Upgrades in Configuration Manager

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 :)

mem-cm-generalmem-cm-osd
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

kalyansundar-6796 avatar image
1 Vote"
kalyansundar-6796 answered
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

RahulJindal-2267 avatar image
1 Vote"
RahulJindal-2267 answered

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.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

GarthJones-MVP avatar image
1 Vote"
GarthJones-MVP answered

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.


5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

jaybird283-2674 avatar image
0 Votes"
jaybird283-2674 answered

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?

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

jaybird283-2674 avatar image
0 Votes"
jaybird283-2674 answered jaybird283-2674 edited

@kalyansundar-6796 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

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.