Exchange 2010 upgrading first time (co-exist with 2007)

[irsprint84]

I ve read many guides and I m confident to start upgrading from 2007 to 2010 there is one thing I m abit worried/ confused by. As soon as I install exchange 2010 will it take precidence immediately? I m worried because I will have to change all the DNS entries and I dont want much email downtime.

 

I also have my MX record (webmail) pointing to server05.school.local so should I change that to newexchange.school.local or have two mx records?

[sukh]

I ve read many guides and I m confident to start upgrading from 2007 to 2010 there is one thing I m abit worried/ confused by. As soon as I install exchange 2010 will it take precidence immediately? I m worried because I will have to change all the DNS entries and I dont want much email downtime.

 

I also have my MX record (webmail) pointing to server05.school.local so should I change that to newexchange.school.local or have two mx records?

 

1. Installing Exch 2010 wont have any effect on your 2007 env unless you start to move users acorss to it or start to change DNS/publishing from 20007 to 2010.

2. Install Exch 2010, make sure youre happy with it then you can switc over your MX records to 2010 for mail delivery.

3. Webmail is different and you need to consider this too. Eihter a migration over the weeked or co-existence scenario. Depends on your deployment/migrations stratgey.

[irsprint84]

I was told when I install exchange 2010 it will ask me to 'co-exist' so you're saying I can install exchange 2010, tell it to 'co-exist' but if I do try and move anything/ change DNS the exchange 2010 will happily sit there doing nothing?

[sukh]

1. You can install Exch 2010 and all the roles, (CAS/HUB?MBX). Exch will create the InterOP connectors and sit there and do nothing.

2. Only if you start to move users, then Exch 2010 will be used, i.e mai routing to 2007 users and you will have to create a send connectot to the internet.

3. If this moved user on Exch 2010 tries to access OWA externally, then this will need to be setup.

4. This is why is depends, if you plan to move all users to Exch 2010 in one big hit over the weekend or over a period of time. If over a time and you want all functionality/service there, then you will have to setup co-exist env for OWA, EAS, OA etc...

5. Here' some links you should read - Upgrading Outlook Web App to Exchange 2010 - Exchange Team Blog - Site Home - TechNet Blogs & Exchange 2007 - Planning Roadmap for Upgrade and Coexistence: Exchange 2010 SP1 Help

[irsprint84]

So just lastly (Just being careful) as soon as I move one user to exchange 2010 I should point my DNS to the 2010 server, if a 2007 user hits that server it will direct them to 2007?

[sukh]

1. You should setup your DNS beforehand, - setup the legacy namespace beforehand

2. Run through this - Exchange Server 2010: Exchange 2010 SP1 Help

3. OWA access depends if its from external or inernal and if you want to co-exist?

[irsprint84]

Hum.. I might just do this over a weekend

 

Just seems so confusing trying to get it to run side by side

Edited September 13, 2011 by irsprint84

[sukh]

then you dont need to worry about the legacy name space and just make sure you switch over your public dns IP to pont to the new 2010 server and amened your firewall rules, and you mx records, create your send connectors and youre done.

 

If using PF folders replication then, and setup your OAB

[irsprint84]

So one last bit then (I m just being careful!) I can install 2010 on another server and do nothing more than exchange windows update, keep all dns records, webmail configs pointing to 2007 and nothing will be different?

[sukh]

So one last bit then (I m just being careful!) I can install 2010 on another server and do nothing more than exchange windows update, keep all dns records, webmail configs pointing to 2007 and nothing will be different?

 

Yes, nothing will be different.