Reinstall W2K or SBS2000 as 'in-place' upgrade?

I recently attempted to transfer an image of W2K SBS2000 from a Dell
Poweredge 2400 with a single processor to another Poweredge 2400 which had a
dual processor.

In the original build I had a 8Gb disk which was partitioned into C and D
drives and a 16Gb E drive which was running Exchange and SQL.

As C and D drive were quite full I decided to add another 8Gb drive to the
new server and image C and D onto seperate physical drives.

Rather than image the E drive - I just physically moved it over from one
server to the other.

At first it seemed to have gone ok. I had to install multi processor
support for the dual processor, along with adding page file space (Windows
reported that it had to create a temp page file)

However, it just seems really 'buggy' now. The first few times I restarted
the server it would take 15-20 minutes to present me with the login prompt
and then a further 5 minutes of a blank screen after I logged in. It's not
as though I'm getting loads of BSOD or there is anything in the event log I
can go off. It just doesnt seem right. Various things seem amis - for
example I can't start Network and Dial-Up Connections sometimes, but other
times I can.

I would like to know if performing an in-place upgrade of Windows 2000 would
help or indeed if I could do SBS2000 this way too?

Jeff
Thu Aug 12 18:44:44 CDT 2004

I suggest you delete the pagefile and the ISA Cache, and any other virtual
memory files like that if you have such.

As a rule, if you get a boot the first time, and you reset the HAL and get a
boot the second time, you aren't having problems from the move of the
system.

You would want to make a full system state backup, and make an ERD while
requesting to backup your system files to disk. That will refresh the local
repair folder.

You should proably clear the Recycle Bin.

Verify that the NICs are bound in the correct order, LAN NIC first.

To answer your question, an inplace upgrade would likely not solve any
problems in this condition if the imaging program you used transfered the
files correctly. I wouldn't think that's the issue.

Start with the stuff I suggested above. If you aren't seeing any errors in
the logs, you probably have an issue that isn't file related.


"James Tarnat" <nonespecified@paranoid.co.uk> wrote in message
news:%23YL7UhffEHA.2460@TK2MSFTNGP12.phx.gbl...
> I recently attempted to transfer an image of W2K SBS2000 from a Dell
> Poweredge 2400 with a single processor to another Poweredge 2400 which had
a
> dual processor.
>
> In the original build I had a 8Gb disk which was partitioned into C and D
> drives and a 16Gb E drive which was running Exchange and SQL.
>
> As C and D drive were quite full I decided to add another 8Gb drive to the
> new server and image C and D onto seperate physical drives.
>
> Rather than image the E drive - I just physically moved it over from one
> server to the other.
>
> At first it seemed to have gone ok. I had to install multi processor
> support for the dual processor, along with adding page file space (Windows
> reported that it had to create a temp page file)
>
> However, it just seems really 'buggy' now. The first few times I
restarted
> the server it would take 15-20 minutes to present me with the login prompt
> and then a further 5 minutes of a blank screen after I logged in. It's
not
> as though I'm getting loads of BSOD or there is anything in the event log
I
> can go off. It just doesnt seem right. Various things seem amis - for
> example I can't start Network and Dial-Up Connections sometimes, but other
> times I can.
>
> I would like to know if performing an in-place upgrade of Windows 2000
would
> help or indeed if I could do SBS2000 this way too?
>
>

Rick
Mon Aug 16 13:46:33 CDT 2004

Over time, I have seen timing issues with W2K and WXP.... many time it is
related to firmware and drivers....

I suggest that you verify that your motherboard drivers are current and that
any other devices have current drivers. i.e. SCSI RAID controller. Even an
integrated NIC.

Oddly enough I recently had a problem like this on a WXPPro dell desktop and
the solution was to change the sequence of the driver installation of the
integrated video driver and the other motherboard drivers. The boot time
dropped from 3 1/2 minutes to 20-25 seconds.

I realize that you are talking SBS but it may be worth a look anyway.

Good luck

RickD

"James Tarnat" <nonespecified@paranoid.co.uk> wrote in message
news:#YL7UhffEHA.2460@TK2MSFTNGP12.phx.gbl...
> I recently attempted to transfer an image of W2K SBS2000 from a Dell
> Poweredge 2400 with a single processor to another Poweredge 2400 which had
a
> dual processor.
>
> In the original build I had a 8Gb disk which was partitioned into C and D
> drives and a 16Gb E drive which was running Exchange and SQL.
>
> As C and D drive were quite full I decided to add another 8Gb drive to the
> new server and image C and D onto seperate physical drives.
>
> Rather than image the E drive - I just physically moved it over from one
> server to the other.
>
> At first it seemed to have gone ok. I had to install multi processor
> support for the dual processor, along with adding page file space (Windows
> reported that it had to create a temp page file)
>
> However, it just seems really 'buggy' now. The first few times I
restarted
> the server it would take 15-20 minutes to present me with the login prompt
> and then a further 5 minutes of a blank screen after I logged in. It's
not
> as though I'm getting loads of BSOD or there is anything in the event log
I
> can go off. It just doesnt seem right. Various things seem amis - for
> example I can't start Network and Dial-Up Connections sometimes, but other
> times I can.
>
> I would like to know if performing an in-place upgrade of Windows 2000
would
> help or indeed if I could do SBS2000 this way too?
>
>