Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Exchange 2003 vs Exhcnage 2007... Upgrade or leave alone 1

Status
Not open for further replies.

reynolwi

IS-IT--Management
Sep 7, 2006
452
US
Ok... it was "suggested" like things normallly are that we should upgrade our exchange server to exchange 2007. I currently have 1 exchange 2003 standard server running in the enterprise for just under 30 users, but the boss seems to think that it should be upgraded to exchange 2007. I am against this right now, but i know in the future (much later) i should look into it. What are the pros to exchange 2007 and just how hard is it to upgrade to exchange 2007. I told him id atleast look into it, but i dont want to mess with anything right now because it is working perfectly. Im just being curious and trying to get a little input.

Wm. Reynolds
RRWDS | TxPSS


- - - - - - - - - - - - -
Network Error:
Hit any user to continue
 
if it ain't broke don't fix it.

Exchange 2007 require a lot of powershell use to do many of the same tasks you could do in Active Directory Users and Computers and the Exchange Administrator. I just deployed my first EX2K7 server and it was a pain in the a$$ finding out where to do all the things I used to do in EX2K3. That being said, 2K7 is mighty fine peice of software and I do recomend it, when there is a business need. I like the fact that 2K7 no longer relies on the Windows 2003 SMTP service. It sure is easier to not have an open relay. There aer quite a few other things I like also, but I wouldn't upgrade a working productio 2K3 system unless I was either bored or had a darn good business reason to. 2K3 works just fine.

It is what it is!!
__________________________________
A+, Net+, I-Net+, Certified Web Master, MCP, MCSA, MCSE, CCNA, CCDA, and few others (I got bored one day)
 
Don't forget you will need to replace your operating system as well - Exchange 2007 requires Windows 2003 64bit version.
 
I unfortunately had to install a 2k7 server. It was chosen and bought before I came online with this project. If I was asked beforehand I would say DONT buy exchange 2007 till they at least release SP1 for it. Thy rushed it out the door without completing the management tools. Like stated above you need to use allot of power shell.



Gb0mb

........99.9% User Error........
 
You don't need a lot of powershell for a basic install, and those you do need are listed clearly in the doco. I installed CCR and several hub/CAL servers and I think I only needed 1 powershell command, and that was when I had to move a database/logs onto network drives. There are GUI tools available which can be used to do things previously requiring powershell to do most things, and SP1 wil provide more native gui finctionality. But it's not a show stopper for installing 2007 now.
 
No upgrade path available between 2k3 - 2k7. Only migration is available because you must change hardware. But now since you already have E2k7 why not use it? It has many neat features like LCR, disclaimers, journal rules, etc.
 
and CCR, AutoDiscover, Edge transport, etc....

Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
 
For anyone else looking at this, also check that there are x64 drivers for any exotic hardware you have. 32 bit drivers will NOT work.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top