learning Exchange 2003 and 2007

[Pants]

Has Exchange Server changed so much from 2003 to 2007 that I should read a book on both 2003 AND 2007 Exchange server?

Maybe I should just forget about 2003 and learn 2007 since 2003 support is ending in 2015, but then again, that's business I might loose since people are still going to be using it, most likely for a while after.

 

[YeOldeStonecat]

I'd learn both, yeah. Exchange was quite similar from 5.5 to 2000 to 2003....good product. 2007 got stupid..I hate it with a passion, they took away so much ease of management. 2010 looks similar but much more functional.

 

[dbdawn]

I would learn 2003 as well as 2007 and 2010. I have clients with all three versions of exchange.

 

[Pants]

I would learn 2003 as well as 2007 and 2010. I have clients with all three versions of exchange.

Why use different versions in the same company (client) ?

 

[YeOldeStonecat]

Possibly means....across all of the clients...some are on 03 some are on 07 some are on 10.

Although at times, techinically we'll have a client on two versions at the same time...for a long term migration.

 

[dbdawn]

Why use different versions in the same company (client) ?

YeOldeStonecat is correct. There are multiple clients with varying versions of exchange. I do have one client that has a mixture of 2007 and 2010 running as part of a migration though.

 

[Pants]

Why would migration take so long.. Is it because the company can't afford the labor for doing it all at once?

 

[YeOldeStonecat]

Why would migration take so long.. Is it because the company can't afford the labor for doing it all at once?

Sometimes there are reasons to take your time. Suppose it's a wide spread company? Or you can just go it several hours at a whack? Some staff that travel a lot and you can't get to them until they're in. Company changeover.

I have one client I moved to Exchange 2010 over a year ago. Moved them from the Exchange 03 built into their SBS. Right now technically their Exchange 03 is still running..although just...not really used. New DC in place. Will "retire" SBS03 in about 1 more year at current plans...still providing some other functionality.

 

[Pants]

Should basic support for Exchange include migration ? Is migration a generally difficult process that would merit higher hourly rate?

 

[dbdawn]

Should basic support for Exchange include migration ? Is migration a generally difficult process that would merit higher hourly rate?

I classify that as a project and I charge more for projects.

 

[frederick]

Migration is a project, totally agree with that.

Long-term migrations are also easier as bugs are worked out without anything being put in to jeopardy. Short migrations tend to lead a wall of issues, that all come at once, and everything is going to hell. With a long-term migration, as a bug appears, the client can still work without much disruption, and you can get the bug fixed.

Some clients like to still use the same 3rd party software from 2003, however, server 2007+ doesn't accept it blindly, and therefore there will be conflicts that will need to be resolved.

Long-term = easier to manage, and problems aren't major
Short-term = more difficult to manage as so much is happening at once, all the problems you could encounter you do...and tends to add time to the overall project that ends up costing you money

 

[Pants]

great wisdom!

 

[YeOldeStonecat]

Should basic support for Exchange include migration ? Is migration a generally difficult process that would merit higher hourly rate?

We treat server migrations outside of fixed monthly contracts....so it's either hourly rate or a quoted price for that project.