• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Keep Win2k Server or Upgrade to Win2k3

A

akshatp

Diamond Member
Basically, the server running our Exchange server is dying, and I have placed an order for a brand new Dell PowerEdge to be delivered in the next two weeks.

I have some options as to what to do OS-wise.

1) Basically duplicate the existing server, by performing a re-install of Win2k and Exch2k and move the data store to the new server, give it the same name, DNS settings, IP address etc and switch the Ethernet cable when ready.

2) Upgrade to Win2k3 Server and Exch 2k3 and give the server a new name, migrate all of the mailboxes, and add the server to the network as a new member server, and then retire the old server.

3) Ghost the existing server to the new hard drive for the Dell PE server.. Would this even work???


What would you do? Im looking for advice here. Money for the new OS and Exchange is already approved. This is for a company with 6 employees, 2 of them P/T.
 
Don't ghost the OS thats for sure. That'd probably result in a whole world of pain.

If you have the budget approved, then it would be a good time to migrate to w2003 and exch2003 just for the improvements and extra security features they provide.
 
BY FAR, the easiest thing to do would be to leave your current server alone, and install Windows Small Business Server 2003 on the new Dell. SBS 2003 would give you tons of extra features, including remote access, automated backups, and daily performance monitoring. And it will cost you less than using standard Windows Server 2003 and Exchange 2003.

The simplest thing to do, with only six employees, is to create a new domain and new accounts, copy your data files over to your new data drive, re-set your file permissions, and migrate the mailboxes to the new Exchange Server with .PST files. The only tricky part is migrating user profiles from the old Domain to the new Domain, but you just need to be prepared to do it correctly.

Before installing SBS, I strongly suggest you do some reading on the correct way to do it. Install SBS, join a test client PC to the Domain. Play with it.

SBS setup is NOT done the same way as standard Windows Server, and if you follow your instincts, you'll probably not do it correctly. You MUST use the Wizards and follow the directions. Trying to take "shortcuts" and do things manually can create a mess.

"If there's a Wizard in SBS for what you want to do, use the Wizard".
 
I was just recently faced with the same dilemma, and went with a new server with 2003 SBS, and another server with 2003 as our TS/application server.

This was for 15 users, and I followed pretty much the exact same thing RebateMonger has said, and used a Pix 501 instead of ISA. Using ExMerge then importing the PSTs was a snap.
 
I forgot to mention. There is already a second TS running Win2000 also, and I would prefer not to mess with that server at all if possible. Correct me if I am wrong, but doesnt SBS need to be installed as the first server of an organization? I wouldnt be able to add the SBS to the existing domain, correct?
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top