SYMPTOMS
Client Setup may not start on a Windows 2000-based domain controller because the replication of the SMS#_
DCname account creation takes longer than 60 minutes on a large Windows 2000 Active Directory site. The same symptoms occur if the replication for the temporary bootstrap account succeeds in time and the SMS#_
DCname client service account is created.
For additional information, click the article number below
to view the article in the Microsoft Knowledge Base:
271724 SMS May Time Out Attempting a PDC/BDC Resynchronization in a Large Windows 2000 Active Directory Environment
RESOLUTION
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Systems Management Server service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The French version of this fix should have the following file attributes or later:
Date Time Version Size File name Platform
----------------------------------------------------------------
03/01/2001 05:15p 2.00.1493.3140 240,400 Ccm.dll Alpha
03/01/2001 05:15p 2.00.1493.3140 151,952 Ccm.dll Intel
NOTE: Because of file dependencies, the most recent hotfix or feature that contains the above files may also contain additional files.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
Note that the SMS 2.0 SP 3 French download that is available from
http://www.microsoft.com/smsmgmt/downloads/sms20sp3.asp has been updated to include this fix.