sysprep ignoring computer name

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi all,
I have a major problem on our network. Almost all of our systems were build
using ghost. sysprep was not run as part of the image so there are errors
everywhere. I have been working on deploying sysprep via sms but I have one
hang up. I have a custom app that queries the existing hostname and inserts
it into the .inf file. This works just fine. After running sysprep though the
user is prompted for the computer name? Any answers as to why the computer
name is being ignored by sysprep? here is my .inf file:

;Created: March 02, 2007

[Unattended]
UnattendMode = "ReadOnly"
OemSkipEula="Yes"

OemPnPDriversPath="winnt\drivers\Video;winnt\drivers\Network;winnt\drivers\Audio"
InstallFilesPath="C:\sysprep\i386"
DriverSigningPolicy="Ignore"

[GuiUnattended]
AdminPassword="XXXXXXXX" (changed for this post)
OEMSkipRegional=1
TimeZone=15
OemSkipWelcome=1

[UserData]
ComputerName=XXXXXXX (changed for this post)
FullName=Computer System (changed for this post)
Orgname=Company name (changed for this post)

[Display]
BitsPerPel=16
Xresolution=1024
YResolution=768

[SetupMgr]
DistFolder=C:\sysprep\i386
DistShare=win2000dist

[Identification]
JoinDomain="Domain name" (changed for this post)
DomainAdmin="My account" (changed for this post)
DomainAdminPassword="password" (changed for this post)

[Networking]
InstallDefaultComponents=Yes
 
I had a similar problem to yours....well actually the opposite!

We need sysprep to prompt for a computer name, however when mini setup
started to run, we saw the 'computer name' dialogue flip by very quickly and
then proceed to immediately try to add the machine to the domain, which would
fail after 10 minutes of waiting!

To get around the problem, I turned (powered off) the workstation when it
was in the 10 minute domain adding phase of mini setup.

When I powered it back on, sysprep ran AGAIN, but this time it did wait and
prompt for a computer name.

Best guess....is that maybe sysprep is caught at a particular point and
cannot finish or be "re-prepped" until the first place where it was caught is
satisfied.

Try powering it off and back on and see if sysprep will run again and be
successful.

Let everyone know if this works!

Mark
 
Back
Top