%11SMS Site Component Manager successfully installed this component. However the SQL Server Principal Name (SPN) could not be validated in Active Directory. Possible cause: The MSSQL Service is running under a user account, instead of the computer account. In this case, SQL does not publish its own SPN. Solution: Manually publish the SQL SPN in Active Directory. The component %1 will operate correctly. However remote site systems requiring access to SQL Server (i.e., server locator points, or management points) might not be able to access SQL in advanced security mode. Refer to your SMS documentation or the Microsoft Knowledge Base for further information.%0
SMS Site Component Manager removed the "%2" account from site system "%1". When SMS Site Component Manager installed SMS ...
SMS Site Component Manager successfully configured site system "%1" to receive SMS server components. SMS Site Component ...
SMS Site Component Manager successfully installed the COM access registry keys for this component on this site system.%0 ...
SMS Site Component Manager successfully installed this component, However a reboot is required to complete the installation. ...
SMS Site Component Manager successfully installed this component. However the SQL Server Principal Name (SPN) could not be ...
SMS Site Component Manager successfully reconfigured site system "%1" to receive SMS server components. SMS Site Component ...
SMS Site Component Manager successfully removed all accounts, files, and registry keys associated with the SMS server components ...
SMS Site Component Manager successfully removed the COM access registry keys for this component from this site system.%0 ...
SMS Site Component Manager successfully used the %1 service to run the following program on site system "%2": %3 %4 %5 The ...