Sysprep Skipping Computer Name Prompt

[Guest]

I have prepared a master image for a new machine. I have run sysprep using
the mini-setup option and generating a new SID. After running sysprep and/or
whenever deploying the image, the computer skips the first GUI prompt for the
Computer Name and Administrator password. After about 10 minutes, the
machine comes up with an error concerning joining the domain. If I power
cycle the machine (either before or when the error pops up), then the process
starts all over and the prompt for Computer Name will appear.

Background:
1) I am using a sysprep.inf file that I have used on past images (used
across 5 different hardware models on both XP and 2000) that did not have
this problem.
2) Using latest version of XP sysprep
3) There is no "computername" line at all in the sysprep.inf
4) The local administrator password is entered in the sysprep.inf

I have researched this issue extensively with no luck. Does anyone have any
ideas?

Thanks.

 

[BG]

How many NICs in your machine?

I have the same problem with a sysprep.inf that I've used successfully on the same machines before. The only difference is the image. This one is a raw SP2 image without patches.

EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com

 

[Guest]

There are 4 network connections that are installed. They are listed as
follows:

Local Area Connection Used Internal
Ethernet Gigabit NIC
1394 Connection Not used Installed by
Windows Plug and Play
Wireless Network Connection Used Built In 802.11
wireless NIC
Cingular GPRS Used Installed
as part of Sierra Wireless software for wireless card

Do you have any theories as to what may be happening?

 

[Bruce Griffith]

Lots of theories, but I haven't find a way to prove them. I suspect a driver problem, specifically ethernet. Is your gigabit NIC an Intel or an integrated NVIDIA?

Try running sysprep again after mini-setup. This works for me, although the network drivers are honked up afterwards and the machine is miserably slow.

EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com

 

[Hervé AUBRY]

I've got a problem like this one, the mini setup didn't use my sysprep.inf
file. It was due of a file under WINDOWS\SYSTEM32 called "$winnt$.inf.
After deletion sysprep works well.