SuperGumby
Tue Oct 25 17:44:25 CDT 2005
one further suggestion, but it's a longshot.
rename boot.ini on the original install. Windows 2000 or later, in the
absence of a boot.ini, will search the HDD for a windows installation to
boot. If the current boot.ini is not defining things in a manner consistent
with the disk config, as the new hardware sees it, removing it may help.
"SuperGumby [SBS MVP]" <not@your.nellie> wrote in message
news:OAkWsJb2FHA.744@TK2MSFTNGP10.phx.gbl...
> if the idea is minimal downtime, call PSS, the newsgroup is not the proper
> resource.
>
> I'm surprised (slightly, not overly) that the repair install didn't get
> you up.
>
> The next step would probably be to do a parallel installation, of just
> Win2K SP4, to the 2nd partition and start editing the registry of the SBS
> install, adding/removing/adjusting drivers based on the info from the
> parallel install. This will be a very long process with assistance via
> mail/news. You would want to ensure that the HAL being loaded in SBS was
> the same as that loaded by the parallel install, then of course drivers
> for the HDD subsystem. Again, PSS are likely to be of assistance.
>
> If we can't get her up and running, and you don't have a backup (actually,
> that question may not have been asked yet, do you have a complete backup?)
> I know of no way to extract the AD from just the files on disk, though
> really this _should_ be possible.
>
> "David" <David@discussions.microsoft.com> wrote in message
> news:A55492B6-4981-46C6-BB3A-D55E9F329B21@microsoft.com...
>> G'day Mick:
>>
>> Our goal here was to migrate SBS2000 to new hardware with minimal
>> downtime
>> to users. Your theory of installing the old hard drive into the new
>> system
>> and starting up in DSRM was great, but I'm still struggling to try to get
>> the
>> OS on the old hard drive to recognize the new system.
>>
>> Followed your instructions and went through the Repair process. Upon
>> reboot
>> Windows runs through initial "Opening Windows 2000"; the Windows 2000
>> Server
>> Family screen appears very briefly; then a blue-screen error message:
>>
>> STOP: 0x0000007B (0xEB42384C, 0xC0000034, 0x00000000)
>> Inaccesible_Boot_Device
>>
>> Reviewing the following document indicates that this may be caused by the
>> installation of a new motherboard with different chipset.
>>
>>
http://support.microsoft.com/default.aspx?scid=kb;en-us;822052#XSLTH3120120129120121120120
>>
>> I've followed the Repair process again, but still receive the same
>> blue-screen error message.
>>
>> Looks like we will be unable to get the old hard drive to boot.
>>
>> So, unless you there's a different fix for the Inaccesible_Boot_Device
>> issue
>> I'm back to my second question: What suggestions would you offer to
>> migrate
>> AD from the old drive to the new drive if I am unable to boot from the
>> old,
>> but can see old installation?
>> Thanks!
>>
>> David
>>
>> PS - "Where are you Supergumby?" was a rethorical question, much like the
>> title of the old, old TV-Show, "Car 54 Where Are You?"
>>
>> "SuperGumby [SBS MVP]" wrote:
>>
>>> OK, this first bit is IMPORTANT. Ideally, we use SBS media of the same
>>> SP
>>> level as the original system. If his original CD's are SBS with no SP we
>>> should try to identify whether SP1a was ever installed. NOTE, this is
>>> SBS
>>> SP1a, not just the Windows SP.
>>>
>>> and you only want one of the HDDs in the box for this procedure, on the
>>> first IDE channel, set as primary.
>>>
>>> IF it was either non-SP media taken to SP1a OR SP1a media we're set to
>>> go
>>> and just need the SBS SP1a CD1. Start the installation process (boot off
>>> CD1), you will be presented with two alternatives, recovery console or
>>> install windows, choose install windows, on the next screen(or maybe
>>> next
>>> again) you will be asked if you want to repair the current installation
>>> or
>>> install a new, choose to repair.
>>>
>>> BTW, if, in your other message asking where I am, you were actually
>>> asking
>>> for my physical location, I'm in Sydney, AU, and I'm a whore,,,,ummm,,,I
>>> mean, consultant, available to attend if required, at very reasonable
>>> rates.
>>> mickm at mickmalloy dot dyndns dot org, but please note: though it may
>>> be
>>> quicker for you to direct mail me, and it just so happens I don't have
>>> much
>>> on today (now about 07:30 Tues) I would prefer correspondence through
>>> the
>>> group so that everyone may benefit. I'll keep m' eyes on the thread.
>>>
>>> "David" <David@discussions.microsoft.com> wrote in message
>>> news:69739E76-DEEE-4EDA-B29C-485231AFDA5A@microsoft.com...
>>> > Sorry for the delay. Found that this issue was awaiting my return
>>> > from
>>> > vacation for a resolution. (Wonder why only the easy stuff gets done
>>> > when
>>> > you're out of the office?)
>>> >
>>> > Hard drive system on both old and new motherboard is IDE.
>>> >
>>> > Old drive is available and appears to have old installation of SBS2000
>>> > in
>>> > place.
>>> >
>>> > Connected old drive to nem mobo and attempted start in DSRM. System
>>> > crashed
>>> > in mid-load with blue screen error 0x0000007B "Inaccessible Boot
>>> > Device".
>>> > Ran CHECKDSK with no success. Unable to boot in Safe Mode to Command
>>> > Prompt.
>>> >
>>> > We did not build this system, and it was DOA so I'm unsure exactly how
>>> > the
>>> > hard drive was setup. Client indicates there were multiple partitions
>>> > on
>>> > boot drive and that it was mirrored to secondary drive. (Two old
>>> > drives
>>> > were
>>> > in box.) I suspect there was something hinky in the old partion and
>>> > or
>>> > mirror setup and thus it just won't work with the new motherboard.
>>> >
>>> > Question:
>>> >
>>> > What suggestions would you offer to migrate AD from the old drive to
>>> > the
>>> > new
>>> > drive if I am unable to boot from the old, but can see old
>>> > installation?
>>> >
>>> > Thanks for your response.
>>> >
>>> > "SuperGumby [SBS MVP]" wrote:
>>> >
>>> >> what sort of drive subsystem? (old and new)
>>> >>
>>> >> It's reasonable that if you can connect the old drive to the new mobo
>>> >> you
>>> >> _may_ be able to run up SBS. On ALL attempts to start with the old
>>> >> drive
>>> >> start in Directory Services Restore Mode. This, if it boots and there
>>> >> is
>>> >> a
>>> >> fair chance it will, will allow Windows to discover the hardware
>>> >> changes
>>> >> without attempting to load AD and certain other services (exchange
>>> >> etc...).
>>> >>
>>> >> If she doesn't BSOD on you you're well on the way to getting the
>>> >> system
>>> >> up.
>>> >>
>>> >> Once the changes to hardware have been detected, restart _in DSRM
>>> >> mode_ a
>>> >> couple of times and just leave her sitting there logged on for a few
>>> >> minutes, sometimes I've seen more changes detected after maybe 10
>>> >> minutes.
>>> >> When you're SURE she's detected all the changes _AND_ you've checked
>>> >> that
>>> >> your IPCONFIG is correct, restart normally.
>>> >>
>>> >> It's then a simple process to move to new drives. Let's see if we can
>>> >> get
>>> >> this far first.
>>> >>
>>> >> You might also want to throw the old drive and a spare into another
>>> >> box,
>>> >> use
>>> >> ghost or similar to 'image' the drive before we start doing anything.
>>> >>
>>> >> "David" <David@discussions.microsoft.com> wrote in message
>>> >> news:AA5E45D4-2658-4CAA-A993-2373E94F8FAC@microsoft.com...
>>> >> > Have a client who has SBS2000 running as a domain controller.
>>> >> > Motherboard
>>> >> > damage requires new hardware. We will install a new hard drive as
>>> >> > well.
>>> >> >
>>> >> > I have the original installation of SBS2000 on a hard drive. I am
>>> >> > planning
>>> >> > have a fresh install of SBS2000 on the new hard drive.
>>> >> >
>>> >> > Are there any migration tools that would help with the task? I'm
>>> >> > thinking
>>> >> > of a tool that would copy the user settings and Security Descriptor
>>> >> > information from the old hard drive with the original installation
>>> >> > of
>>> >> > SBS2000.
>>> >>
>>> >>
>>> >>
>>>
>>>
>>>
>
>
>