Exchange 2013 / 2007

Would there be any disruption in the ActiveSync and OWA services? if I deploy new exchange 2013 server in a VM with Windows 2012 and just keep it active for a week before actual migration or before applying any certificate services or before changing any routing and DNS.



Our emails comes from inbound securence filter. I hope if the public and private IP forwarding does not know about new Exchange the old exchange should continue to work, but I skeptic after seeing article about Exchange 2013 SSL automatically trying to proxy services after it was introduce to existing environment
LVL 4
pchettriIT DirectorAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Amit KumarCommented:
if you don't change your public IP and DNS record to Exchange 2013, so there will not be any issue while introducing new servers. You can apply certificates as well on Exchange 2013 it will not effect anything.

Just to remember don't point internal/external DNS record for OWA/Autodiscover/ActiveSync/OA to Exchange 2013 until you are ready to start actual migration.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
pchettriIT DirectorAuthor Commented:
Thanks for your quick reply...

I am planning to change external and internal DNS only after introducing new certificate and after adding _autodiscover SRV record to resolve unregistered name. Once I know, it works fine with test user and internal DNS then I will add record to external  DNS for_autodiscover SRV, and add forwarding on firewall.
0
Amit KumarCommented:
Just remember minimum supported requirement.


Supported with the following minimum versions of Exchange:

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

Before migration Exchange 2013 should be installed with mentioned CU or later version:

2. Exchange 2013 Cumulative Update 2 (CU2) or later on all Exchange 2013 servers in the organization.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.