Adressbook hang Exchange 2010 - Outlook 2010,2013

Hi Forum
we have Exchange 2010 and Clients with Office 2010, 2013
on all client we can't use adressbook, when we open it and change the adresslists
Outlook hang
i think the problem is since Exchange Rollup 8 v2

Hi,
Please confirm if the issue occurs when using Global Address List in OWA.
In server side, please restart Microsoft Exchange File Distribution service and check whether the OAB folder in the following path is the latest date in Exchange sever:
a. OAB generated in Mailbox:
\\Program Files\Microsoft\Exchange Server\ ExchangeOAB
b. OAB distribution in Client Access:
\\Program Files\Microsoft\Exchange Server\ClientAccess\OAB
In Outlook client, please download Address Book manually in Outlook by the following setps:
In the ribbon click Send / Receive, click
Send/Receive Groups and then click Download Address Book.
Then check whether there is any error when download it.
Regards,
Winnie Liang
TechNet Community Support

Similar Messages

Outlook client requirements and Exchange 2010/2013 coexistence

Good morning!
A question regarding Exchange 2010/2013 coexistence and the Outlook client requirement. I am upgrading and about to install Exhange 2013 into an existing Exchange 2010 Org. The current 2010 Org is patched to SP-3 and Outlook Anywhere is currently disabled.
I have Outlook clients that do not yet meet the minimun requirements for 2013 (Outlook 2007/2010). When I install my first 2013 server will it effect the current downlevel clients? The mailboxes are still in 2010 so my thoughts were since the Office upgrade
including Outlook has not yet taken place I didn't want to wait for them to at least get 2013 into the Org. The 2013 server should effect the clients until I configure the CAS on 2013 and only when they are at the proper version, is this correct? Does Outlook
Anywhere need to be first enabled and configured on the 2010 CAS before I attempt the confgiuration on the 2013 CAS? I just dont want to install 2013 and have Outlook connectivity issues right out of the gate...
Thanks in advance!

Outlook 2007 and 2010 are supported for Exchange 2013, you just need to push out the latest patches.
http://technet.microsoft.com/en-us/library/aa996719(v=exchg.150).aspx
If you configure the URLs properly in Exchange 2013 to URLs that point to the Exchange 2010 servers, your clients shouldn't try to talk to the Exchange 2013 server.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Exchange 2010/2013 coexistence: OWA proxy not working properly ":-( Something went wrong"

Hi
Exchange 2010 users are NOT able to connect to their mailboxes when they go through exchange 2013 OWA address. We get a message that says following ---> "Something went wrong"
Following is our URL. The address is pointing to 2013 CAS loadbalancer VIP. Outlook anywhere is working fine. What is going on?
Important: All my exchange 2010 / 2013 URIs are the same as suggested by Microsoft (Owa, ecp, activesync, ews, autodiscover): --> mail.domain.com/XXX

Hello Rawa,
Can you log on Exchange 2010 OWA using its localhost address?
Please make sure the intenralurl value is set to Exchange 2010’s local host name and set the Externalurl to Null.
http://technet.microsoft.com/en-us/library/bb310763(v=exchg.141).aspx
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Exchange 2010-2013 co-existence - need for OWA/ActiveSync legacy namespace?

Hi all
Straight to the point: how to I update units that were set up manually with Exchange ActiveSync (pointing to owa.domain.com) with a temporary legacy namespace owa-legacy.domain.com, and then back to owa.domain.com?
Background: I did a test run of migrating a single-server installation from Exchange 2010 to Exchange 2013. As expected, after moving a user's mailbox to the new Exchange 2013 CAS with owa.domain.com still pointing to Exchange 2010, the user
was unable to log in at the Exchange 2010 OWA, and the ActiveSync unit was unable to fetch mail.
So I created a legacy namespace (owa-legacy.domain.com) and set this as the URL on the Exchange 2010 server, and waited for it to populate, then switched owa.domain.com to Exchange 2013. But the URL on ActiveSync units was still pointing to the wrong URL.
What did I overlook or not understand, or am I making migration more complex than needed?
Thanks for reading and best regards
/Maurice
PS: here were some of my pre-post readings:
Exchange 2003-2013 co-existence, even better
Exchange 2003-2013 co-existence,
Exchange 2010-2013 co-existence slides,
Upgrading ActiveSync to Exchange 2010,

