In-place upgrade fails after restore from different hardware

I'm moving a Win2000 Server installation from an old machine to a new
one. I followed the procedure in KB 249694, and I perform an in-place
upgrade following the restore from backup.

During the hardware detection phase of setup, I get a BSOD complaining
about cdfs.sys. A clean install of Win2000 on the new h/w works fine,
so there is something during the h/w enum process that is failing. A
subsequent Repair attempt fails as well.

On my next attempt, I will try looking for any hidden devices and
uninstall them. Does anyone have any other suggestions for cleaning
up the restored backup before attempting the in-place upgrade
following restore to different hardware?

I have always found the best solution when moving across hardware platforms
to be a clean install followed by recovery of data and reinstallation of
applications. You run into so many hardware enum differences that Windows
2000 never really run clean IMHO after the inplace.

--
Joseph Conway [MSFT]
Windows 2000/2003 Server group

This posting is provided "AS IS" with no warranties, and confers no rights
"Zanoni" <zan@nospam.com> wrote in message
news:3fl4305e33q9ldmelihptldmg2r1c9h1q9@4ax.com...
>
> I'm moving a Win2000 Server installation from an old machine to a new
> one. I followed the procedure in KB 249694, and I perform an in-place
> upgrade following the restore from backup.
>
> During the hardware detection phase of setup, I get a BSOD complaining
> about cdfs.sys. A clean install of Win2000 on the new h/w works fine,
> so there is something during the h/w enum process that is failing. A
> subsequent Repair attempt fails as well.
>
> On my next attempt, I will try looking for any hidden devices and
> uninstall them. Does anyone have any other suggestions for cleaning
> up the restored backup before attempting the in-place upgrade
> following restore to different hardware?

On Thu, 19 Feb 2004 07:40:18 -0500, "Joseph Conway [MSFT]"
<joscon@online.microsoft.com> wrote:

>I have always found the best solution when moving across hardware platforms
>to be a clean install followed by recovery of data and reinstallation of
>applications. You run into so many hardware enum differences that Windows
>2000 never really run clean IMHO after the inplace.

The expense of reinstalling everything would be very high -- it's a
dev platform with *many* 3rd-party controls and products installed. I
went through the HW Wizard and exposed hidden devices, deleted
anything that appeared left over from the old system. After this, I
booted off the CD and did a Repair. I chose this approach instead of
the in-place upgrade, because the latter had failed before.

The Repair process completed after the "Examining the disks" phase.
When it rebooted, I got the normal boot menu, and Window 2000 started
with the normal login screen. There was no further setup phase or
hardware detection. I wonder if this means the Repair setup found
nothing to do? Should I still try an in-place upgrade?

Well the problem with all of this comes down to the registry. We dont really
touch it a whole lot on in-place upgrades unless we detect a change that
needs added. So whats going to happen is the inplace is going to leave you
where you are right now.

--
Joseph Conway [MSFT]
Windows 2000/2003 Server group

This posting is provided "AS IS" with no warranties, and confers no rights
"Zanoni" <zan@nospam.com> wrote in message
news:inu930p09t1poir8b4l9arbprss1ivq6uh@4ax.com...
> On Thu, 19 Feb 2004 07:40:18 -0500, "Joseph Conway [MSFT]"
> <joscon@online.microsoft.com> wrote:
>
> >I have always found the best solution when moving across hardware
platforms
> >to be a clean install followed by recovery of data and reinstallation of
> >applications. You run into so many hardware enum differences that
Windows
> >2000 never really run clean IMHO after the inplace.
>
> The expense of reinstalling everything would be very high -- it's a
> dev platform with *many* 3rd-party controls and products installed. I
> went through the HW Wizard and exposed hidden devices, deleted
> anything that appeared left over from the old system. After this, I
> booted off the CD and did a Repair. I chose this approach instead of
> the in-place upgrade, because the latter had failed before.
>
> The Repair process completed after the "Examining the disks" phase.
> When it rebooted, I got the normal boot menu, and Window 2000 started
> with the normal login screen. There was no further setup phase or
> hardware detection. I wonder if this means the Repair setup found
> nothing to do? Should I still try an in-place upgrade?
>