Single name space in between Exchange 2010 and 2013

Hi,
In my current environment I have 2 Exchange 2010 servers with DAG no CAS NLB. I installed Exchange 2013 with 2 CAS with WNLB and 2 Mailboxes with DAG. The main requirement is to configure Single name space to access in between Exchange 2010 and Exchange
2013. On Exchange 2010 DAG there is a URL using is owa.domain.com and I also configured in Exchange 2013 all the virtual directories with this name owa.domain.com but having an issue that when I open explorer and use the owa.domain.com URL the user on Exchange
2013 gets their mailbox but user on Exchange 2010 gets error HTTP 403 blank page.
I observed that in Exchange Organization settings CAS settings one server OWA, ECP etc shows their internal external URL but the other server unable to open the OWA, ECP URL and give error message that "An IIS directory entry
couldn't be created. The error message is Access is denied. HResult = -2147024891"
Please guide how to resolve this issue and use the same name URL in Exchange 2010 and Exchange 2013
Thanks,

Hi,
See the below brief:
User will connect to mail.contoso.com as his namespace endpoint. CAS2013 in Site1 will authenticate the user, do a service discovery, and determine that the mailbox version is 2010 and is located within the local AD site. CAS2013 will proxy the
request to an Exchange 2010 Client Access server which will retrieve the necessary data from the Exchange 2010 Mailbox server
Go through the full blog for better understanding of the redirection.
Client Connectivity with Exchange 2013
Hope you have changed your DNS records to direct connections only to your new Exchange 2013 server. You'll move the host names (for example, mail.contoso.com) users have been using to connect to Outlook Web Access, Autodiscover, and so on, from your
Exchange 2010 server to your Exchange 2013 server. When an Exchange 2010 user tries to open their mailbox, the Exchange 2013 server will proxy their request and communicate with the Exchange 2010 server on their behalf.
Configuring DNS includes the following:
Change the primary host names, such as mail.contoso.com, autodiscover.contoso.com, and owa.contoso.com (if used) to point to the external, publically-accessible, IP address of the Exchange 2013 Client Access server with your public DNS provider.
Change the primary host names, such as mail.contoso.com (or internal.contoso.com if you're using different internal host names) and owa.contoso.com (if used) to point to the internal machine name of the Exchange 2013 Client Access server on your internal
DNS servers.
NOTE- Go through the Exchange Deployemnt Assitant - Configure DNS Records section
Regards,
Satyajit
Please“Vote As Helpful”
if you find my contribution useful or “MarkAs Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

Similar Messages

Mail is Slow between Exchange 2010 and 2013 During Co-Existance Transition

Hello,
I recently migrated from a single Exchange 2003 server to a single Exchange 2010 server
I am now trying to Migrate from Exchange 2010 to Exchange 2013.
I have a test user on Exchange 2013, and Internet Mail works fine and quickly both inbound and outbound.
However, when I try and send between a 2010 user to my 2013 user, delivery takes around 10 minutes.
On the 2013 server I see health check messages, and my 2010 user's message stuck in retry status. The messages eventually clear and the mail is delivered. Any ideas what is causing this delay?
In terms of connectors I have all the defaults. And I created 1 for internal relays from devices. Which works fine.
I have two Exchange 2013 servers configured in a DAG, but I don't have a load balance in place as of yet. So only server 1 is being accessed as the CAS.
Thanks

Hi,
According to your description, the mail flow is slow only between Exchange 2010 and Exchange 2013 server. If I misunderstand your meaning, please feel free to let me know.
If yes, I’d like to confirm if there are multiple NICs on your Exchange servers. And you can refer to the following thread:
http://social.technet.microsoft.com/Forums/exchange/en-US/66f0629f-21fb-444b-b3f1-99ed8a4f52b2/slow-mail-flow?forum=exchangesvrsecuremessaging
We have ONLY 1 network adapter, but if we select "All network adapters" instead of Hyper-V, we will get delays.
Thanks,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Angela Shi
TechNet Community Support

Exchange 2010 and 2013 coexistence Internal and external URL

Hi all,
been reading alot of threads about Outlook anywhere and virtual directories in co-existence exchange 2010 and 2013.
Still i dont get any smarter.
Here is scenario:
Exchange 2010
Cas1
Cas2
Mailbox1
Mailbox2
Casarray is Exchange.casarray,com ( internal dns pointed to CAS1 in exchange 2010).Seems like by default both exchange 2013 cas servers are added to the casarray.
Exchange 2013
CAS+Mailbox
Cas+Mailbox
DNS
mail.exchange.com pointing to VIP (kemp loadbalancer)
Autodiscover ( pointed to same vip ,kemp load balancer)
Outlook anywhere on all servers (2010 and 2013)
Internal ( pointing to VIP on Kemp)
External ( pointing to external IP,then it passes firewall that again passes to kemp)
Problem we are having is when migrating users from Exchange 2010 - 2013.
Users using Outlook 2010
restart of outlook and mail works fine.
OWA works fine
Active sync fails ( need to inherit permission of users AD object),wait couple of hours then mobile can sync again.)
Users using Outlook 2013
Outlook in disconnected status,only fix is to create new profile.
OWA works fine
Active sync fails ( need to inherit permission of users AD object),wait couple of hours then mobile can sync again.)
Question is,what should be set for internal and external url (active sync,owa,ews)on 2010 and 2013 servers?
Where is the config wrong?
Thanks!
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

