%11SMS Component Status Summarizer reset the status of component "%1", running on computer "%2", to OK.%12 SMS Component Status Summarizer will automatically reset a component's status to OK every time the Component Status Threshold Period elapses and a new Threshold Period begins. For example, if the Threshold Period is "Since 12:00:00 AM", SMS Component Status Summarizer will reset the component's status to OK every 24 hours at midnight. At this time, the counts of status messages reported by the component for the Threshold Period will be reset to zero. Solution: SMS Component Status Summarizer will also reset a component's status to OK when an administrator manually resets the counts of status messages reported by the component for the Threshold Period. Solution: SMS Component Status Summarizer will also reset a component's status to OK when an administrator adjusts the Component Status Thresholds to be higher than the current counts of status messages reported by the component.%0
SMS Component Status Summarizer reset the count of Warning status messages reported by component "%1" on computer "%2" for ...
SMS Component Status Summarizer reset the count of Warning status messages reported by component "%1" on computer "%2" for ...
SMS Component Status Summarizer reset the count of Warning status messages reported by component "%1" on computer "%2" for ...
SMS Component Status Summarizer reset the count of Warning status messages reported by component "%1" on computer "%2" for ...
SMS Component Status Summarizer reset the status of component "%1", running on computer "%2", to OK.%12 SMS Component Status ...
SMS Component Status Summarizer set the status of component "%1" running on computer "%2" to Warning.%12 Possible cause: ...
SMS Component Status Summarizer set the status of component "%1", running on computer "%2", to Critical.%12 Possible cause: ...
SMS Despooler deleted an instruction and package file from SMS 2.0 child site %1 because this site doesn't allow any child ...
SMS Despooler failed to decompress package "%1" from "%2".%12 Possible cause: The compressed image "%2" is either missing ...