Hi
Is that because External URL on Internet facing CAS servers were set to Blank，and Users are not able to get Updated URL
Please try to Add the External URL and made sure that all the required configurations are set Appropriately.
Also I suggest posting on Exchange ActiveSync Forum as well
http://social.technet.microsoft.com/Forums/en-US/home?forum=exchangesvrmobility
Cheers
If you have any feedback on our support, please click
here
Zi Feng
TechNet Community Support

Search-Mailbox not attaching the infected emails in target folder and deleting the contents in exchange 2010 & 2013 coexistence

Dear All,
I have an issue with deleting circulated spam emails in my environment through search-mailbox
We have Exchange 2010 & 2013 CU5 environment
I followed the search and destroy document for exchange 2010
http://windowsitpro.com/exchange-server-2010/search-destroy-email-content-exchange-2010
Added the user to Discovery Management group
Created a new role group as below
New-RoleGroup "Mailbox Import-Export Management" -Roles "Mailbox Import Export"
Add-RoleGroupMember "Mailbox Import-Export Management" -Member Administrator
I ran the below commands
Search-Mailbox -Identity "[email protected]" -SearchQuery "Subject:'report'" -TargetMailbox "Administrator" -TargetFolder "Filter" -LogOnly -LogLevel Full
The above command gets completed successfully and sends the log report however im unable to see any attachments
Similarly the deletecontent also gets completed successfully and logs result. But it does not delete the infected emails
Search-Mailbox -Identity "[email protected]" -SearchQuery "Subject:'report'" -TargetMailbox "administrator" -TargetFolder "filter" -deletecontent -LogLevel Full
Any idea why it is not fetching the infected emails in zip file and why it is not deleting but it is able to log in the target folder
Any help much appreciated
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)

Hi All
I managed to find the solution. Below command helped me in solving the issue
get-mailbox -ResultSize unlimited -IgnoreDefaultScope | search-mailbox -SearchQuery ‘Subject:"virus infected"’ -LogOnly -TargetMailbox administrator -TargetFolder filter -LogLevel Full
get-mailbox -ResultSize unlimited -IgnoreDefaultScope | search-mailbox -SearchQuery ‘Subject:"virus infected"’ -TargetMailbox administrator -TargetFolder filter -deletecontent -LogLevel Full
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-2013 Migration - Outlook Client gets "Your administrator has made a change..."

