Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Microsoft KB Archive/171005

From BetaArchive Wiki
Knowledge Base

SMS: Site Configuration Manager service locks trusted service account

Article ID: 171005

Article Last Modified on 10/27/2006


  • Microsoft Systems Management Server 1.0 Standard Edition
  • Microsoft Systems Management Server 1.1 Standard Edition
  • Microsoft Systems Management Server 1.2 Standard Edition

This article was previously published under Q171005


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

   15:49:57 1997~><thread=12E>
   ~Trusted domain: DOMAINB   $$<SMS_SITE_CONFIG_MANAGER><Wed Jun 18

   ~NetServerGetInfo server: SERVER return: 5

   15:50:03 1997~><thread=12E>


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.


To work around this problem, do either of the following:

  • Change the Systems Management Server Service Account name on the trusted domain.


  • If the trusted domain is not using Program Group Control (PGC), use the SETGUG utility to shut off global user group enumeration.


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: kbbug kbnetwork kbscman KB171005