SYSPREP problem

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

Guest

After running setupmgr to create an answer file for sysprep i get the
following error:
"An error occurred while trying to update your registry" when running
sysprep. I have googled and found one MS KB doc however that is not the
problem.

Windows 2K PRO Version 5.0 Build 2195 SP4
Logged in as local admin
no gp restricting reg edit.

TIA
 
Yea, That is the one. Made sure answer file was correct. I did also google
for over an hour before i posted.
 
Hi,
I don't want to prove you wrong but for the better understanding of the
issue can you please paste your sysprep.inf file and list your system
hardware here.

Lukesh
 
Here is the inf file the delpoyment tool made.
;SetupMgrTag
[Unattended]
OemPnPDriversPath=C:\drivers
InstallFilesPath=C:\sysprep\i386

[GuiUnattended]
AdminPassword=#######
OEMSkipRegional=1
OEMDuplicatorstring=LabSysprep92905
TimeZone=35

[UserData]
FullName=Lab
OrgName="Cardiac Telecom Corporation"

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

[RegionalSettings]
LanguageGroup=1
Language=00000409

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

[Identification]
JoinDomain=HRSLAB
DomainAdmin=#######
DomainAdminPassword=#######l

[Networking]
InstallDefaultComponents=Yes
 
is this group monitored by MS?
--
Vincent Lape



vlape said:
Here is the inf file the delpoyment tool made.
;SetupMgrTag
[Unattended]
OemPnPDriversPath=C:\drivers
InstallFilesPath=C:\sysprep\i386

[GuiUnattended]
AdminPassword=#######
OEMSkipRegional=1
OEMDuplicatorstring=LabSysprep92905
TimeZone=35

[UserData]
FullName=Lab
OrgName="Cardiac Telecom Corporation"

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

[RegionalSettings]
LanguageGroup=1
Language=00000409

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

[Identification]
JoinDomain=HRSLAB
DomainAdmin=#######
DomainAdminPassword=#######l

[Networking]
InstallDefaultComponents=Yes


--
Vincent Lape



lukesh said:
Hi,
I don't want to prove you wrong but for the better understanding of the
issue can you please paste your sysprep.inf file and list your system
hardware here.

Lukesh
 
Hi,
Are you using any third party mass storage drivers on this box. Even if you
are not using them, you can try including [SysprepMassStorage] section in
your sysprep.inf file manually. You can refer:
http://support.microsoft.com/?kbid=303786

I am also including one such section as an example. I hope it helps:
[SysprepMassStorage]
PCI\CC_0101=%systemroot%\inf\mshdc.inf
PCI\VEN_8086&DEV_2411=%systemroot%\inf\mshdc.inf
Primary_IDE_Channel = %windir%\inf\mshdc.inf
Secondary_IDE_Channel = %windir%\inf\mshdc.inf

You can also include pnp id's from scsi.inf files. If you are using a third
party controller, specify pnp id's usinf their inf files.

Lukesh
 
Tried it, no joy.

As soon as the sysprep tool launches i get the this app will caose system to
reboot bla bla bla.... As soon as i press OK the error "An error occored
while trying to update registry" Unable to continue.

To launch sysprep i am using sysprep.bat created by setupmgr it calls
sysprep -pnp
 
I broke down and Called Microsoft Technical Support. It took 1 hour to get
someone who spoke english i could understand. After that 1 1/2 hours later
the engineer was stumped. We will be working on the issue again monday. I
will post any resolution.
 
Hi,
Ofcourse he'll be stumped. This is one of the strangest sysprep issues I
have ever faced. Your sysprep file looks good and it seems as if there is
some issue when sysprep tries to enumerate the registry. Probably a registry
corruption issue. Please keep me posted about what happened.
Thanks,
Lukesh

vlape said:
I broke down and Called Microsoft Technical Support. It took 1 hour to get
someone who spoke english i could understand. After that 1 1/2 hours later
the engineer was stumped. We will be working on the issue again monday. I
will post any resolution.
--
Vincent Lape



lukesh said:
Hi,
Are you using any third party mass storage drivers on this box. Even if you
are not using them, you can try including [SysprepMassStorage] section in
your sysprep.inf file manually. You can refer:
http://support.microsoft.com/?kbid=303786

I am also including one such section as an example. I hope it helps:
[SysprepMassStorage]
PCI\CC_0101=%systemroot%\inf\mshdc.inf
PCI\VEN_8086&DEV_2411=%systemroot%\inf\mshdc.inf
Primary_IDE_Channel = %windir%\inf\mshdc.inf
Secondary_IDE_Channel = %windir%\inf\mshdc.inf

You can also include pnp id's from scsi.inf files. If you are using a third
party controller, specify pnp id's usinf their inf files.

Lukesh
 
Hi,
1. Try adding a [SysprepMassStorage] section with nothing in it to your
Sysprep.inf file.
2. Make sure you download the Deployment Tools and use the version of
Sysprep.exe and setupmgr.exe that corresponds with the operating system
version and service pack:

http://www.microsoft.com/windows2000/downloads/servicepacks/SP4/deploytools.asp