So we're migrating from an Exchange 2010 environment to Exchange 2013. We use a single namespace ("exchange.contoso.com") for both internal and external clients.
In testing, we have taken a few machines running outlook 2013 and 2010, and edited their hosts file such that "exchange.contoso.com" points toward the new exchange 2013 environment, rather than the 2010 environment for our users. So far so good,
they can connect, no issues.
However, when we move a mailbox to the 2013 environment, the outlook client comes back with "Your Exchange Administrator has made a change which requires you to restart outlook". This error affects both Outlook 2013 and 2010. We do have public
folders in place in exchange 2010, but we have not yet migrated them to 2013 (because the user's still are on 2010).
Repairing the profile is no help, and recreating the profile does not work either. Any thoughts?

Hi ,'
On you first post you have said you have put host file entries for the namespace "exchange.contoso.com"
in few of the client machines .
what about for autodiscover namespace did you have put any host entries for that .If not please put that
too in the host file of the client machines and then check by moving anyone of the mailbox from exchange 2010 to exchange 2013 .
Same time please check this blog especially on the end of the page .
http://blogs.msdn.com/b/aljackie/archive/2013/11/14/outlook-and-rpc-end-point-the-microsoft-exchange-administrator-has-made-a-change-that-requires-you-quit-and-restart-outlook.aspx
Regards
S.Nithyanandham
Thanks S.Nithyanandham

Problems with archive mailbox in Outlook, with exchange 2010+2013 co-existence

Hi!
We have an Exchange 2010 environment plus one Exchange 2013 MBX server meant for archive mailbox purpose. (We are going to upgrade to 2013 but with over 20.000 mailboxes it will take som time. Therefore we need to co-exist with primary mbx on 2010 and archive
mbx on 2013 for some time.)
My primary mailbox is on a 2010 MBX server, and I have today given myself an archive mbx on 2013 MBX server.
When I use OWA, both my primary mailbox and my archive shows up and everything works 100% fine!
But when I try Outlook 2010 or Outlook 2013, only my primary mailbox works. The archive mailbox shows up, but generates an error when accessing it:
"The set of folders cannot be opened. Microsoft Exchange is not available. Either there are network problems or the Exchange server is down for maintenance"
Anyone who knows about this issue? Would we nice to know why it works in OWA but not in Outlook.
Thanks!
Trond Jenssen

Hi，
Please try to recreate a profile to access archieve mailbox.
If it doesn't make sense, also try Uncheck “Download shared folders” and check it again.
If you have any feedback on our support, please click
here
Wendy Liu
TechNet Community Support

Missed Call Notification in Exchange 2010/2013 coexistence mode

Dear all,
Context:
Lync 2013 Enterprise Voice, Exchange 2010 and Exchange 2013 in coexistence mode
Waiting complete migration, some users are always on exchange 2010
UM role is installed on both exchange server
The exchange servers UM are attached to only one UM Dial Plan
Scenario :
A call to a lync user. The caller hang-up before user announcement
Problem: Missed call notification doesn't work for user on Exchange 2010 (it's work fine for user on Exchange 2013)
Voice Messaging works fine
Troubleshooting / SIP Traces:
SIP Info is always send to Exchange 2013 even if user is on exchange 2010
SIP Info sent from Lync FE to Exchange 2013 UM :
TL_INFO(TF_PROTOCOL) [0]6330.3AE8::02/12/2015-12:25:23.575.015c018e (S4,SipMessage.DataLoggingHelper:sipmessage.cs(774))[1718622663]
>>>>>>>>>>>>Outgoing SipMessage c=[<SipTlsConnection_13ECA29>], 192.168.5.110:49786->192.168.5.203:5061
INFO sip:outlook.mydomain.com:5061;ms-fe=exchange2013-UM.mydomain.localdomain;transport=Tls SIP/2.0
FROM: <sip:A410AA79-D874-4e56-9B46-709BDD0EB850>;epid=8C75BE2D95;tag=35c2d8a65a
TO: <sip:exchange2013-UM.mydomain.localdomain;opaque=app:rtcevent;transport=tls>;epid=C4C2F4F6BA;tag=ac126413f
CSEQ: 43 INFO
CALL-ID: 535a07e2-8e82-4d13-8e03-bf43ad97602d
MAX-FORWARDS: 70
VIA: SIP/2.0/TLS 192.168.5.110:49786;branch=z9hG4bKd66442be
CONTACT: <sip:LyncFE-2013.mydomain.localdomain;transport=Tls>
CONTENT-LENGTH: 454
USER-AGENT: RTCC/5.0.0.0 Inbound Routing (Microsoft Lync Server 2013 5.0.8308.726)
CONTENT-TYPE: application/ms-rtc-usernotification+xml
- <UserNotification>
       <User>sip:[email protected]</User>
       <EumProxyAddress>EUM:[email protected];phone-context=UMDialPlan.mydomain.localdomain</EumProxyAddress>
       <Time>2015-02-12 12:25:23Z</Time>
       <Template>RtcDefault</Template>
    + <Event type="missed">
</UserNotification>
------------EndOfOutgoing SipMessage
Answer from Exchange 2013 UM
TL_INFO(TF_PROTOCOL) [1]6330.2DF4::02/12/2015-12:25:23.642.015c2481 (S4,SipMessage.DataLoggingHelper:sipmessage.cs(774))[1718622663]
<<<<<<<<<<<<Incoming SipMessage c=[<SipTlsConnection_13ECA29>], 192.168.5.110:49786<-192.168.5.203:5061
SIP/2.0 200 OK
FROM: <sip:A410AA79-D874-4e56-9B46-709BDD0EB850>;tag=35c2d8a65a;epid=8C75BE2D95
TO: <sip:exchange2013-UM.mydomain.localdomain;opaque=app:rtcevent;transport=tls>;tag=ac126413f;epid=C4C2F4F6BA
CSEQ: 43 INFO
CALL-ID: 535a07e2-8e82-4d13-8e03-bf43ad97602d
VIA: SIP/2.0/TLS 192.168.5.110:49786;branch=z9hG4bKd66442be
CONTENT-LENGTH: 0
SUPPORTED: ms-dialog-route-set-update
SERVER: RTCC/5.0.0.0 MSExchangeUM/15.00.0995.028
ms-diagnostics-public: 15642;reason="Lync SIP INFO notifications are not supported for legacy users. User: EUM:[email protected];phone-context=UMDialPlan.mydomain.localdomain"
------------EndOfIncoming SipMessage
Gerald Cheminant