Hi Martina,
did the test as mentioned,even tried both CAS 2013 servers.Flush and registerdns didnt help.
Still Outlook is Connected to the cas.exchange.as (which again Points to 1 of Exchange 2010 servers),
Tried repair Outlook profile,no og.Only fix is to setup New account.
Any more tips?
thanks!
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

Exchange 2010 and 2013 coexisting in separate trusted AD Forests, same email domain.

Im in a bind here.
Here is my scenario: We have domain 1, lets call this old-domain.corp that has an exchange server 2010 with MBX, CAS and HT role. We created a new domain, lets call this new-domain.corp that we migrated all our users AD accounts using ADMT from our old domain
to our new-domain.corp. We have both domains trusted two way, and we converted all our mailboxes on our old exchange 2010 server in our old domain to “linked mailboxes” with the owners of the mailboxes belonging to their new-domain.corp accounts.
This all works well currently.
What im trying to do now is have mailboxes live natively in the new-domain.corp on the new exchange 2013 server (only MBX role) I just built, whilst still having mailboxes working on our old-domain.corp while we migrate the mailboxes to the new. What
is the best way to achieve this? Right now I can create new mailboxes on the new server and send emails (using owa), but receiving is an issue since once mail is routed to my exchange 2010 (old) server it doesn’t keep going to the new exchange 2013 server.
Some details
Exchange 2010 – old-domain.corp – MBX, CAS, HT – latest rollup and exchange updates as of a week ago.
Exchange 2013 – new-domain.corp trusted two way with old domain - MBX
140 users - Single email domain name space
All on premise
Thank you,

Hi
In your case first you would need to bring Exchange 2013 CAS into the new domain.
Point all the web services URL to the Exchange 2013 CAS server
Redirect your firewall to receive all the emails to Exchange 2013 server
Then you would need to preparemove request and then once the objects are created then you would need to run new move request to move all the mailboxes from old domain to the new domain
One good article for your reference
http://msexchangeguru.com/2013/11/03/e2013crossforestmigration/
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish
(MVP)

Exchange 2010 and 2013, Coexisting "OWA" and "ActiveSync" 1 Public IP.

Hello Everyone.
I find myself in a bit of a dilemma and in a desperate need for some well educated help.
Scenario: Server 1 (Small Business Server 2011 Standard) with Exchange 2010
Server 2 (Server 2012 Standard) with Exchange 2013
1 Static Public IP Address
This used to be one domain that split into two separate entities that are still occupying the same office space.
All port forwarding is currently pointing to the SBS and everything there is working properly. I setup a new receive connector on the SBS that is forwarding the mail for domain 2 to the "Exchange 2013" server and mail flow in and out is working
100%.
The problem lies with OWA and ActiveSync.
I tried changing the SSL port in IIS on Server 2 from 443 to 1443 and forwarded those ports to server 2 from the router, then OWA works externally, but for some reason the clients on the local network can't connect anymore, so I had to drop that idea after
being unable to find the cause.
The only other thing I can think to try, is to setup HTTP redirection on the SBS IIS or adding the mail.domain2.com in the SBS DNS or something.
I have searched for hours but can't find anything specific to my scenario. Any and all help will be greatly appreciated.
Any and all help will be greatly appreciated.
Thank you in advance.
Hentie Loots

You need to use ARR.
http://www.iis.net/downloads/microsoft/application-request-routing
It is essentially like a basic proxy service. So the SBS would receive an SSL connection for mail.domain2.com and instead of it failing it would be redirected internally to the second server.
Robert Pearman SBS MVP
itauthority.co.uk |
Title(Required)
Facebook |
Twitter |
Linked in |
Google+