3. Perform a clean/new install of Windows 2000 from retail media or Volume
License media and then try running Sysprep.exe. The current install of
Windows 2000 may be tainted. See the following articles for more
information:

828287 Unsupported Sysprep scenarios
http://support.microsoft.com/?id=828287

830958 Summary of the limitations of the System Preparation tool
http://support.microsoft.com/?id=830958

4. Avoid using any command-line switches with Sysprep.exe except for -mini
until we get this resolved.

--
Emmers Presson [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

vlape said:
Here is the inf file the delpoyment tool made.
;SetupMgrTag
[Unattended]
OemPnPDriversPath=C:\drivers
InstallFilesPath=C:\sysprep\i386

[GuiUnattended]
AdminPassword=#######
OEMSkipRegional=1
OEMDuplicatorstring=LabSysprep92905
TimeZone=35

[UserData]
FullName=Lab
OrgName="Cardiac Telecom Corporation"

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

[RegionalSettings]
LanguageGroup=1
Language=00000409

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

[Identification]
JoinDomain=HRSLAB
DomainAdmin=#######
DomainAdminPassword=#######l

[Networking]
InstallDefaultComponents=Yes


--
Vincent Lape



lukesh said:
Hi,
I don't want to prove you wrong but for the better understanding of the
issue can you please paste your sysprep.inf file and list your system
hardware here.

Lukesh
 
Hi Vincent,
It could be because of permissions on the registry. Give full control to
administrator and system on hkey_local_machine and replicate to the child
objects.

Lukesh

vlape said:
I broke down and Called Microsoft Technical Support. It took 1 hour to get
someone who spoke english i could understand. After that 1 1/2 hours later
the engineer was stumped. We will be working on the issue again monday. I
will post any resolution.
--
Vincent Lape



lukesh said:
Hi,
Are you using any third party mass storage drivers on this box. Even if you
are not using them, you can try including [SysprepMassStorage] section in
your sysprep.inf file manually. You can refer:
http://support.microsoft.com/?kbid=303786

I am also including one such section as an example. I hope it helps:
[SysprepMassStorage]
PCI\CC_0101=%systemroot%\inf\mshdc.inf
PCI\VEN_8086&DEV_2411=%systemroot%\inf\mshdc.inf
Primary_IDE_Channel = %windir%\inf\mshdc.inf
Secondary_IDE_Channel = %windir%\inf\mshdc.inf

You can also include pnp id's from scsi.inf files. If you are using a third
party controller, specify pnp id's usinf their inf files.

Lukesh
 
I doubt you are syspreping OEM build image and not the one created from
Retail Media

thanks
Preetam
Emmers Presson said:
Hi,
1. Try adding a [SysprepMassStorage] section with nothing in it to your
Sysprep.inf file.
2. Make sure you download the Deployment Tools and use the version of
Sysprep.exe and setupmgr.exe that corresponds with the operating system
version and service pack:


http://www.microsoft.com/windows2000/downloads/servicepacks/SP4/deploytools.asp


3. Perform a clean/new install of Windows 2000 from retail media or Volume
License media and then try running Sysprep.exe. The current install of
Windows 2000 may be tainted. See the following articles for more
information:

828287 Unsupported Sysprep scenarios
http://support.microsoft.com/?id=828287

830958 Summary of the limitations of the System Preparation tool
http://support.microsoft.com/?id=830958

4. Avoid using any command-line switches with Sysprep.exe except for -mini
until we get this resolved.

--
Emmers Presson [MSFT]
This posting is provided "AS IS" with no warranties, and confers no
rights.

vlape said:
Here is the inf file the delpoyment tool made.
;SetupMgrTag
[Unattended]
OemPnPDriversPath=C:\drivers
InstallFilesPath=C:\sysprep\i386

[GuiUnattended]
AdminPassword=#######
OEMSkipRegional=1
OEMDuplicatorstring=LabSysprep92905
TimeZone=35

[UserData]
FullName=Lab
OrgName="Cardiac Telecom Corporation"

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

[RegionalSettings]
LanguageGroup=1
Language=00000409

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

[Identification]
JoinDomain=HRSLAB
DomainAdmin=#######
DomainAdminPassword=#######l

[Networking]
InstallDefaultComponents=Yes


--
Vincent Lape



lukesh said:
Hi,
I don't want to prove you wrong but for the better understanding of the
issue can you please paste your sysprep.inf file and list your system
hardware here.

Lukesh

:

Yea, That is the one. Made sure answer file was correct. I did also
google
for over an hour before i posted.
--
Vincent Lape
Systems Administrator
Cardiac Telecom Corporation
800-403-7682 X 102


:

Hi Vlape,
Hope this is not the article which did not help you.
http://support.microsoft.com/?kbid=249690

Lukesh

:

After running setupmgr to create an answer file for sysprep i get
the
following error:
"An error occurred while trying to update your registry" when
running
sysprep. I have googled and found one MS KB doc however that is
not the
problem.

Windows 2K PRO Version 5.0 Build 2195 SP4
Logged in as local admin
no gp restricting reg edit.

TIA

--
Vincent Lape
Systems Administrator
Cardiac Telecom Corporation
800-403-7682 X 102
 
Back
Top