Hi,
This behavior is by design. Exchange 2010 server is not going to accept any SIP messages from Exchange 2013 server because it is not listed as UM IP Gateway. Therefore, even if Exchange 2013 redirected the SIP INFO packet to Exchange 2010, it will fail.
During migration\coexistance scenario, this feature (Missed call notifications from Lync server) will not work for legacy users whose mailbox is still in Exchange 2010.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Exchange 2010 - 2013 Coexistence Issues

I am migrating from Exchange 2010 to Exchange 2013, the Exchange 2013 is built in a different Geo-location site with its dedicated domain controllers in the new site. I have confirmed the mail flow between Exchange 2010 and 2013 mailboxes. I am able to discover
Exchange 2010 servers from 2013 environment via Get-ExchangeServer shell command. However, I am not to discover Exchange 2013 servers from 2010 environment.
I need to configure Outlook Anywhere and Service Connection Point (Autodiscover) on Exchange 2010 to accept connections from Exchange 2013 servers.
Any suggestions would be much appreciated, thanks!

Hi ,
Please have a look in to the below mentioned blog after reading that blog i came to know few things .
I am not sure ,i thought exchange 2013 servers will not be displayed in exchange 2010 management shell.
Better and advisable method is to configure your exchange 2010 and 2013 servers via EAC or Shell in exchange 2013.
http://exchangeserverpro.com/exchange-server-2010-2013-migration-managing-co-existence-environment/
Taken from the above blog :
You can’t use the Exchange 2010 EMC to manage Exchange 2013 objects and servers. While customers upgrade to Exchange 2013, we encourage them to use the EAC to:
Manage Exchange 2013 mailboxes, servers, and corresponding services.
View and update Exchange 2010 mailboxes and properties.
View and update Exchange 2007 mailboxes and properties.
We encourage customers to use Exchange 2010 EMC to create Exchange 2010 mailboxes.
We encourage customers to use Exchange 2007 EMC to create Exchange 2007 mailboxes.
Customers can continue to perform management tasks using the Exchange Management Shell and script tasks.
Regards
S.Nithyanandham
Thanks S.Nithyanandham

EXchange 2010 & 2013 Co-existence

Hi,
I have Exchange 2010 Running currently in 3 Sites. Now I have to introduce Exchange 2013 CU6 on 4th Site (Same Exchange ORg) and migrate all E2k10 Mailboxes to E2k13.
My Questions is ... What would be the Internal Hostname that I need to mentioned in E2k10 server in Out Look Anywhere ?
Note: I am using Existing OWA & Autodiscover URL which is running for E2k10 server mai.abc.com & Autodiscover.abc.com .
On E2k13 I have set External & Internal URL for Outlook anywhere is mail.abc.com .
I am using E2k10 certificate on E2k13 server as it having same DNS name space mentioned.
Please suggest !!
Amit

Hi,
I have Exchange 2010 Running currently in 3 Sites. Now I have to introduce Exchange 2013 CU6 on 4th Site (Same Exchange ORg) and migrate all E2k10 Mailboxes to E2k13.
My Questions is ... What would be the Internal Hostname that I need to mentioned in E2k10 server in Out Look Anywhere ?
Note: I am using Existing OWA & Autodiscover URL which is running for E2k10 server mai.abc.com & Autodiscover.abc.com .
On E2k13 I have set External & Internal URL for Outlook anywhere is mail.abc.com .
I am using E2k10 certificate on E2k13 server as it having same DNS name space mentioned.
Please suggest !!
Amit
You wouldn't need to define an internal host. It can be set to the internal FQDN of the 2010 CAS itself. or set to the same as the external hostname if using split DNS.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Ports Required to open between Exchange 2010 & 2013

