DOCUMENT:Q171005 31-JUL-2001 [sms] TITLE :SMS: Site Config Manager Service Locks Trusted Service Account PRODUCT :Microsoft Systems Management Server PROD/VER:winnt:1.0,1.1,1.2 OPER/SYS: KEYWORDS:kbnetwork kbSCMan smssiteconfigman ====================================================================== ------------------------------------------------------------------------------- The information in this article applies to: - Microsoft Systems Management Server versions 1.0, 1.1, 1.2 ------------------------------------------------------------------------------- SYMPTOMS ======== When Site Configuration Manager (SCMAN) does global user group enumeration, a Systems Management Server service account for another Systems Management Server site may be locked out in the process. The Scman.log file will have entries similar to the following: ~Domain (DOMAINA) user groups previously enumerated $$ ~Trusted domain: DOMAINB $$ ~NetServerGetInfo server: SERVER return: 5 $$ CAUSE ===== This problem occurs if the two domains have Systems Management Server service accounts that have the same user name, but different passwords. When the domain for the site where SCMAN is running is trusted by the other site's domain, Site Configuration Manager attempts to enumerate the user groups of the trusted domain using its service account. Because the passwords do not match, an error 5 (access denied) occurs. If account lockout is set at the trusted domain, this may result in the trusted domain's Systems Management Server service account being locked out. WORKAROUND ========== To work around this problem, do either of the following: - Change the Systems Management Server Service Account name on the trusted domain. -or- - If the trusted domain is not using Program Group Control (PGC), use the SETGUG utility to shut off global user group enumeration. For more information on the SETGUG utility, see the following article in the Microsoft Knowledge Base: Q168724 SMS: List of Tools Available on SMS 1.2 CD STATUS ====== Microsoft has confirmed this to be a problem in Systems Management Server versions 1.0, 1.1, and 1.2. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available. Additional query words: prodsms sms ====================================================================== Keywords : kbnetwork kbSCMan smssiteconfigman Technology : kbSMSSearch kbSMS100 kbSMS110 kbSMS120 Version : winnt:1.0,1.1,1.2 Issue type : kbbug ============================================================================= THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY. Copyright Microsoft Corporation 2001.