Upgrade to Exchange 2010 from Exchange 2003 Sp2

[said07]

I have not taken a class yet but I would like to have an idea from the experts before.
I have two 2003 sp2 Exchange servers in Fe/be config with about 120 mailboxes hosted both on Windows 2003 sp2 servers and both are Vms. My hardware is 64bit capable.
we also provide Owa access and do use Public Folders. Only few on the network have the 2007 Outlook client the rest uses 2003 Outlook
Can someone tell me please what route to take to migrate to Exchange 2010?

Thanks for your time.

 

[TekkieDave]

You can migrate mailboxes from 2003 directly to 2010. You basically just need to prep the domain for the 2010 box, install the server, and then move the mailboxes from one to the other.

I'm pretty sure 2010 can support Outlook 2003, but you might want to check out what to look for - compatability wise.

 

[58sniper]

To transition to 2010, you'll need the 64bit hardware (not the hardware you're currently using). I'm assuming you're going to migrate to a single server for 2010?

As for Outlook, you're fairly safe, with the exception of the 2010 archive feature. That's not available to users using Outlook 2003 or 2007.

For public folders, you should begin researching an eventual migration away from them as they are considered a fairly deprecated feature. But they do exist in 2010 - but with no real new features.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[said07]

Thanks to all.
58sniper: Do I understand that Front-end/back-end is no longer needed with 2010?

 

[58sniper]

For 120 users, it was never a requirement. Even in 2003.

The need for a front end/back end scenario comes from a scalability perspective. You could separate the roles to separate machines if you really wanted to, say, for scalability by using multiple servers and load balancers.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[ntinlin]

I would upgrade your clients to OL2007. Although you now have to pay extra for the CAL's for it unlike EX2003 and previous.

OL2003 DOES work but it has niggling problems with new mail notify etc.

If I recall correctly there was an article on MSExchangeTeam.com about using OL2003 against 2010.

Hardest thing to get ones head around is the requirement for certificates I think. Can be a pain to get set up properly if you can't just use the Exchange internally generated ones.

Neill

 

[58sniper]

If you're going to upgrade the clients, it doesn't make sense to go to an outdated version - especially since 2007 doesn't support the archive. Go to Outlook 2010. Lots more functionality and synergy with Exchange 2010.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[ntinlin]

Very true Pat.

Although he's presumably got a stable build of OL2007.

Might be quicker to get that out to everyone than waiting for an Office 2010 project.
I know it would be in my company.

Neill

 

[said07]

Yes, I 'd rather go 2010 client strait.
I did distribute 2003 client with a transform while back in 2004. Is it still possible to do a similar thing?
Customize the client and distribute it via gpo?
Thanks

 

[58sniper]

You don't need a transform file. If your autodiscover is working fine, the client will auto configure.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[said07]

58Sniper - Thanks for the help.
How about distributing the client to the user? Can use an msi with a gpo to push out?

 

[58sniper]

I don't see any reason why not. System Center Configuration Manager could also be used. But an .msi *should* be possible (disclaimer: I haven't rolled out 2010, as another team does that).

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[said07]

Thanks 58 sniper. I will give it a shot when I am at that point and let you know how it went.