User '{0}' at '{1}' failed to start a Remote Tools session with '{2}'.
Solution: Verify that the Remote Tools Client Agent is installed on the client. If the agent is installed and you cannot start a Remote Tools session, use the "Show Status" command on Control Panel, Remote Tools on the client to verify that the Remote Control Agent is listening on the right protocol.
User '{0}' at '{1}' failed to perform a status information query from '{2}'. WinRM error code: '{3}'; PT error code: '{4}'; ...
User '{0}' at '{1}' failed to perform a system inventory query from '{2}'. WinRM error code: '{3}'; PT error code: '{4}'; ...
User '{0}' at '{1}' failed to start a Remote Tools session with '{2}' due to insufficient security credentials. Solution: ...
User '{0}' at '{1}' failed to start a Remote Tools session with '{2}'. Solution: Confirm that another Remote Tools session ...
User '{0}' at '{1}' failed to start a Remote Tools session with '{2}'. Solution: Verify that the Remote Tools Client Agent ...
User '{0}' at '{1}' lost a Remote Tools connection with '{2}'. Possible cause: When Remote.exe has an open connection to ...
User '{0}' at '{1}' lost a Remote Tools connection with '{2}'. Possible cause: When Remote.exe has an open connection to ...
User '{0}' attempted to download the content for software update with CI_ID '{1}'. Update Details: ID = '{2}', QNumbers = ...
User '{0}' attempted to import the content for software update with CI_ID '{1}'. Update Details: ID = '{2}', QNumbers = '{3}', ...