%11SMS NT User Group Discovery Agent failed to find the primary domain controller for the domain %1.%12 Possible cause: The primary domain controller is not accessible. Solution: Verify that the primary domain controller is running and accessible. Possible cause: The domain %1 does not exist. Solution: Verify that the domain name was specified correctly. In SMS Administrator console, under Site Settings, Discovery Methods, open the Windows NT User Group Discovery dialog box. Possible cause: The SMS Service account lacks sufficient rights in the domain %1. Solution: See the SMS documentation for the necessary rights of the SMS Service account, then ensure that the SMS Service account has such rights.%0
SMS NT User Discovery Agent failed to read the location of the outbox, but it will retry at its next interval.%12 Solution: ...
SMS NT User Discovery Agent failed to read the necessary registry information, but it will retry at its next interval.%12%0 ...
SMS NT User Group Discovery Agent failed to determine the trusted domains for the domain %1. Therefore, no users from the ...
SMS NT User Group Discovery Agent failed to enumerate user groups from the domain %1. No users from the trusted domains will ...
SMS NT User Group Discovery Agent failed to find the primary domain controller for the domain %1.%12 Possible cause: The ...
SMS NT User Group Discovery Agent failed to read the location of the outbox, but it will retry at its next interval.%12 Solution: ...
SMS NT User Group Discovery Agent failed to read the necessary registry information, but it will retry at its next interval.%12%0 ...
SMS NW Logon Discovery Manager detected that there is no NetWare bindery redirector installed on the site server. SMS NW ...
SMS NW Logon Discovery Manager failed to initialize, but it will retry in one hour. Possible cause: SMS Inbox Manager is ...