Sysprep 2.0 & XP SP2 - Failed to Update Registry

[Kenny]

I have a brand new Dell Optiplex GX520 (SATA Drives, if that matters) this
is the first time I'm running sysprep with SP2. Everytime I run it I just
"unable to update registry when the machine comes back up.
I have tried Sysprep 1.0 with my standard answer file, and sysprep 2.0 with
a new answer file I generated (shown below). On someone elses advice I also
tried running sysprep with no answer file but it ended in the same result.

I have searched the internet and this forum and haven't found anything that
seems to pertinent to my problem. anyone have any ideas?

Thanks, Kenny

;SetupMgrTag
[Unattended]
InstallFilesPath=C:\sysprep\i386

[GuiUnattended]
AdminPassword=password
EncryptedAdminPassword=no
OEMSkipRegional=1

[UserData]
ProductKey=XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
FullName="user1"
OrgName="my company"

[TapiLocation]
CountryCode=1
Dialing=Tone
AreaCode=770

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

[GuiRunOnce]
Command0=C:\windows\system32\SetServiceTag.exe

[Identification]
JoinDomain=CWD

[Networking]
InstallDefaultComponents=Yes

 

[Guest]

Give this a try: (it can also be a drive permission issue but that is another
thing). Also, are you using Ghost, PE or what?
SetupMgrTag
[Unattended]
OemSkipEula=Yes or No (choose one)
KeepPageFile=0
TargetPath=\WINDOWS
[GuiUnattended]
AdminPassword=password
EncryptedAdminPassword=no
OEMSkipRegional=1
[UserData]
ProductKey=XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
FullName="user1"
OrgName="my company"
[TapiLocation]
CountryCode=1
Dialing=Tone
AreaCode=770
[GuiRunOnce]
Command0=C:\windows\system32\SetServiceTag.exe
[Identification]
JoinDomain=CWD
[Networking]
InstallDefaultComponents=Yes

 

[Kenny]

Same result on that one I'm afraid

What permissions should I be looking at? On my C:\sysprep folder
Administrators, Users, and SYSTEM have full control. I have also verified
that the read only attribute is off on the folder and all of it's contents.

What other security could effect this?

To tell you the truth I built this from scratch so it shoul dhave the
default security, I granted additional permissions in places but I did not
revoke permissions anywhere. However I'm willing to try anything I'm flying
out Monday to dpeloy these machines.

Thanks, Kenny

 

[Kenny]

Here what I pulled out of some logs:

1st Error-
D:\XPSPRTM\base\NTsetup\syssetup\syssetup.c,1514,... failed. Error = 5


I'm not even sure if the next two are errors depends one whether 1 or 0
means success I guess.

2nd Error-
RUNONCE -r returned exit code 1

3rd Error-
SetUpVirtualMemory: Exit (1)

 

[Darrell Gorter[MSFT]]

Hello Kenny,
Is this the correct error message in this article?
818171 "An Error Has Been Encountered That Prevents Setup from Continuing"
http://support.microsoft.com/?id=818171

Also look at this article that talks about possible issues with the
[SysprepMassStorage] section.
249690 "An error occurred while trying to update your registry" message
http://support.microsoft.com/?id=249690

Thanks,
Darrell Gorter[MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
<From: "Kenny" <[email protected]>
<References: <#[email protected]>
<[email protected]>
<Subject: Re: Sysprep 2.0 & XP SP2 - Failed to Update Registry
<Date: Tue, 8 Nov 2005 17:51:33 -0500
<Lines: 16
<X-Priority: 3
<X-MSMail-Priority: Normal
<X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
<X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
<X-RFC2646: Format=Flowed; Original
<Message-ID: <[email protected]>
<Newsgroups: microsoft.public.windowsxp.setup_deployment
<NNTP-Posting-Host: cooperlighting-sw.cooperlighting.com 216.130.131.66
<Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP15.phx.gbl
<Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windowsxp.setup_deployment:37503
<X-Tomcat-NG: microsoft.public.windowsxp.setup_deployment
<
<Same result on that one I'm afraid
<
<What permissions should I be looking at? On my C:\sysprep folder
<Administrators, Users, and SYSTEM have full control. I have also verified
<that the read only attribute is off on the folder and all of it's contents.
<
<What other security could effect this?
<
<To tell you the truth I built this from scratch so it shoul dhave the
<default security, I granted additional permissions in places but I did not
<revoke permissions anywhere. However I'm willing to try anything I'm
flying
<out Monday to dpeloy these machines.
<
<Thanks, Kenny
<
<
<