Re: URGENT - System State Restore - SBS
- From: "Les Connor [SBS Community Member - SBS MVP]" <les.connor@xxxxxxxxxxxx>
- Date: Sat, 6 May 2006 18:46:42 -0500
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??
.
- Follow-Ups:
- Re: URGENT - System State Restore - SBS
- From: Gregg Hill
- Re: URGENT - System State Restore - SBS
- References:
- Re: URGENT - System State Restore - SBS
- From: cjobes
- Re: URGENT - System State Restore - SBS
- From: Les Connor [SBS Community Member - SBS MVP]
- Re: URGENT - System State Restore - SBS
- From: Gregg Hill
- Re: URGENT - System State Restore - SBS
- Prev by Date: Re: Changing a .local name to a .com name
- Next by Date: Re: Any reason for 2nd NIC w/hardware firewall?
- Previous by thread: Re: URGENT - System State Restore - SBS
- Next by thread: Re: URGENT - System State Restore - SBS
- Index(es):
Relevant Pages
|