Re: URGENT - System State Restore - SBS

This references an issue with Dell OEM, perhaps that's the problem?

http://support.microsoft.com/kb/885191/en-us

Here's how to start recovery console for ws2003.

http://support.microsoft.com/kb/326215/en-us

Repair Installation:
How to Perform an In-Place Upgrade of Windows Server 2003
http://support.microsoft.com/kb/816579/en-us


And this <snip>

How to Repair Your Installation of Windows
You may be able to repair a damaged Windows Server 2003 installation by
running Windows Setup from the Windows CD.

To repair your installation of Windows, follow these steps: 1. Insert the
Windows Server 2003 CD in the CD-ROM or DVD-ROM drive.
2. If the Windows CD displays the What would you like to do? menu,
click Exit.
3. Turn off your computer, wait ten seconds, and then turn your
computer back on.
4. If you are prompted to start your computer from the CD, do so.

Note You must be able to start your computer from the Windows Server
2003 CD-ROM to run Windows Setup. Your CD-ROM or DVD-ROM drive must be
configured to do so. For information about how to configure your computer to
start from the CD-ROM or DVD-ROM drive, see the documentation that is
included with your computer, or contact your computer manufacturer.
5. After Setup starts, press ENTER to continue the setup process.
6. Press ENTER to select the option To set up Windows now, press
ENTER. Do not select the Recovery Console option.
7. Press F8 to accept the licensing agreement.

Setup searches for previous installations of Windows. . If Setup does
not find a previous installation of Windows Server 2003, you might have a
hardware failure.

Hardware failures are beyond the scope of this article. See a
computer hardware specialist for more help or try the Hardware
troubleshooter. For more information about the Hardware Troubleshooter, see
the Windows Server 2003 Help topic "Using Troubleshooters."
. If Setup does find a previous installation of Windows Server
2003, you may receive the following message:
If one of the following Windows Server 2003 installations is
damaged, setup can try to repair it. Use the up and down arrows to select an
installation. To repair the selected installation, press R. To continue
without repairing, press ESC.
Select the appropriate Windows Server 2003 operating system
installation, and then press R to try to repair it.
. Follow the on-screen instructions to repair the installation.

Notes . You might have to change the boot drive sequence in your
BIOS settings to successfully start your computer from the Windows Server
2003 CD. Contact the manufacturer of your computer, or see your
manufacturer's documentation, for more information.
. If you cannot start your computer from the Windows
Server 2003 CD, you might have a CD-ROM or DVD-ROM drive failure or other
hardware failure.

Hardware failures are beyond the scope of this article.
See a computer hardware specialist for more help or try the Hardware
troubleshooter. For more information about the Hardware Troubleshooter, see
the Windows Server 2003 Help topic "Using Troubleshooters."
. After you repair your Windows Server 2003, you may be
required to reactivate your copy of Windows Server 2003.




--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
----------------------
"Tell me and I'll forget. Show me and I'll remember. Involve me and I'll
understand." - Confucius


"Gregg Hill" <bogus@xxxxxxxxxxx> wrote in message
news:eYQjNNfcGHA.3352@xxxxxxxxxxxxxxxxxxxxxxx
Les,

That is precisely what I have done, but each time I choose a repair
installation, it says it cannot find a previous installation, or it says
it will delete the current Windows directory before it re-installs.

It is my understanding that an OEM CD will not do a repair installation
without deleting the current Windows folder.

Gregg Hill



"Les Connor [SBS Community Member - SBS MVP]" <les.connor@xxxxxxxxxxxx>
wrote in message news:OS4%237cWcGHA.1208@xxxxxxxxxxxxxxxxxxxxxxx
As I recall, you just boot from CD1 and follow the bouncing ball until
the existing OS if found, and you're asked if you want to do a repair of
the existing OS (or a new install). There's also the recovery console - a
kb search should get you all you need.

--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
----------------------
"Tell me and I'll forget. Show me and I'll remember. Involve me and I'll
understand." - Confucius


"Gregg Hill" <bogus@xxxxxxxxxxx> wrote in message
news:OIr7wTOcGHA.464@xxxxxxxxxxxxxxxxxxxxxxx
Les,

