Windows Server 2000 to 2003 Upgrade

[schueymcfee]

We're running 2000 server and we've been thinking about upgrading to 2003.

Now, can you upgrade, or do you need to flatten and do a fresh install?

Aside from reinstalling drivers, noting passwords etc is there anything I'm forgetting about?

I'm almost sure the server has a problem because all the client machines try to download Google instead of opening it in a browser!

Any advice would be great.

[aldi]

Obviousley I don't know how many people are using it or how critical the data is or anything else for that matter, but I'd definatley go with a fresh install possibly on a new hard disk if you want to use the same box. If for no other reason than that if you try to upgrade the existing install and it doesnt work you would be in a tight spot. Whereas if you're working on a new disk and it goes pete tong you can just put the old one back and have a cup of tea. Are you on active directory?

[lockstock2sb]

I'd agree on the new disk/build idea - purely as an ass-saving exercise

Make sure your server can handle 2003 also before doing anything.

>> Edited by lockstock2sb on Wednesday 8th February 15:54

[schueymcfee]

That's a really good idea, why didn't I think of that!

[aldi]

Can't promise it'l fix your weird google problem though

[maddog-uk]

if you are running rmirrored raid why dont you just break the pair and put one disk aside for safety then let the pair rebuild.

At work we did a combination of upgrades in place and some complete rebuilds. If you do an upgrade in place there are a few things you need to run after if you want everything truly 2003 compliant.

But yes, check the spec and also what version are you going to 2003sp1, 2003r2 etc?

[agent006]

schueymcfee said:

I'm almost sure the server has a problem because all the client machines try to download Google instead of opening it in a browser! Any advice would be great.

I assume it's running some kind of proxy then?

[maddog-uk]

Sure sounds that way! Is it a small business server?

[schueymcfee]

Yep, small business server, running Windows 2K server, connected to D-Link router, Watchguard SOHO 5 firewall router, and Terrapin Multinet to manage the clients.

Basically all the clients were running directly through the SOHO to connect to internet, then their access was blovked for some reason, only the server had access, and the only way the clients could connect to the internet was by using the server as a proxy and Terrapin.

That's the first problem, my two new problems and the reason for upgrading is, the Google problem, and also there's some kind of weird cache thing going on, whereby if you log-in to E-Bay from one client machine, you can find that every other client machine can get into that account! Not Good at all, and I'm struggling to pin it down to a virus, or a problem with Terrapin.

[maddog-uk]

Well sbs has a proxy and so does Terrapin. How are the clients configured to use the proxy? Do they have automatically detect proxy set or is the proxy hardcoded?

[jamieboy]

TBH, I'd be inclined to do this in two stages - fix the problems, and the upgrade the working system.

Chances are the upgrade will introduce a few funnies anyway, and it'd be much better if you were starting from a solid footing.

[schueymcfee]

maddog-uk said:

Well sbs has a proxy and so does Terrapin. How are the clients configured to use the proxy? Do they have automatically detect proxy set or is the proxy hardcoded?

Proxy is hardcoded to server's network IP

[maddog-uk]

Alas I dont know terrapin but it sounds like that and ISA (if you have that edition of SBS) are having a fit.

[schueymcfee]

Okay have sorted the Google and cache problem, it was Terrapin after all!

Thanks for all suggestions