locked
Task Sequencing monitoring --- very poor??? RRS feed

  • Question

  • Hi,

    just a quick one. In cm07 you could view a TS deployment from Advertisements status, monitoring each step as it happened. Any idea how you do that in CM12?

    I've seenin monitoring-deployments there is 1line information, but it doesn't give anywhere near the information required. Before if you have a 50 step Task sequence you could monitor each step in a log viewer, now it's a 1 liner that even when it fails doesn't provide failure details... very very poor, especially when monitoring multiple machines during different deployments...

    Any idea if TS monitoring can only be done from Monitoring -> deployments???

    and no, not considering SMSTS.log for this scenario when trying to monitor multiple deployments

    Monday, November 5, 2012 7:49 PM

Answers

  • Hi,

    have you tried out the report "Status summary of a specific task sequence deployment" from that report you can drill down to an individual deployment and get the same level of details as in SCCM 2007.

    Regards,
    Jörgen


    -- My System Center blog ccmexec.com -- Twitter @ccmexec

    • Marked as answer by Dancing Ferret Wednesday, November 7, 2012 1:58 PM
    Monday, November 5, 2012 8:08 PM

All replies

  • Hi,

    have you tried out the report "Status summary of a specific task sequence deployment" from that report you can drill down to an individual deployment and get the same level of details as in SCCM 2007.

    Regards,
    Jörgen


    -- My System Center blog ccmexec.com -- Twitter @ccmexec

    • Marked as answer by Dancing Ferret Wednesday, November 7, 2012 1:58 PM
    Monday, November 5, 2012 8:08 PM
  • As always spot on,  thanks Jörgen

    DF

    Wednesday, November 7, 2012 2:00 PM
  • If you prefer old messages config

    Just import following query in monitorign\overview\systemstatus\status messages queries

    select SMS_StatusMessage.*, SMS_StatMsgInsStrings.*, SMS_StatMsgAttributes.* 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_StatusMessage.MachineName = ##PRM:SMS_StatusMessage.MachineName## and SMS_StatusMessage.Component = "Task Sequence Engine" and SMS_StatMsgAttributes.AttributeTime > ##PRM:SMS_StatMsgAttributes.AttributeTime##

    Then execute it,

    put computername and time

    and you will see all task sequences messages beginning at time entered.


    JEFFDEG

    • Proposed as answer by JEFF DEG Wednesday, November 14, 2012 10:22 AM
    Wednesday, November 14, 2012 10:22 AM