Exchange 2010 and 2013 "OWA and ActiveSync" co-existance 1 Public IP.

Hello Everyone.
I find myself in a bit of a dilemma and in a desperate need for some well educated help.
Scenario: Server 1 (Small Business Server 2011 Standard) with Exchange 2010
Server 2 (Server 2012 Standard) with Exchange 2013
1 Static Public IP Address
This used to be one domain that split into two separate entities that are still occupying the same office space.
All port forwarding is currently pointing to the SBS and everything there is working properly. I setup a new receive connector on the SBS that is forwarding the mail for domain 2 to the "Exchange 2013" server and mail flow in and out is working
100%.
The problem lies with OWA and ActiveSync.
I tried changing the SSL port in IIS on Server 2 from 443 to 1443 and forwarded those ports to server 2 from the router, then OWA works externally, but for some reason the clients on the local network can't connect anymore, so I had to drop that idea after
being unable to find the cause.
The only other thing I can think to try, is to setup HTTP redirection on the SBS IIS or adding the mail.domain2.com in the SBS DNS or something.
I have searched for hours but can't find anything specific to my scenario. Any and all help will be greatly appreciated.
Any and all help will be greatly appreciated.
Thank you in advance.
Hentie Loots

I recommend that you post this in the SBS Forum since SBS is different:
http://social.technet.microsoft.com/Forums/en/smallbusinessserver/threads
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

OWA Exchange 2010 and 2013 Co-Existance

Hi All
I have 2 new Exchange 2013 Multi role servers in a test environment. I have setup the namespace's in the following way
Communcal OWA URL - exchange.domain.co.uk/owa
Server 2013 Boxes
OWA URL Internal and External - owa.domain.co.uk/owa
Server 2010 Boxes
OWA Internal - legacy.domain.co.uk
OWA External - legacy.domain.co.uk
Authentication on Exchange 2010 boxes is set to basic, form based.
Authentication on Exchange 2013 boxes is set to basic and form based.
When users hit are exchange.domain.co.uk/owa it is sent to 2013 servers. This we then want to process all requests and proxy connections to 2010. Accessing a 2013 mailbox is fine, however 2010 users just get the message, opening mailbox, it then sticks on
Still Working on it for indefinite and never progress'.
Have tried removing the External URL from 2010 as I have seen suggested elsewhere but this makes no difference.
ECP address' match what OWA are and certificates include all 3 namespaces.
Many THanks in advance for any assistance
Jason

Hi All
I have 2 new Exchange 2013 Multi role servers in a test environment. I have setup the namespace's in the following way
Communcal OWA URL - exchange.domain.co.uk/owa
Server 2013 Boxes
OWA URL Internal and External - owa.domain.co.uk/owa
Server 2010 Boxes
OWA Internal - legacy.domain.co.uk
OWA External - legacy.domain.co.uk
Authentication on Exchange 2010 boxes is set to basic, form based.
Authentication on Exchange 2013 boxes is set to basic and form based.
When users hit are exchange.domain.co.uk/owa it is sent to 2013 servers. This we then want to process all requests and proxy connections to 2010. Accessing a 2013 mailbox is fine, however 2010 users just get the message, opening mailbox, it then sticks on Still
Working on it for indefinite and never progress'.
Have tried removing the External URL from 2010 as I have seen suggested elsewhere but this makes no difference.
ECP address' match what OWA are and certificates include all 3 namespaces.
Many THanks in advance for any assistance
Jason

Exchange 2010 and 2013 Monitoring with SCOM 2012

HI all,
I have exchange 2013 and 2010 in my environment , Iwant monitor both in SCOM 2012,
Can you all please tell can i implement 2013 monitorinng first later can i go to 2010 Monitoring, Please advise in that supported or do i need to go with exchange 2010 monitoring first

There are no dependencies on the 2010 MP so you should be good to go, see the following:

Exchange 2010 and 2013

Hi All can some one guide me in correct path on exchange journalDB restore? I have Journal DB on exchange 2010 i need to mount the journalDB to exchange 2013 once this is successful i can decom the exchange 2010 servers. until i dont get journal DB restore
right i will not be able to decom my exchange 2010.i have tried restoring using DPM backup server but not having any luck. i have followed following link to restore the DB.
http://exchangeserverpro.com/restore-individual-mailbox-exchange-2010/
Regards
Ravi