I keep seeing people refer to repair installations, which I have done
many times with Win98, but never have gotten to work with 2000 or
higher. Each time I try, it either says it cannot find a previous
installation, or it says it will delete the current Windows directory
before it re-installs.

How do you do a repair install? Does it require non-OEM CDs?

Gregg Hill



"Les Connor [SBS Community Member - SBS MVP]" <les.connor@xxxxxxxxxxxx>
wrote in message news:uGstWU4bGHA.3472@xxxxxxxxxxxxxxxxxxxxxxx
A restore to different hardware is going to be somewhat messy, and
generally would only be used for disaster recovery where there isn't
another option.

What you could try is, after the restore - and after the blue screen -
boot to your Windows CD (disk 1) and perform a repair installation.
This often succeeds, but you'll have to do some work in devman
afterwards to clean up non-present devices from the previous
installation. This includes NICs - and the non-present nics and now
invalid network configuration will likely cause a *very* long boot
time, but eventually the server should come up.

--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
----------------------
"Tell me and I'll forget. Show me and I'll remember. Involve me and
I'll understand." - Confucius


"Andy Wolsten" <AndyWolsten@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5D5440F0-66FC-4FC1-AE93-E73D7F44CF5A@xxxxxxxxxxxxxxxx
i cant remember exactly. im just rebuilding the server now to reattempt
the
restore.

Reading the article on SBS restore there are various things which are
disimilar between the current live server and the new test server. It
is a
completely different hardware set for a start, disk sizes, cpu etc,
but would
this affect the restore of the system state only?



"cjobes" wrote:

What is the next line under the stop error? 0x0000007b is normally
inaccessible_boot_device

Claus

"Andy Wolsten" <AndyWolsten@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:EC0A6A9E-72D5-483C-8365-B110CAD19BC7@xxxxxxxxxxxxxxxx
ok, i built an offline copy of my SBS server, booted in to
Directory
Services
Mode and performed a system state restore via NT backup from a
successful
System State backup we took yesterday

On reboot, when the win2k3 progress screen comes up the OS blue
screens

message:

STOP 0x0000007b (0xf789A63C,0xC0000034, 0x00000000, 0x00000000)
-(not that i expect anyone to understand this exactly of course)

any ideas??














.

Relevant Pages

  • Re: Changing Computer with XP
    ... BIOS-locked to a specific chipset and therefore not transferable to a new motherboard - check yours before starting), unless the new motherboard is virtually identical to the one on which the WinXP installation was originally performed, you'll need to perform a repair (a.k.a. in-place ... WinXP, like Win2K before it, is not nearly as "promiscuous" as Win9x when it comes to accepting any old hardware configuration you throw at it. ... On installation it "tailors" itself to the specific hardware found. ...
    (microsoft.public.windowsxp.basics)
  • Re: new computer/old harddrive install
    ... it said disk error so I put in the XP disk and tried repair and it took me to c:\windows\ and I have no idea what to do next?? ... Normally, and assuming a retail license, unless the new motherboard is virtually identical to the one on which the WinXP installation was originally performed, you'll need to perform a repair ... WinXP, like Win2K before it, is not nearly as "promiscuous" as Win9x when it comes to accepting any old hardware configuration you throw at it. ... On installation it "tailors" itself to the specific hardware found. ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: No repair option
    ... There is also some evidence that 'upgrade' media may not provide a repair ... How to Repair Your Installation of Windows ... You may be able to repair a damaged Windows Server 2003 installation by ...
    (microsoft.public.windows.server.sbs)
  • Re: Active Directory restore with disimilar hardware
    ... Our server had to have a new Mobo some time back (Windows Server 2003) ... I booted off the CD and ignored the first option to repait, ... I have done the inplace repair on new hardware of our ... press ENTER as if performing a new installation. ...
    (microsoft.public.windows.server.active_directory)
  • Re: No repair option
    ... How to Repair Your Installation of Windows ... You may be able to repair a damaged Windows Server 2003 installation by ...
    (microsoft.public.windows.server.sbs)