Exchange Upgrade 2007 to 2013

Hi Leo,
Inplace upgraded is not supported. You have to install a new windows server and Exchnage 2013 server in the same forest and move the mailboxes and public folders to the new server.
You need an additonal name in your certificate legacy.yourdomain.com so any Exchage2007 users connect to your common name it wll be redirected to legacy.yourdomain.com. You can ignore this if you move all mailboxes on a weekend.
You should have an additional A record legacy.yourdomain.com in your internal and external DNS.

Ths will help you
https://technet.microsoft.com/en-us/exdeploy2013/Checklist?state=3229-W-AQAEAAAAQAAAAAEAAAAAAAAAAAAAwAMAAAA~

Thanks, do I have to create a new domain and in that I have to install new AD server and Exchange Server?

-->Thanks, do I have to create a new domain and in that I have to install new AD server and Exchange Server?
no need new domain you just install Exchange 2013 in a new VM/hardwarebox in the same domain where your exchange2007 exists.

Thanks, any article which will list installing instructions of Exchange 2013 step by step?

You can go through this article series which will guide you through the whole process of migrating Exchange 2007 to 2013 including planning and configuring co-existence - http://techgenix.com/planning-and-migrating-small-organization-exchange-2007-2013-part1/

See the proper configuration of URLs for Proxy and Redirection - Exchange 2007/2013 CoExistence URLs
http://silbers.net/exchange-20072013-coexistence-urls/

Additionally, you may get hep from migration solutions like Lepide and CodeTwo to migrate easily and efficiently.

Hope this helps!

On Exchange 2007 do I have to apply any update rollups?

If you want to create an EdgeSync Subscription between an Exchange 2007 Hub Transport server and an Exchange 2013 SP1 Edge Transport server, you need to install Exchange 2007 SP3 Update Rollup 13 or later on the Exchange 2007 Hub Transport server.

Learn about the Exchange 2013 requirements that you need to know before you install Exchange 2013:
https://technet.microsoft.com/en-us/library/aa996719(v=exchg.150).aspx

Use this checklist to upgrade from Microsoft Exchange Server 2007 to Exchange Server 2013:
https://technet.microsoft.com/en-us/library/ff805032(v=exchg.150).aspx

Step-by-step guide for migrating from Exchange Server 2007 to Exchange Server 2013:
https://community.spiceworks.com/how_to/122658-step-by-step-guide-for-migrating-from-exchange-server-2007-to-exchange-server-2013

Hope this helps!

Thanks, we are going to install Exchange 2013 Enterprise SP1 (that's what we are licensed for) and current running Exchange Server is 2007
 V 08.03.0485.001.

Whats the benefit of having EdgeSynch Subscription between Exchange 2007 and 2013 SP1? Would it impact on the production Exchange 2007?

and in this article https://technet.microsoft.com/library/aa996719%28v=exchg.150%29.aspx under "Supported coexistence scenarios"
Exchange 2007 -->
Supported with the following minimum versions of Exchange:

• 1Update Rollup 10 for Exchange 2007 Service Pack 3 (SP3) on all Exchange 2007 servers in the organization, including Edge Transport servers.


• Exchange 2013 Cumulative Update 2 (CU2) or later on all Exchange 2013 servers in the organization.

Do I have to install that update rollup? means does it apply to migration?

I can only suggest you to update rollup because when you're upgrading your existing Exchange 2007 organization to Exchange 2013, there's a period of time when Exchange 2007 and Exchange 2013 servers will coexist within your organization.

To maintain this coexistence, I think you need to follow the checklist and system requirements.

I have read that Exchange 2013 extends AD environment, would it cause any changes to production Exchange server which is running 2007? do we have to avoid installing any specific roles?

I've done this recently and had no problems.  The changes to the AD schema are only relevant to Exchange and won't have an affect on the rest of your active directory. Once installed and configured correctly, Exchange 2013 will become the front end of your Exchange organization, and the Exchange 2007 server will only operate on the back end (except for OWA should you need it).  Then, once all of your mailboxes, public folder contents, etc., have been moved, you can decommission the Exchange 2007 server completely and remove it gracefully from your domain.

Thanks, "Exchange 2013 will become the front end of your Exchange organization" that wont take over the current Exchange 2007 until we make the required changes?

Do i add legacy host name before installing exchange 2013 or after (https://technet.microsoft.com/en-us/library/ee332348.aspx)?
Just thinking if i add before installing exchange 2013, would it impact on currently running exchange 2007?

I know it needs to be created, my question was does it needs to be done before i install exchange 2013 or after? And what are the implications of it on exchange 2007 once DNS names are created?

Thanks, so we cant install exchange 2013 now? Means it has to be installed when we plan to migrate the mailboxes? I just thought get it up and running because there will be firewall changes which needs to be done and MX record changes....also for migrating mailboxes we are going to use a tool (most probably priasoft)

Just to clear up that confusion for you:  When I said that Exchange 2013 becomes the front end, that means that after the Exchange 2013 install, you should immediately set your firewall to forward mail to the Exchange 2013 server, not the Exchange 2007 server.  The Exchange 2013 server will deliver email to mailboxes on the Exchange 2007 server and on itself, depending on where they are at the time.  Once you have all mailboxes/public folders moved, then you can do away with the legacy.domain.com URL for OWA and remove the Exchange 2007 from your domain.

so as soon as Exchange 2013 is installed, firewall changes needs to be done?

Bit confused about if I can install Exchange 2013 now and move mailboxes and do firewall changes on the weekend?

thanks.

Thanks, should I use the same external IP of exchange 2007 on new exchange 2013? and get a new external IP for Exchange 2007?
There are in total 5 countries which are in same domain same forest, in all 5 countries Exchange will be upgraded, so after we upgrade exchange in first country should we keep it active? for synch and legacy DNS purpose?

You need an additional IP for Exchange2007 and you need an additional name legacy.domain.com in your certificate.
i.e. after moving the mailboxes. New public IP will be pointed to legacy.domain.com (Exchnage server2007) for external access.

You need two external IP addresses, one for receiving email (port 25, SMTP) forwarded to the Exchange 2013 server and one for legacy.domain.com, forwarded to the Exchange 2007 server.  The one that's forwarded to Exchange 2013 will be for receiving email and also for users whose mailboxes have been moved to the new server to use for Outlook Web App and ActiveSync.  The one that's forwarded to Exchange 2007 will allow users whose mailboxes are still on that server to access Outlook Web App and ActiveSync. The users on the Exchange 2007 server will use "legacy.domain.com" for those purposes (or the new IP address).  This will stay in place until all users have been moved to the Exchange 2013 server, and then you can remove the "legacy.domain.com" reference.

Enough information to confirm an answer.