SCCM has detected an alert: {AlertName}. {AlertText}
Alert type: {AlertType}
Severity: {Severity}
Active time (UTC): {ActiveTimestamp}
Condition: {RaiseCondition}
@if(RootCause){
Root cause: {RootCause}
}
Comment: {Comment}
Same as HTTP status 502 - the server, while acting as a gateway or proxy, received an invalid response from the upstream ...
Same as SOAPCLIENT_INITIALIZE_ERROR - initialization of the SOAP client failed, possibly because of an MSXML installation ...
Same as SOAPCLIENT_SOAPFAULT - SOAP client failed because there was a SOAP fault for reasons of WU_E_PT_SOAP_* error codes. ...
Save your work to avoid losing data. Notify users logged on to this computer that they should log off immediately for a pending ...
SCCM has detected an alert: {AlertName}. {AlertText} Alert type: {AlertType} Severity: {Severity} Active time (UTC): {ActiveTimestamp} ...
Scheduler at site %1 has received package %2 version %3 and has instructed the Sender to send the package to the following ...
Scheduler does not have an address defined at site "%2" for site "%1". Files cannot be sent from site "%2" to site "%1" until ...
Scheduler has data to send to site "%1", and addresses defined at site "%2" for site "%1", but none of them are available ...
Script execution failed with error code -1. Failure may be related to execution policy not being set to Bypass for power ...