Knowledge Base

Automated Setup Does Not Install BDC

Article ID: 129284

Article Last Modified on 11/1/2006

Microsoft Windows NT Server 3.5
Microsoft Windows NT Server 3.51

This article was previously published under Q129284

SYMPTOMS

Computer Profile Setup (CPS) and Unattended Setup fail to install a backup domain controller (BDC). Setup configures the machine as a primary domain controller (PDC) rather than as a BDC.

CAUSE

NTLANMAN.INF performs an incomplete comparison of the variable STF_AUTOPRIMARY.

     ifstr(i) $(!STF_AUTOPRIMARY) != ""
         set NCPA_CMD_LINE = $(NCPA_CMD_LINE)" /t STF_AUTOPRIMARY = YES"
         endif

RESOLUTION

To correct this problem, edit your answer file before using it to install Windows NT Server. Change the line that reads:

   !AutoPrimary =    "no"

   !AutoPrimary =     ""

If you are running CPS, make the above modification to %SYSTEMROOT%\SYSTEM32\DEFAULTS.INF on the Distribution share after running UPLODPRF.EXE, but before running WINNTP.EXE.

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 3.5 and 3.51. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional query words: prodnt setupmgr.exe

Keywords: KB129284