Hi,
I have to introduce Exchange 2013 into Exchange 2010 environment that is in same Organization. There are 3 sites connected on which Exchange 2010 installed and 4 site will be Exchange 2013 and then mailbox will migrate to E2k13 servers.
All 4 sites and connected to MPLS link, please let me know what ports are required to open for Communication between mail flow.
From Internet OWA : 443 & 25 is sufficient for Mail flow.
Amit

Exchange does not support blocking any ports between individual Exchange Servers as well as Exchange to DC communication, so for internal communication everything has to be opened.
If you are just talking client traffic (OWA, ActiveSync, Outlook Anywhere) and smtp mail traffic from external sources, then you should only need 443 (client traffic) and 25 (smtp traffic).
https://social.technet.microsoft.com/Forums/en-US/bc21b467-76bb-4c86-b7e1-21daa82cc37a/ports-required-for-exchange-2013-installation?forum=exchangesvrdeploy

Exchange 2010 & 2013 coexistence mail flow between servers

Hi Everyone,
I have an exchange 2010 server which I am trying to move away from. I have installed 2013 and it seems to be working well. I have successfully moved a mailbox over to 2013 without any issues.
The problem i have at the moment is that a user who has their mailbox on the 2010 server can send to the user on the 2013 server. However the 2013 user cannot reply.
Any ideas?

Yes, some issues with client connectivity are related to Outlook.
Exchange Blog:
www.ntweekly.com
MCSA, MCSE, MCITP:SA, MCITP:EA, MCITP:Enterprise Messaging Administrator 2010,MCTS:Virtualization

Exchange 2010 - 2013 Mailbox move - Syncing with no progress (Stalled?)

I'm in the process of moving mailboxes from Exchange 2010 to Exchange 2013, the major of the mailboxes have moved successfully, however I did not anticipate the additional space required by Exchange 2013 and ran out of disk space during the mailbox move,
and some mailboxes did not move successfully.
I have since added additional space but can't seem to get the remaining mailboxes to sync.
I have tried :
Rebooting
Clearing out migration batches and recreating
Stopping and resuming batches.
I see nothing helpful in the Migration log files.
2013-05-20T23:59:57.904Z,14,MigrationServicelet,Information,",827890ff-522d-4c13-9f42-96fbfefb57f4,,","Job type ExchangeLocalMove, status SyncStarting, result Working, length 0.2724593, job :827890ff-522d-4c13-9f42-96fbfefb57f4:ExchangeLocalMove:Staged:4::SyncStarting:2013-05-17
2:59:12 PM::"
When I download the report for one of the users I see this, but don't know what it means :
The job is currently stalled due to 'Content Indexing' lagging behind on resource 'CiAgeOfLastNotification(Mailbox Database 2065686096)'
For one of the other users the downloaded report only shows :
2013-05-16
2:11:18 PM '' created move request.
DWW
Additional Info: I followed the info located here in regards to creating the ContentSubmitters group:
http://www.bullspit.co.uk/2013/04/08/exchange-2013-content-indexing-during-migration/
My mailbox database currently has Content index state: FailedAndSuspended
I only have one database, I am not using DAG

