Swapping MB chipsets...saving OS

[Homerboy]

So I've inherited 2 REALLY crappy servers here built with totally generic bits and pieces. I've been putting off the inevitable and last night one of the PSUs fried and down time resulted. Obviously not ideal for office email servers and application servers.

So I've talked to the check writers, explained the ordeal and they are willing to fork out some cash. However, the trick is that to do it RIGHT I should be swapping out the generic MBs and lowly RAM too, not just PSUs, cases, HDDs etc.

The problem is that to redo all the applications and settings would be a logistical nightmare at this point. So, if possible, I'd like to preserve the OS installs on these servers while swapping out nearly everything on them.

If possible I'd like to jump from the Intel CPUs to AMD too, but I fear thats asking too much.

Any suggestions comments concerns?

 

[spyordie007]

It's certainly all possible, but on any server I recomend against it. If this is a server that matters get good hardware and build it right, this is not somewhere you should be cutting every corner to save money (because if you do it wrong it will cost more in the long run).

 

[Homerboy]

actually not trying to save "money" itself, but lots of time and reconfiguring. There are lots of apps that were set up LONG before me on these servers, and reconfiguring could turn troublesome, if not impossible.

I guess the right thing to do is get all new parts, start building and test but leave current server alone until the new one is reconfiged/setup 99% right.

Ugh... thats a long road ahead

 

[spyordie007]

I guess the right thing to do is get all new parts, start building and test but leave current server alone until the new one is reconfiged/setup 99% right.

Correct. Besides you could take this opportunity to learn the applications a little so you know what's going on. You should know enough about them so that if the server died entirely you could get a new server and restore from backups and be running

Good Luck

 

[n0cmonkey]

Ghost the drive. Read the FAQ. Restore if necessary.

 

[Homerboy]

agreed 100%... problem is the powers that be are the types that feel that an "IT/Sys Admin" should just be able to fix everything on the fly, knowing everything about anything that plugs in or has lights on it. Screw it... time for THEM to learn

 

[Sideswipe001]

Originally posted by: Homerboy
So I've inherited 2 REALLY crappy servers here built with totally generic bits and pieces. I've been putting off the inevitable and last night one of the PSUs fried and down time resulted. Obviously not ideal for office email servers and application servers.

So I've talked to the check writers, explained the ordeal and they are willing to fork out some cash. However, the trick is that to do it RIGHT I should be swapping out the generic MBs and lowly RAM too, not just PSUs, cases, HDDs etc.

The problem is that to redo all the applications and settings would be a logistical nightmare at this point. So, if possible, I'd like to preserve the OS installs on these servers while swapping out nearly everything on them.

If possible I'd like to jump from the Intel CPUs to AMD too, but I fear thats asking too much.

Any suggestions comments concerns?

Since you don't mention the OS, I'll make the jump and assume you're running Windows 2000 server or later.

What I'd do with 2000, is get it up and running again in the "old" configuration, long enough to BACKUP, and then run "Sysprep". You should shut it down, then install the hard drives into the new system. Sysprep should cause the OS to re-initiate setup to a certain degree, including searching for and installing device drivers.

If the new equipment has drivers that are built into Windows, it should come up again just fine.

 

[Homerboy]

good idea on the sysprep (yes win2k)
theres some limitation there though as ID like to go from PATA to SATA and the old MB obvipously doesnt have SATA ports.
Ill think of something.

In all honesty a clean start on these machines is likely best. Ill just build it side by side to the old machine and once 99% of everything is running right Ill flip them

 

[Phoenix86]

I don't really recommend this for servers, but your asking and you seem to know the risks. A clean setup is the best route.

Sysprep guide.

The write up is for XP, but the meat applies to W2K as well, make sure to get the right sysprep version.

I have never tried PATA > SATA. Make FULL backups prior. Good luck.

 

[Smilin]

Sysprep should NOT be used on a production machine. It is intended for a new installation that will be cloned.

What you should do:
Get a good backup.
Go read and follow KB article 249694 over at Microsoft.

 

[Phoenix86]

Originally posted by: Smilin

Sysprep should NOT be used on a production machine. It is intended for a new installation that will be cloned.

What you should do:
Get a good backup.
Go read and follow KB article 249694 over at Microsoft.

99% of all my posts on this forum have been made from a syspreped system. I have supported *thousands* of syspreped systems in production environments. Ever XP install on my network (under 1000) have *all* been syspreped. Your first statement is very misleading, if not flat out incorrect.

Sysprep is intended for *preconfigured* installations which, by definition are not "new". They have apps installed, that fact alone makes them not "new". The difference between an well used machine, and one that's installed today with 10 apps installed is very little, esp. on a server.

I don't really recommend it, but it's exactly what the OP is asking for. From my experience with sysprep it will probably work for what he's doing. I'd recommend a rebuild, but that isn't an option to them.

That's a pretty neat KB article, hadn't read it before... It looks like doing sysprep by hand with some additional steps for HAL types. Good read.

edit: speeling

 

[Homerboy]

rebuilding from ground up at this point. Via another thread found some good deals on a nice Dell server (2x2.8 Xeon) and I agree with you guys from the get go, a rebuild is the RIGHT way to do it... I was just being lazy I guess. Not to mention I should figure out the ins/outs of alll these (horribly god forsaken) programs anyways. GOod thing is the check writers have already bought my sales pitch, so I'm in.

Thanks.

 

[Smilin]

Originally posted by: Phoenix86

Originally posted by: Smilin

Sysprep should NOT be used on a production machine. It is intended for a new installation that will be cloned.

What you should do:
Get a good backup.
Go read and follow KB article 249694 over at Microsoft.

99% of all my posts on this forum have been made from a syspreped system. I have supported *thousands* of syspreped systems in production environments. Ever XP install on my network (under 1000) have *all* been syspreped. Your first statement is very misleading, if not flat out incorrect.

Sysprep is intended for *preconfigured* installations which, by definition are not "new". They have apps installed, that fact alone makes them not "new". The difference between an well used machine, and one that's installed today with 10 apps installed is very little, esp. on a server.

I don't really recommend it, but it's exactly what the OP is asking for. From my experience with sysprep it will probably work for what he's doing. I'd recommend a rebuild, but that isn't an option to them.

That's a pretty neat KB article, hadn't read it before... It looks like doing sysprep by hand with some additional steps for HAL types. Good read.

edit: speeling

I'm not saying it won't work. I'm just telling you the recommended way and the right way. My first statement is neither misleading nor incorrect. Sysprep documentation flat out tells you not to use on a box that's been in production for a while. It's intended to roll out clean installs (with apps of course) and that is all. I'm glad you feel well exposed to sysprep, imaging and "Setup" for windows but I don't think you have the same experience with this that I do.

Stick to the KB I recommended. I know the guy that wrote it and he's a pretty clever fella. It is NOT the same as doing sysprep by hand with some additional HAL steps.