%11The data file "%1" that was submitted by the client whose SMS unique ID is "%2", was rejected because the file was signed but the authentication key did not match the recorded key for this client. Possible Cause: This usually happens when a client at a native mode site has been moved to a mixed mode site but the parent site is not aware of the change. Solution: If the mixed mode client data should overwrite the native mode client data, delete the client record at the central site, which will allow the mixed mode client to re-register with its assigned site and resend the data up the hierarchy. If you have not moved the client from a native mode site to a mixed mode site, investigate the mixed mode client computer for misconfiguration or tampering.%12%3%4%5%6%7%8%9%10%0
The currently logged-in user does not have rights to access the client machine. You must provide the username, domain, and ...
The data file "%1" that was submitted by the client whose SMS unique ID is "%2", was rejected because the file was not signed ...
The data file "%1" that was submitted by the client whose SMS unique ID is "%2", was rejected because the file was signed ...
The data file "%1" that was submitted by the client whose SMS unique ID is "%2", was rejected because the file was signed ...
The data file "%1" that was submitted by the client whose SMS unique ID is "%2", was rejected because the file was signed ...
The database must already exist on the SQL Server. The minimum database size is %d MB, the transaction log size should be ...
The Delete Aged Collected Files database maintenance task completed successfully. The task deleted %1 collected files and ...
The Delete Inactive Client Discovery Data task has completed, %1 inactive clients have been removed from the database.%12%0 ...
The Delete Obsolete Client Discovery Data task has completed, %1 obsolete clients have been removed from the database.%12%0 ...