Re: SysPrep Problem - Hangs on first boot

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: John (jjcc101_at_community.nospam)
Date: 08/10/04


Date: Tue, 10 Aug 2004 14:56:37 -0400

Repost - sure would like to know why this is happening. I have tried
everything to fix it. I am going to plan B now, which is to use Ghost
Walker to set my computer's SID and name.

"John" <jjcc101@community.nospam> wrote in message
news:uofXZvVfEHA.3928@TK2MSFTNGP11.phx.gbl...
> I have a Windows XP Pro computer that I have been working on imaging for
> several weeks. I have gone through many iterations of SysPrep, image,
> reboot over the weeks. More iterations that I would like to think about.
;)
> I have not had any problems... until Friday.
>
> Suddenly on the first reboot after doing a SysPrep it hangs on the blue
> screen that says the computer is being setup, followed by the dots... It
> locks up right there after the 9th dot displays. I let it sit for an hour
> and nothing happens.
>
> If I power down and restart a second time it seems to go through the
process
> but all my local user profiles are corrupted, showing in the list as
> 'unknown.' When I log in as one of those users it creates a new profile,
> but this time the folder in the "Documents and Settings" tree shows the
user
> name plus a period plus the computer name. It did not name it that way
> before. And of course I get the default user configuration which doesn't
do
> me much good.
>
> All I am doing is running SysPrep, checking the mini-setup check box and
> clicking reseal. Then I reboot. I am using the same inf file as before
and
> I have no idea why this problem just started to happen.
>
> Why did this suddenly start to happen? Please help!!
>
>
>
> Windows XP Pro
> Volume License Key that does not require activation
> Latest version of SysPrep
>
>
> ;SetupMgrTag
> [Unattended]
> OemSkipEula=Yes
> InstallFilesPath=C:\sysprep\i386
> TargetPath=\WINDOWS
> OemPnPDriversPath=
> DriverSigningPolicy=Ignore
> UpdateInstalledDrivers=Yes
> OEMPreinstall=Yes
>
> [GuiUnattended]
> AdminPassword="*****"
> EncryptedAdminPassword=NO
> OEMSkipRegional=1
> TimeZone=35
> OemSkipWelcome=1
>
> [UserData]
> ProductKey=******
> FullName="Workstation"
> OrgName="Company Name"
> ComputerName=*
>
> [Display]
> Xresolution=800
> YResolution=600
>
> [TapiLocation]
> CountryCode=1
> Dialing=Tone
> AreaCode=301
> LongDistanceAccess="9,"
>
> [Identification]
> JoinWorkgroup=WORKGROUPNAME
>
> [Networking]
> InstallDefaultComponents=Yes
>
> [Branding]
> BrandIEUsingUnattended=Yes
>
> [Proxy]
> Proxy_Enable=0
> Use_Same_Proxy=0
>
> [SetupMgr]
> DistFolder=C:\sysprep\i386
> DistShare=windist
>
>
>



Relevant Pages

  • Re: sysprep
    ... Sysprep will strip the details out like Dave & I have both said. ... session you have given the Ghost Corporate edition ... reboot the machine which will load the boot loader. ... due to the admin password in the sysprep config file... ...
    (microsoft.public.windowsxp.general)
  • Re: SP2 SysPrep Imaging Problem: Lost Model Independence
    ... This sounds like a mass storage controller issue. ... have the PnP IDs in the Sysprep.inf for the mass storage adapter of the ... > have a problem that started with the new SysPrep for XP SP2 that I have ... > When I download that image to the exact same model of computer and reboot, ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: Sysprep and multiple computer names
    ... time, reboot, join it to the domain, reboot again, then add user profile. ... know sysprep can take care of the domain join part, ... If you don't use SysPrep before cloning the first computer, you'll end up with 10 computers with the same machine SID, which is definitely *not good*. ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: OSC Image Capture Wizard Network Error
    ... The log indicates that sysprep is returning error code 259 (no more data ... -- brett flegg | software design engineer/test | SMS | OSD FP This posting is provided AS IS with no warranties and confers no rights. ... > a reboot or anything. ... >> It sounds like the capture wizard is failing in the full OS for some>> reason. ...
    (microsoft.public.sms.tools)