I had already created the contentsubmitters and it helped with the speed of the mailbox moves. We have a SMB with >100 users and everything was working great, migrating from 2007 to 2013. If I had it to do over, maybe it would have been better
to go to 2010 on a 2008 R2 box but decided to jsut go straight to 2013 on a 2012 R2 server. But the one thing I REALLY wish I had to do over again is to allocate about 3 times more space to the drive that was to hold the mailbox database. Everything
was working so well until a mailbox was being moved - a batch of several, I was doing maybe 5 at a time for the larger mailboxes - the disk filled up. Also, before I realized what was going on, I ran some cmdlets thinking my receive connectors weren't
right. I recovered the database - at first it would not mount at all... but after eseutil /r and /p (and allocating more disk space) I could mount the database and open the mailboxes. But from then on, nothing is being received and if you send,
it goes to sent items - doesn't hang in outbox, but never goes anyhere except into a queue. I have MS support working on it and it's been escalated to the top. If they fix it I will try to post any helpful information I can learn from it. But one
lesson - I will read the planning and preparations documentation thoroughly from now on.
Oh, and also, I keep getting this message in the ECP when navigating to the Recipients>migration applet:
Cannot open mailbox /o=<Organization>/ou=Exchange Asministrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/CN=<yourExchangeserver>/cn=Microsoft System Attendant.
If you did the same thing, (and didn't hang yourself or jump in front of a speeding locomotive), you are stronger than I. Not that I have taken the path of the Samurai network admin or anything....
And if you were able to fix it, I am impressed and would love to know how you fixed this.
Thanks and best,
Sam

Lync 2010 with Exchange 2010-2013 Migration?

We are installing Lync 2010 for the purpose of internal LAN and Internet/Federated instant messaging, video chat and desktop sharing.
There is no telephone integration and there is no Unified Messaging used in Exchange 2010.
Within a few months after rolling out Lync 2010, Exchange 2010 is going to be migrated to Exchange 2013. Outlook will remain at Office 2010 and Lync client will be 2010. We will continue to not use Exchange Unified Messaging after Exchange is
upgraded to 2013.
Are there any steps required to keep Lync 2010 working normally after the Exchange environment is upgraded from 2010 to 2013 in this scenario?

Hi
During the migration and post migration to EWS URL for the user i reachable by the Lync 2010 Client
And the outlook client is able to establish a Mapi session with the mailbox all should be fine
as best practice please have the Lync 2010 and outlook 2010 client update to the latest CU update
There is known issue when migrating from Exchange 2007 to 2013 good to know information
http://silbers.net/blog/2013/12/19/lync-ews-broken-during-exchange-20132007-transition/
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" Regards Edwin Anthony Joseph

Exchange 2010/2013 coexistence published in TMG 2010

Environment:
Two Windows 2008 R2, Exchange 2010 SP3 servers, currently holding all mailboxes
Two Windows 2012 R2, Exchange 2013 SP1 servers, setup in progress
Two Windows 2008 R2, TMG 2010, V7.0.9193.540 publishing both Exchange 2010 servers.
Scenario:
I need to continue having Exchange 2010 setup in TMG as is as the mailbox migration to 2013 will take weeks if not months and I have a project requirement to have Exchange Database Availability Group (DAG) functionality for all mailboxes throughout the project,
so 4 servers are an absolute must. So I need to add Exchange 2013 in TMG and not just replace the 2010 setup with the 2013 setup and I cannot run one 2010 and one 2013 server.
Questions:
1. I currently only have 2 public IP addresses available to SMTP, mapped to the external interfaces of TMG, to allow my environment to be able receive emails on 4 Exchange servers (two 2010 and two 2013) I need to have 4 public IP addresses, is that correct?
2. Does anyone have a good general guide/blog for doing this (setting up Exchange 2013 in TMG in a coexistance scenario)?
This is nice, but doesn't really approach it from a coexistance scenario:
http://blogs.technet.com/b/exchange/archive/2012/11/21/publishing-exchange-server-2013-using-tmg.aspx
Thanks!

Hi Trana,
In TMG you can use single IP address to publish multiple Web address and below are the options which you can explore.
Hope your OWA ECP etc are Https
You need a SSL certificate which has all the URL SAN entry of both old and new Exchange server.
Create a listener and select the IP address (Say public IP address 195.219.x.x)
Link the SSL certificate
Public DNS entry
A record , Single IP
195.219.x.x
Point to
Owa1.exchange1.com   - Old Server
195.219.x.x
Point to
ECP1.exchange1.com     - Old Server
195.219.x.x
Point to
ECP2.exchange2.com      - New Server
195.219.x.x
Point to
Owa2.exchange2.com     - New Server
Create a Web publishing rule as below
Old server Exchange 1
Owa1.exchange1.com
ECP1.exchange1.com
One Web publishing Rule with all the URL added on it and link the Rule with the listener we created
Point the Web publishing to Exchange1.com server which is old
New server Exchange 2
Web publishing Rule with all the URL added on it and link the Rule with the listener we created
Point the Web publishing to Exchange2.com server which is New
ECP2.exchange2.com
Owa2.exchange2.com

Adressbook hang Exchange 2010 - Outlook 2010,2013

Similar Messages

Maybe you are looking for