According to your description, I would like to refer you on this well explained blog that covers all the required parts and would be a good start-up while need to restore Journal mailboxes using DPM :
http://www.techrepublic.com/blog/data-center/eight-steps-to-restore-an-individual-exchange-2010-mailbox-with-system-center-data-protection-manager/
Moreover, you may also consider on this automated option (http://www.exchangeserverrecovery.com/) that could also be a better alternative approach for the same concern.

Activesync URL in Exchange 2010 and 2013 co-existence environment

I am running a 2013 / 2010 coexistence environment, and have a question about activesync external URl setting on the Exchange 2010 servers. Do I need to set it to $null? Thanks

I am running a 2013 / 2010 coexistence environment, and have a question about activesync external URl setting on the Exchange 2010 servers. Do I need to set it to $null? Thanks
Set it to the same externalURL as the 2013 ExternalURL .
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Migrate Exchange 2010 to 2013 External Mail Flow

Dear All,
I am in the middle of Exchange Server 2010 to 2013 Migration. The scenario is I have single Exchange 2010 server with HUB/CAS/Mailbox and installed new Exchange 2013 with single CAS and single Mailbox server. The internal email flow between Exchange
2010 to 2013 and 2013 to 2010 is working. Having some issues and need assistance to resolve at earliest.
The issue with the external mail flow and I want to Exchange 2010 should be configured to send external email while migrating users to Exchange 2013. Once migrate all users to Exchange 2013 then will configure Exchange 2013 send connector.
How can I configure single name space of web URL for OWA both on Exchange 2010 to Exchange 2013, if user mailbox is in Exchange 2010 can access same OWA URL as user migrate to Exchange 2013.
How to configure SSL certificate, I have single URL certificate this would be enough for OWA, ActiveSync and Anywhere.
Is that possible if directly move the Exchange 2010 database to Exchange 2013 database, this will move all users mailboxes in one go or do I need to migrate users mailbox individual or in bulk.
Kindly guide if any thing missing that need to address during start the migration activity.
Thanks in Advance

Hi ,
Sorry for delay.
Question : Thanks for your valuable response. On
point no.2, I want to use same external URL for Exchange 2010 and Exchange 2013, is this possible if user is on exchange 2010 server or migrated on Exchange 2013 can use same external single name space URL to access OWA ?
Yes you can have the same External URL for the exchange 2010 owa and exchange 2013 owa.So users from exchange
2010 and exchange 2013 can access owa on the same URL from external world.For exchange 2010 users owa connections will be proxied from exchange 2013 to exchange 2010.
For mailbox connectivity issue in exchange 2013 :
1.From internal outlook clients ,Please check the internal outlook anywhere name is resolved to exchange
2013 server and also make sure the authentication set on the outlook anywhere is set to NTLM. Same time we need to have the internal outlook anywhere name on the SAN certificate.
2.Make sure the names used exchange on 2013 URL'S is available on the SAN certificate and also the certificate
needs to installed on the exchange server and that certificate has to be enabled for the required services like iis,pop.imap,smtp.
3.Make sure the outlook client request coming for internal outlook anywhere name and also to autodiscover
service is not reaching the proxy server if you have on your network.
In case if you have proxy server in your environment for internet access ,So for that we need to add the internal outlook anywhere name and autodiscover name
on the internet explorer proxy exceptions for all the internal outlook clients.We can globally achieve it through group policy.
4.please share me the output for the below mentioned command.
get-ClientAccessServer -Identity “server name” | fl AutodiscoverServiceInternalURI
5.If you are having outlook 2007 then make sure it fully patched with latest sp and updates.
6.On which operating system version those outlook 2007 clients are installed?
Please reply me if anything is unclear.
Thanks & Regards S.Nithyanandham

Lync 2010 and 2013 coexistence - DNS

Hi all,
we are planning to upgrade from Lync server 2010 to 2013.During this mode,what is best to do regarding DNS?
Should we just keep existing ones and let Lync server proxy users, or do we need to point dns (internal and external) to the new 2013 server?
Like in Exchange 2010 and 2013 coexistence we had to point all dns to 2013 server,or users wont be proxied.
These are the DNS:
lyncdiscoverinternal
meet,dialin,admin
_sipinternaltls._tcp.domain.com
_sipfederationtls._tcp
sip.domain.com
Other DNS i might forgot?
thanks!
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

If you don't want to cut everyone over at once, you'll need different FQDNs for external web services between the pools, because mobility and meetings will use them both, regardless of where lyncdiscover and meet point.
If you want to keep the same name, that's fine, but you'll have to cut over in one big shot.
Also, pick a different name for the internal vs external web services. Mobility uses the external name, even when connecting on internal WiFi, so you'll want to redirect requests on port 443 to port 4443 for that and make it available internally.
If you have the same name for the internal web services, then internal requests will also use that path, which can cause issues or at the least route through a reverse proxy for no good reason.
Correct about pool FQDN being unique, also internal and external web service FQDNs unless you move everyone in one shot and don't care.
Everything else is pretty much a repoint when you're ready situation.
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications
This forum post is based upon my personal experience and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Free/Busy not working Exchange 2007 and 2013 co-existence

Hi,
I'm migrating our Exchange 2007 environment to Exchange 2013. Now I am in a co-existence environment where all the mailboxes except some test-users resides on Exchange 2007. Between Users on the same Exchange MBX Server athe FREE/BUSY Information sharing
works correctly, but between Exchange 2007 and 2013 it's not working.
I verified my settings and also the EWS virtual directory on 2007 CAS Servers using Get-WebServicesVirtualDirectory.
The internal and the external URLs are set to https://legacy.mydomain.com/....
What am I missing?
Thanks & Kind Regards,
Jürgen

Hi,
According to your description, I understand that the free/busy information between Exchange 2007 and Exchange 2013 is not available for your coexistence environment. To narrow down the issue, please check the following points:
1. Does the issue happen to all users or specific users?
2. Although a user on Exchange 2013 can't get free/busy information from a user on Exchange 2007, please confirm whether Exchange 2007 user can get free/busy information from Exchange 2013 users.
3. Close Outlook and only access user mailbox from OWA to check whether the issue persists. For Outlook client,
create a new Outlook profile
to have a try.
4. Please make sure the virtual directories settings are configured correctly in both Exchange 2013 and Exchange 2007.
Virtual directories settings in Exchange 2007:
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-3-step-by-step-exchange-2007-to-2013-migration.aspx
Certificate and Virtual directories settings in Exchange 2013:
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-2-step-by-step-exchange-2007-to-2013-migration.aspx
5. Restart IIS service in Exchange server by running iisreset /noforce from a command prompt window.
If possible, please run Test E-mail AutoConfiguration in Outlook to check whether the autodiscover service can get correct Availability service URL in the results. If there is any event logs, please collect some for further analysis.
Regards,
Winnie Liang
TechNet Community Support

Exchange 2010 to 2013 Co-Existence Reverse DNS Issue

We are running a Exchange 2010 and 2013 coexistence. Mail Flow is fine on the 2013 side, but for mailboxes still on 2010, some are getting mail delivery failures only for certain external addresses. One of the deliveries says the Sending IP
does not have a valid rDNS. The IP Address it sent back is the main Public IP and not the Public IP assigned to our mail servers. Not understanding why the 2013 mailbox users can send to these external addresses no problem when 2010 mailbox users
are being routed through 2013. Thanks for any help.

Hi,
According to your post, I understand that account in Exchange 2010 deliver message failed for certain external addresses, however the user in Exchange 2013 works fine.
If I misunderstand your concern, please do not hesitate to let me know.
Whether all user in Exchange 2010 or some special account experience this question?
If this issue only occur on some specific external address, please contact its administrator to double confirm the configuration of anti-spam filter.
Besides, I recommend run Message tracking log and Protocol log to check the deliver process. More details about “Analyzing the protocol logs and Message tracking logs in Exchange 2013”:
http://social.technet.microsoft.com/wiki/contents/articles/23182.analyzing-the-protocol-logs-and-message-tracking-logs-in-exchange-2013.aspx
Thanks
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Allen Wang
TechNet Community Support

Lync Phone Edition coexistance with lync 2010 and 2013

Hi Everyone
I am currently planning a coexistent network between Lync 2010 and 2013 as I need to get 2013 out urgently. My question is around the Lync phone edition and how to get the phone to find the front end to register the phone to depending on which lync
pool the user is configured to use. Right now all phones are configured with DHCP and are configured to use the 2010 front end server to get its cert provisioned. I also use the HP 4110 and 4120 phones in the office.
How should I configure DHCP so that I do not cut my user off if they are moved the 2013 pool?
Many Thanks
Joe
Joe

Hi,
Check this old Thread
https://social.technet.microsoft.com/Forums/office/en-US/fca0b7be-124e-4480-ba2f-19ca4eebbd53/phone-edition-aries-polycom-cx600-coexistence-lync-2010-and-2013?forum=lyncvoice
http://unifiedme.co.uk/2013/09/lync-2010-2013-migration-lync-phone-edition-devices/
Whenever you see a helpful reply, click on Vote As Helpful & click on Mark As Answer if a post answers your question.

Single name space in between Exchange 2010 and 2013

Similar Messages

Maybe you are looking for