Logging on locally after unattended install joins computer to the doma

**jeremyschubert** · May 25, 2007

My sif file is below. I have set up my unattended install so that the computer joins the domain and is placed in the appropriate OU. That allows it to right away catch a few GPO installs. I thought I was setting it up to log in once locally and run c:\install\start.cmd. In start.cmd, I have a registry edot that is supposed to set the appropriate default domain to logon to. Then another registry edit sets the computer to automatically logon to a specific domain account. Then it's to run shutdown.exe so that the computer will reboot and autologn on to the specific domain user account. The login script of that specific user account then deletes c:\install, installs some more software, sets the computer not to autologon on and then reboots the computer.

Problem is that when I come back to the computer after the install is finished, the domain rather then the local machien name is showing in the domain field for logging on. The c:\install folder is still there and none of the programs have installed. So I log in with a domain account, run c:\install\start.cmd and everything then starts to work as it should.

I'm wondering if having the computer placed in a specific domain during the install is causing the domain to show in the domain field rather than the computer name? So then the local admin account can't log in? Does that make sense?

SIF File

;SetupMgrTag

[Data]

AutoPartition=1

MsDosInitiated="0"

UnattendedInstall="Yes"

AutomaticUpdates=yes

[unattended]

UnattendMode=FullUnattended

OemSkipEula=Yes

OemPreinstall=Yes

TargetPath=\WINDOWS