SMS: Password Uniqueness Disables SMS 2.0 Server Client Install (216855)

The information in this article applies to:

Microsoft Systems Management Server 1.2
Microsoft Systems Management Server 2.0

This article was previously published under Q216855

SYMPTOMS

In Systems Management Server 2.0, client component installation on computers running Microsoft Windows NT Server 4.0 through SMS_CLIENT_CONFIG_MANAGER may fail to complete when password uniqueness is enabled within the domain.

WORKAROUND

To work around this problem, use the Windows NT Server User Manager for Domains to disable password uniqueness in the Account policy of the domain. To do this, perform the following steps:

Start User Manager for Domains.
On the Policies menu, click Account.
In the Password Uniqueness section of the Account Policy dialog box, click Do Not Keep Password History.

STATUS

Microsoft has confirmed that this is a problem in Systems Management Server 2.0. This problem was first corrected in Systems Management Server 2.0 Service Pack 1.

MORE INFORMATION

When password uniqueness is enabled in User Manager for Domains, the installation of the client components on a computer running Windows NT Server fails to complete. A temporary directory, Sms_temp, is left in the system root directory, while the system_root\MS\SMS directories are not fully populated. If logging of SMS_CLIENT_CONFIG_MANAGER is enabled at the site server, several message 2245 entries are logged:

--->Wait Waiting for PDC/BDC Sync (2245) $$ SMS_CLIENT_CONFIG_MANAGER

Modification Type:	Major	Last Reviewed:	10/8/2006
Keywords:	kbBug kbClient kbfix kbQFE kbHotfixServer KB216855