Re: OSD Upgrade from Windows 2000 Pro ends to a BSOD

The STOP 0x0000007B appears to be because the machine you are deploying to
has a different mass storage controller than the reference system. In your
Sysprep.inf, did you include a "[SysprepMassStorage]" section and a
"BuildMassStorageSection=yes" directive? This would enable your image to be
deployed to most systems without any further effort (subject to HAL
limitations).

-Michael Niehaus
Systems Design Engineer
mniehaus@xxxxxxxxxxxxx
http://www.microsoft.com/desktopdeployment
This posting is provided "AS IS" with no warranties, and confers no rights.


"Papastef" <Papastef@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:DD119ED1-3045-4697-BABA-46892FA7316F@xxxxxxxxxxxxxxxx
> Hi all
>
> I'm having a problem with OSD when I try to upgrade an existing Windows
> 2000
> Pro system. Here is my lab set up:
>
> SMS 2003 SP1 on Windows 2003 server
> AD extended
> One Primary site server with all system roles
> RIS server (Windows 2003) configured to boot OSD image deployment cd
>
> Here is the steps I followed:
>
> Created a reference system, followed the procedures described in the OSD
> guide to capture a wim image.
>
> Created a OSD package, program and advertisement
>
> The client receives the advertisement and completes successfully validate,
> preinstall, capture user state (Usmt 2.6 configured in program) phases and
> then system restarts.
>
> Then it tries to boot in WinPE for the install phase and I receive a BSOD
> with the following description:
>
> A problem has been detected and windows has been shutdown to prevent
> damage
> to your computer. If this the first time.
>
> Technical information:
>
> *** STOP: 0x0000007B (0xF8984528, 0xC0000034, 0x00000000, 0x00000000)
>
> I tried the above procedure to an HP DC7100 workstation and to a vmware
> machine and I get the same.
>
> If I try to run the same OSD package, program and advertisement to a
> Windows
> XP system (physical and virtual) everything works fine.
>
> Any Ideas?
>
> Thanx in advance.
>


.

Relevant Pages

  • Re: OSD/PE05 Ramboot via RIS freezes systems everytime
    ... We recently had a very similar problem with booting OSD from RIS. ... Although I still don't understand why the systems do not freeze ... Created a customized version of Windows PE 2005 using the "config.hta" ...
    (microsoft.public.sms.tools)
  • Re: Do I need to create an image for each computermodel ?
    ... On item #1, OSD will not change the HAL itself, so it should be deploying ... you will need to create a different OSD package ... > 2) Problem with IDE drivers. ... but OSD will not check hardware and change the ...
    (microsoft.public.sms.tools)
  • Re: OSD Image install issue
    ... It looks like you have updated the Windows PE being used by OSD (as the ZTI ... >> server STPap01, ... >> object Utopia Sound Scheme pointed by object ...
    (microsoft.public.sms.tools)
  • Re: Upgrading to WinXP SP2 - Which way is best?
    ... Deploying Windows XP Service Pack 2 using Software Update Services ... I need to update to WSUS and WinXP SP2. ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: Using Client side extensions in a 2003 environment
    ... We removed Vista from all our desktops so I'm only needing the XP process. ... I'll work on deploying this. ... Windows Server 2003 environment and XP/Vista clients? ... be deployed with Software Installation. ...
    (microsoft.public.windows.group_policy)