Monday, September 7, 2009

What is business justification going from Exchange 2007 to Exchange 2010

I remember myself having hard time to talk about going from 2003 to 2007 (-: , yet burning desire to implement exchange 2007.


The short story as the same question goes and comes back, the business reason why should anyone bring exchange 2010? I wrote many little articles to discuss why and will continue to write as I see myself more an more be implementing exchange 2010 than any other version ever before (-:

Exchange 2010 will simply save $$$$$ for your business and here are some of the major bullets how

  • Use cheap storage to provide San (DAS) direct attached storage to exchange, as I said several times Exchange is off the SAN plate first time in the history……..
  • Huge savings from expensive SAN , and single person will be able to take care of many things within the application without needing any third party software or tools
  • Less complexity since no other product is being used for high availability and archiving.
  • Exchange archiving will provide basic regulatory requirements, such as policy’s to implement security practices and satisfy auditing needs. E-mails older than 6 years ( archived e-mails cannot be deleted)
  • No third party utility to manage archived e-mail, all build into exchange application
  • Great looking menu, light fast OWA experience and outlook 2010 will add more joy into exchange 2010 journey.
  • True DR solution is build right into product, if companies choose to implement DAG ( data availability group) they are redundant , every single mailbox and its content it available if one server goes down, end user experience is a minute interruption and valuable messaging experience right comes backup.
  • Major schema changes implemented to mailbox tables, allowed huge I/O reduction , there is simply no need for SIS ( gone)
  • Better delegations for IT administrator, giving more options to end users (create DL and invite others) taking away heavy load from IT administrators.
  • Exchange 2010 is fully redundant right out the box just like active directory servers….. You have to take every single Exchange server down in DAG to stop end user getting their mailsEmbarrassed
  • Another 50 % I/O reduction, the Exchange application operation much lighter faster application working more efficient.

So have your management understand the $$$ saving part, true build  redundancy and providing mailbox to end user as big as 20 30 GIG so they never have to delete any single mail until get retire (-: and let  your management decided not too move !!!…………………….. (-:

I truly believe when it comes to cost reduction management gives quick decision , it has always been this way and wont change….



oz Casey Dedeal,

MVP (Exchange)
MCSE 2003, M+, S+, MCDST
Security+, Project +, Server +

Http:// (Blog)

Http:// (Blog)

Http:// (Blog


Mark Arnold said...

Generally a good article but you're being a bit Fanbois-ish.

LuisB said...

The savings may be there for a Small to Medium Business, but I can't see my customers 5K+ with this kind of Data Center footprint. Relative terms, "Cost" and "Complexity", are actually raised significantly.

Each environment is different, and this new "business justification" does not apply to everyone.

Oz Casey Dedeal said...

I have to be disagree with you, exchange 2010 is bringing much less complexity if you really look at it the futures, redundancy+ archiving faster lighter application, better improved GUI, smarter approach , takes unnecessary load off the helpdesk, creating groups etc. is given to end user, message tracking end user tools etc. I will be implementing exchange 2010 (hopefully) 100K + environments and I ensure you there you see the most saving.
The biggest savings is going to be in the enterprise network scenarios.

joseph said...

What if some upgrade to trial exchange 2010 and then dont wanna keep it, would it hurt anything during reverting back to 2007.