Exchange 2003-2010 co-existence environment

i have exchange 2003 -2010 co-existence environment .
Everything works fine accept below;weird issue,i tried to re-create routing group connector but issue is same.
My issue is very simple,The mail flow as below:
exchange 2003 to outside............
exchange 2010 to outside ...........works
exchange 2010 to 2003 ...............works
exchange 2003 to 2010................is not

Hi Huzefa,
Can you try creating a new bidirectional RGConnector and check?
New-RoutingGroupConnector -Name "NameOfRG" -SourceTransportServers "Ex2010.contoso.com" -TargetTransportServers "Ex2003.contoso.com" -Cost 10 -Bidirectional $true -PublicFolderReferralsEnabled $true
http://technet.microsoft.com/en-us/library/aa997292(v=exchg.141).aspx
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Similar Messages

Exchange 2003 /2010 Co-existence plus 2010 migration to new hardware

Hi,
Here is our current scenario;
Exchange 2003/2010 co-existence. This has been running perfectly for a couple of months now.
Exchange 2003 - exch1.domain.lan
Exchange 2010 (SP3) - exch2.domain.lan (local domain name) / mail.domain.com.au (external domain name)
ActiveSync, autodiscover, legacy etc are all working. Our UAC certificate from GoDaddy has all the required names for exch2 - except it doesn't have the local domain name as they don't allow certificates with that anymore. I've configured all the required
services to be the external domain name and am running split DNS.
The first Exchange 2010 server I installed was lower spec'd and only has about 25 users on it. I now need to install a second Exchange 2010 server (exch3.domain.local), which is properly spec'd and will host the entire company. I won't be running DAG as
I need to repurpose the first Exchange 2010 server once it's removed.
My high level questions are;
1) Should I migrate everyone off Exchange 2003 onto Exchange 2010, decommission the 2003 server, and then install the second 2010 server? OR
2) Should I install the second Exchange 2010 server, migrate everyone from the first Exchange 2010 server, decommission that one, then do the migration from 2003 to 2010?
OR does it matter which way I do it?
I've read what I can find about installing the second Exchange 2010 server into the organisation. It seems to be pretty simple at first. Just install Exchange 2010 with HT, mailbox and CAS roles which will automatically configure it into the same Exchange
organisation.
1) Do I configure CAS to be externally facing right from the get go or do I do that later?
2) As soon as I install the second Exchange 2010 server, will I encounter any mail flow problems? Will mail be trying to flow out of the second Exchange 2010 server as well as the first?
In regards to SSL, so obviously the second Exchange 2010 server will have a different local domain name than the first, but ultimately, I want it to have the same external domain name, eg mail.domain.com.au. As my certificate doesn't contain any local domain
names, can I export the certificate from exch1 and import it into exch2, or should I just generate a new CSR from exch2 and get GoDaddy to reissue it?
OR should I look at creating a CAS Array from exch1 and adding exch2 to it. (I don't fully understand the workings of this at the moment).
Any guidance on the above is helpful.
Thanks.
Steve

Hi Steve I will try my best to answer each of these
My high level questions are;
1) Should I migrate everyone off Exchange 2003 onto Exchange 2010, decommission the 2003 server, and then install the second 2010 server? OR
2) Should I install the second Exchange 2010 server, migrate everyone from the first Exchange 2010 server, decommission that one, then do the migration from 2003 to 2010?
OR does it matter which way I do it?
doesn't matter at all. Since you want to move to a new hardware you can setup a new Server CASH/HUB/Mailbox. Once installed start migrating the mailboxes from Exchange 2003 to this mailbox server. This way you will not have to redo the migration from 2010
to new 2010 sever -- like you mentioned in 1) it will save you a lot of time and repeating procedure.
I've read what I can find about installing the second Exchange 2010 server into the organisation. It seems to be pretty simple at first. Just install Exchange 2010 with HT, mailbox and CAS roles which will automatically configure it into the same Exchange organisation.
1) Do I configure CAS to be externally facing right from the get go or do I do that later?
Keep your existing 2010 internet facing for now. Once you finished migrating the mailboxes then you will need to do it.
2) As soon as I install the second Exchange 2010 server, will I encounter any mail flow problems? Will mail be trying to flow out of the second Exchange 2010 server as well as the first?
Mail will not flow to 2ndry server unless you add that server as a source serve in the transport.
In regards to SSL, so obviously the second Exchange 2010 server will have a different local domain name than the first, but ultimately, I want it to have the same external domain name, eg mail.domain.com.au. As my certificate doesn't contain any local domain
names, can I export the certificate from exch1 and import it into exch2, or should I just generate a new CSR from exch2 and get GoDaddy to reissue it?
You can always export the certificate and then import it to the newly installed Exchange 2010.
OR should I look at creating a CAS Array from exch1 and adding exch2 to it. (I don't fully understand the workings of this at the moment).
You will only need to setup the CAS array if you are going to use both the server which can be done later.
Hope that help
Where Technology Meets Talent

Exchange 2003/2010 Co-Existence - Distribution Group Management

We're running both exchange 2010 and Exchange 2003. I have an issue where some distribution groups were upgraded to Exchange 2010 (v14.0.100) and the manager of those lists who are on Exchange 2003 can no longer modify members, they get the error:
"Changes to the distribution list membership cannot be saved. You do not have sufficient permission to perform this operation on this object".
We've already implemented the myDistributionGroupsManagement role with success to allow Exchange 2010 users to manage their own list without allowing them to create new ones.
http://blogs.technet.com/b/exchange/archive/2009/11/18/3408844.aspx
Trying to apply the "Default Role Policy Assignement" to the exchange 2003 users returns an error. Is there any way Exchange 2003 users can manage Exchange 2010 Distribution list they owned without being upgraded to Exchange 2010? If not, is
there any way to downgrade distribution group to Exchange 2003 once they've been upgraded?

Hi,
From my lab, legacy exchange user can manage the distribution group which has been upgrade to Exchange 2010.
Exchange 2010 sp2, Exchange 2003 with sp2.
I can add/remove member for distribution group from address book via outlook.
Xiu Zhang
TechNet Community Support

Exchange 2003 - 2010 Co-existence Migration Autodiscover & OAB Issue

Hi,
I am in the middle of a Ex2003 to Ex2010 Migration initially through co-existence. Everything has been working perfectly for the last couple of months.
The first Ex2010 server I installed (EX01.domain.local) was just a temporary server that hosted a handful of users that were imported from another company.
I have since installed a second Ex2010 server (EX02.domain.local), which will be the permanent 2010 server. The end result will be 1 Ex2010 server only, after I have migrated everyone off EX01 and the 2003 server.
EX01 and EX02 both have the Mailbox, CAS, & HT roles installed.
I created the mailbox and Public Folder databases on EX02. I have assigned the Public Folder database to the mailbox database.
I added EX02 as a Source Server within Hub Transport.
I've exported the UC/SAN certificate from EX01 and imported it into EX02 and assigned the SMTP, IIS, POP & IMAP services to it.
I setup the legacy URL for OWA.
I changed the relevant settings on EX02, eg OWA, ECP, ActiveSync, OAB, AutoDiscoverServiceInternalUri etc to be external domain name that is listed on the certificate, eg mail.domain.com.au. (The SSL certificate is through GoDaddy and they do not allow you
to put any internal domain names on the certificate).
So before I installed the second Ex2010 server, everything was working correctly.
After I installed the second Ex2010 server and performed the steps above, I have noticed a couple of things;
1) The Autodiscovery test within Outlook works for mailboxes that have been migrated to either of the Ex2010 servers, but fails for mailboxes that are still on the Ex2003 server. It finds the correct URL, https://mail.domain.com.au/Autodiscover/Autodiscover.xml,
and brings back an HTTP status of 200. However, it says it then fails with (0x800C8203). I tested with Outlook 2003 and 2010. They both fail.
2) OAB fails to download for clients whose mailbox is still on the Ex2003 server. It fails with (0x8004010F - The operation failed. An object cannot be found). It works for clients with mailboxes on either of the 2010 servers.
I'm going around in circles reading numerous articles on trying to fix autodiscover. Using Microsoft's MRCA site, autodiscovery works externally for clients on the Ex2010 servers, but not on the 2003 servers, (which I thought was how it worked anyway as
autodiscovery doesn't work on Ex2003).
Is this the same for internal users. I'm not sure if I'm chasing my tail by trying to fix something that doesn't need fixing, but obviously the OAB should work.
Any suggestions are grateful.
Thanks.
Steve

Output from get-webservicesvirtualdirectory | fl
RunspaceId
: 12158f4a-101e-45c7-b35a-02c6b5652e41
CertificateAuthentication :
InternalNLBBypassUrl
: https://ex01.domain.local/ews/exchange.asmx
GzipLevel
: High
MRSProxyEnabled
: False
MRSProxyMaxConnections : 100
Name
: EWS (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity}
ExternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity}
LiveIdSpNegoAuthentication : False
WSSecurityAuthentication
: True
LiveIdBasicAuthentication : False
BasicAuthentication
: True
DigestAuthentication
: False
WindowsAuthentication
: True
MetabasePath
: IIS://EX01.domain.local/W3SVC/1/ROOT/EWS
Path
: C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\exchweb\EWS
ExtendedProtectionTokenChecking : None
ExtendedProtectionFlags
ExtendedProtectionSPNList : {}
Server
: EX01
InternalUrl
: https://mail.domain.com.au/ews/exchange.asmx
ExternalUrl
: https://mail.domain.com.au/EWS/Exchange.asmx
AdminDisplayName
ExchangeVersion
: 0.10 (14.0.100.0)
DistinguishedName
: CN=EWS (DefaultWebSite), CN=HTTP, CN=Protocols, CN=EX01, CN=Servers, CN=Exchange Administrative Group (FYDIBOHF23SPDLT), CN=Administrative Groups,CN=CompanyA,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=local
Identity
: EX01\EWS (Default Web Site)
Guid
: fd59fcca-87aa-4c7c-87d9-6ddeef4ca9e9
ObjectCategory
: next.lan/Configuration/Schema/ms-Exch-Web-Services-Virtual-Directory
ObjectClass
: {top, msExchVirtualDirectory, msExchWebServicesVirtualDirectory}
WhenChanged
: 28/03/2014 11:25:50 AM
WhenCreated
: 29/12/2013 9:42:33 AM
WhenChangedUTC
: 28/03/2014 12:25:50 AM
WhenCreatedUTC
: 28/12/2013 10:42:33 PM
OrganizationId
OriginatingServer
: DC2.domain.local
IsValid
: True
RunspaceId
: 12158f4a-101e-45c7-b35a-02c6b5652e41
CertificateAuthentication :
InternalNLBBypassUrl
: https://ex02.domain.local/ews/exchange.asmx
GzipLevel
: High
MRSProxyEnabled
: False
MRSProxyMaxConnections : 100
Name
: EWS (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity}
ExternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity}
LiveIdSpNegoAuthentication : False
WSSecurityAuthentication
: True
LiveIdBasicAuthentication : False
BasicAuthentication
: True
DigestAuthentication
: False
WindowsAuthentication
: True
MetabasePath
: IIS://EX02.domain.local/W3SVC/1/ROOT/EWS
Path
: C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\exchweb\EWS
ExtendedProtectionTokenChecking : None
ExtendedProtectionFlags
ExtendedProtectionSPNList : {}
Server
: EX02
InternalUrl
: https://mail.domain.com.au/EWS/Exchange.asmx
ExternalUrl
: https://mail.domain.com.au/ews/exchange.asmx
AdminDisplayName
ExchangeVersion
: 0.10 (14.0.100.0)
DistinguishedName
: CN=EWS (Default Web Site), CN=HTTP, CN=Protocols, CN=EX02, CN=Servers, CN=Exchange Administrative Group (FYDIBOHF23SPDLT), CN=Administrative Groups,CN=CompanyA,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=local
Identity
: EX02\EWS (Default Web Site)
Guid
: e592adcd-18c2-4c4b-bd89-fca95e9e9622
ObjectCategory
: next.lan/Configuration/Schema/ms-Exch-Web-Services-Virtual-Directory
ObjectClass
: {top, msExchVirtualDirectory, msExchWebServicesVirtualDirectory}
WhenChanged
: 28/03/2014 10:50:54 AM
WhenCreated
: 27/03/2014 10:34:27 AM
WhenChangedUTC
: 27/03/2014 11:50:54 PM
WhenCreatedUTC
: 26/03/2014 11:34:27 PM
OrganizationId
OriginatingServer
: DC2.domain.local
IsValid
: True

2003/2010 co-existence - is it safe to create recipient policies under 2010?

I'm pretty sure this won't affect anything, but just want to be 100% sure.
Exchange 2003/2010 are in co-existence happily working away
The existing Exchange 2003 recipient policies are a real mess
To save having to fix them all up, the plan is to just create new ones under Exchange 2010 and scope them to apply for users on 2010
When all users are moved to 2010, the old ones can be removed which saves having to upgrade them to all to 2010 format which is another bonus
Will creating new recipient policies under 2010 apply to recipients on 2003 or force the 2003 policies to run again somehow against existing users, or can recipient policues under 2010 be set to only apply to users in 2010 using a custom attribute for example
and when users are moved to 2010 with the custom attribute the policy can be enforced at that time? All the current polices are set to applied = false under 2003.

I have experience with messing up in this scenario :) in a 20,000 user environment.
E-Mail address policies are shared across the Exchange Organization so you will see ones created in 2010 in 2003, although you won't be able to edit those. Having the 2003 policies set to false means that they haven't been applied in some time and
its best not to touch during the migration. My first step here (after making a mistake) is to Disabled the Automatic Email Update for all mailboxes. I can look up how I did this on a mass scale a little later.
I then created the policies in 2010 to use a custom attribute, as you had suggested, and when mailboxes were migrated over, I made sure those accounts had the Attribute and then checked the box to auto apply the address policy.
Someone else may have a better answer for you, but this is how I saved my butt in a larger organization.
Jason Apt, Microsoft Certified Master | Exchange 2010
My Blog

Exchange 2003 -2010 cross forest (NDR 5.4.6)

Hi.
Have: Exchange 2003+2010 in source forest. Exchange 2010 in target forest.
Successful migrate mailbox to target forest (in source forest this mailbox convert to mailuser).
When try send e-mail to this mailbox (it`s in target forest) from Exchange 2003 mailbox get this:
A configuration error in the e-mail system caused the message to bounce between two servers or to be forwarded between two recipients.
If send from Exchange 2010 (source/target) - all mail ok.
If delete this mailuser (in source forest) - all set to ok.
x500?
Please, help.
Thanks.

Hi,
In the error event, 5.4.6 means "Routing loop detected" (RFC1893).
This issue occurs if the source Exchange organization is authoritative for the target domain. Because the source Exchange organization is responsible for mail delivery to target, the categorizer tries to find locally a recipient for
that message. The categorizer does not succeed, and then you receive the NDR.
More details in the following KB:
You receive an NDR with a 5.4.6 status code when you send a message to a specific domain in Exchange
http://support.microsoft.com/kb/324732/en-us
Hope it is the solution.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Exchange 2013/2010 - Co-Existence, URLs.

Hey Team,
I am sure this is well documented and i for some reason cant seem to get good solid answer. But here is my questions. what are the correct URL settings for (OWA, ActiveSync, EWS) etc for Exchange 2013/2010 in a coexistence scenario?
1) All servers in the same ad site
2) mail. autodiscover, pointed to the 2013 server
3) 2013 server is internet connected.
Am i supposed to clear all the 2010 URLs?, Just the external ones? Use a separate namespace?
Thanks,
Robert
Robert

This is well documented in the below post, I would recommend you check it:
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
In Exchange 2010/2013 coexistence scenario, CAS 2013 will proxy all connections to Exchange 2010.
How CAS2013 Picks a Target Legacy Exchange Server
It’s important to understand that when CAS2013 proxies to a legacy Exchange Client Access server, it constructs a URL based on the server FQDN, not a load balanced namespace or the InternalURL value.
When a CAS2013 starts up, it connects to Active Directory and enumerates a topology map to understand all the Client Access servers that exist within the environment. Every 50 seconds, CAS2013 will send a lightweight request to each
protocol end point to all the Client Access servers in the topology map; these requests have a user agent string of HttpProxy.ClientAccessServer2010Ping
Mohammad Saeed Abdelaziz | MCSE 2003 | MCTS: Lync, OCS, Exchange2007 | CCNP | UC Voice Specialist http://lyncrocks.wordpress.com/

Exchange 2003/2010 2003 AD to 2008 R2 AD

Setup:
DC's
2003 - 2, 2008 R2 -1 Domain functional level is Windows 2003.
Exchange
1 - 2003 SP2 running Exchange 2003, 1 - 2008 R2 running Exchange 2010 SP3.
All mail comes in through the Exchange 2003 server.
Question:
Both of our 2003 Domain Controllers are in bad shape and need to be replaced. We are going to replace them with 2008 R2 domain controllers. Can we change the domain functional level to 2008 R2 and leave the Exchange servers
alone or do we have to remove the Exchange 2003 server as well? Thanks for any help.

Hi
I would install the new DC, let replication take place and then seize the rolls to the new server. After that once you happy with everything then decommission the 2008 server. Are you running SBS with 2003 installed? if so you will need to first move all
your mailboxes over etc. before you decommission that DC.
It shouldnt be a problem to raise your domain level to 2008 R2 at all. I would plan this as you making big changes to your environment.
http://technet.microsoft.com/en-us/library/ff728623(EXCHG.141).aspx

Exchange 2003 - 2010. Moving public folders one at a time

Hi all,
I'm in the process of decomisioning our old Exchange 2003 server (long overdue after what has been a relativly smooth and trouble free transition to 2010). As the first step in the decomisioning process, I'm looking to move the public folders from the 2003
box to the 2010 box. From my understanding there are a couple of ways to achieve this (please correct me if I'm wrong). The first is to add the Exchange 2010 server as a new replication partner, allow for replication of the PFs to occur, and then remove the
2003 partner from the replication partnership. The other option is to use MoveAllReplicas.ps1.
I opted for the first option, but the problem I have is that the initial replication process started to generate a very large number of transaction logs on the Exchange 2010 server, to the point I was slightly conccerned I was going to run out of space on
the volume (our server is backed up nightly at which point the transaction logs are normally flushed).Whilst I know I could potentially increase the size of the volume or turn on cicular logging for the duration of the migration (neither of which is appealing
as it will involve down time), I was wondering if there was a way to move a smaller set of Public folders one at a time with a powershell command, or is it an all or nothing operation? My other option may be to replicate a small subset of folders everyday,
but that just a little painful as there are a large number of child folders with in the structure. Any other suggestions welcome!
Many thanks,
Rob

Hi,
If your Public Folder Database is large, you can use tool like Exfolders or ESM to add replica folder by folder.
A related article for your reference.
http://careexchange.in/moving-public-folders-from-exchange-2003-to-exchange-2010/
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or
suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
And it is recommended to replicate public folders off business hours.
Best regards,
Belinda Ma
TechNet Community Support

Namespace for Exchange 2003 == 2010 == 2013 Migration

Hi
Hope someone can help. I am working on an Exchange 2003 to 2010 migration, which will then quickly move onto a 2010 to 2013 migration and need some clarification on the namespaces to use. I am aware that if I do not do this right at the 2003
to 2010 migration, this will cause a headache at the 2010 to 2013 migration.
Some background:
2003 Functional Level Domain - 2 x 2008 DC's
Currently users are on a 2003 exchange cluster with a mix of RPC (internal users) and RPC over HTTP connections (roaming users)
We will be installing Exchange 2010 on a single server, with CAS, HUB and Mailbox roles and no load balancer, as we will be moving quickly to 2013.
We have two Kemp load balancers ready for Exchange 2013.
Exchange 2010 is installed on a single server (exh2010.domain.local) and configured with an CAS array name (exh-cas.domain.local) which is resolvable internally only.
Currently we have multiple smtp namespaces e.g. @company.com, @company2.com.
Our main website etc is www.company.com
Our public facing services are at https://service.mycompany.com
Our 2003 RPC address is https://webmail.mycompany.com
I understand that the 2010 RPC CAS array name should be separated from the Outlook Anywhere (RPC over HTTPS) address so that when 2013 takes over the HTTPS address, the RPC connections are not broken.
Two Questions:
Do we have to use the HTTPS same namespace for 2013 as we do in 2010? Its just I would want to test the Kemp load balancers before making them live (slow careful transition), and giving them a different namespace, e.g.
https://mail.mycompany.com would allow a migration, rather then a cutover.
Can we use the *.mycompany.com address rather then the company.com address, even though we have no SMTP addresses at mycompany.com? Can autodiscover still work?
Thanks in advance for any guidance
Cheers
Steve

1. No, but you can. Exchange 2013 will proxy all services for Exchange 2010, so if you set up everything right, you should be able to simply swing the name from Exchange 2010 to 2013.
2. Your web services can be published with any domain as long as the hostname is in the certificate. Only Autodiscover needs to match the e-mail domain(s). So in your example, you could publish OWA, ECP, ActiveSync, Web Services and OAB
at owa.mycompany.com. You would need autodiscover.company.com, autodiscover.company2.com, etc., but if you don't have e-mail addresses with mycompany.com, you don't need autodiscover.mycompany.com. If all users have a company.com e-mail address,
the you only need autodiscover.company.com as long as users know to enter that e-mail address when configuring profiles on PCs or devices. If you're going to have to have Autodiscover for multiple domains, then you might consider using an SRV record
instead because it can greatly simplify your certificate requirements.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Exchange Server 2010 SP3 test environment - email flow to/from internet

Today I set up test environment for Exchange Server 2010 SP3 - domain controller running Windows Server 2008 R2 SP1, Exchange Server 2010 SP3 on Windows Server 2008 R2 SP1 and client computer running Windows 7 Pro SP1 x64 with Outlook Pro 2010 x64. These
machines are VMs on vSphere 5.0 cluster made of 4 esxi 5.0 hosts.
I have three years of experience in working with Exchange Server 2010 in my production environment but until recently I have not had enough resources to build a test environment. Does "testing" Exchange Server 2010 infrastructure have
a real life purpose considering the fact that only internal email flow is possible since authoritative SMTP accepted domain is not hosted anywhere thus not visible to outside world. This limited email flow combined with absence of possibility to test
ActiveSync, Outlook Anywhere, OWA from WAN, . . . really hurt and make Exchange Server rare technology that can not be tested completely before introducing something new into the production. Services that are not possible to test from the outside world are
useless and whole point of Exchange-like technologies is availability from anywhere and from whatever device.

I set up Internet Send Connector (by default this type of send connector uses DNS MX records to route email automatically). Having sent an email to my gmail account I did not receive it and in transport logs I saw that mx record was found successfully
but there is the following line:
2014-08-05T20:39:51.942Z,Internet Connector,08D17F000FE36010,1,,2a00:1450:4013:c01::1b:25,*,,"Failed to connect. Error Code: 10051, Error Message: A socket operation was attempted to an unreachable network 2a00:1450:4013:c01::1b:25"
I tried also to send an email to my production email address (we have Symantec Messaging Gateway which is used as a smart host (antispam,antimalware,content filter appliance)) but then error is:
2014-08-05T20:50:08.395Z,Internet Connector,08D17F000FE36019,1,,91.238.7.10:25,*,,"Failed to connect. Error Code: 10061, Error Message: No connection could be made because the target machine actively refused it 91.238.7.10:25"
Telnet from test exchange to 91.238.7.10 on port 25 also is not working.

Exchange 2003 - 2010 Local Mail box move Error

Hey everyone,
I have just finished a transition from Microsoft Exchange 2003 to 2010, and I am having problem with moving the Legacy mailboxes over.
I have managed to move all the mail boxes over bar 2, using the " New local move Request".
So the problem is just these 2 mail boxes with the same error as below.
Any Advice?
Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:00:39
Sifiso Mguni
Failed
Error:
Service 'net.tcp://tvt-exchange.vtrust.local/Microsoft.Exchange.MailboxReplicationService' encountered an exception. Error: MapiExceptionLogonFailed: Unable to open message store. (hr=0x80040111, ec=-2147221231)
Diagnostic context:
    Lid: 18969   EcDoRpcExt2 called [length=131]
    Lid: 27161   EcDoRpcExt2 returned [ec=0x0][length=48][latency=0]
    Lid: 23226   --- ROP Parse Start ---
    Lid: 27962   ROP: ropLogon [254]
    Lid: 17082   ROP Error: 0x80040111
    Lid: 26937
    Lid: 21921   StoreEc: 0x80040111
    Lid: 31418   --- ROP Parse Done ---
    Lid: 22753
    Lid: 21817   ROP Failure: 0x80040111
    Lid: 26297
    Lid: 16585   StoreEc: 0x80040111
    Lid: 32441
    Lid: 1706    StoreEc: 0x80040111
    Lid: 24761
    Lid: 20665   StoreEc: 0x80040111
    Lid: 25785
    Lid: 29881   StoreEc: 0x80040111
Exception details: MapiExceptionLogonFailed (80040111): MapiExceptionLogonFailed: Unable to open message store. (hr=0x80040111, ec=-2147221231)
Diagnostic context:
    Lid: 18969   EcDoRpcExt2 called [length=131]
    Lid: 27161   EcDoRpcExt2 returned [ec=0x0][length=48][latency=0]
    Lid: 23226   --- ROP Parse Start ---
    Lid: 27962   ROP: ropLogon [254]
    Lid: 17082   ROP Error: 0x80040111
    Lid: 26937
    Lid: 21921   StoreEc: 0x80040111
    Lid: 31418   --- ROP Parse Done ---
    Lid: 22753
    Lid: 21817   ROP Failure: 0x80040111
    Lid: 26297
    Lid: 16585   StoreEc: 0x80040111
    Lid: 32441
    Lid: 1706    StoreEc: 0x80040111
    Lid: 24761
    Lid: 20665   StoreEc: 0x80040111
    Lid: 25785
    Lid: 29881   StoreEc: 0x80040111
Exchange Management Shell command attempted:
'vtrust.local/Valley Trust Users/Users/Staff/Sifiso Mguni' | New-MoveRequest -TargetDatabase 'Mailbox Database 0271422377'
Elapsed Time: 00:00:39

HI. I had the same problem while trying to migrate a user from Exchange 2003 to 2010. And the same error as you have appeared. I tried to skip more e-mails in case some fails but couldn't get successful.
Check if the user have accessed the mail at all on Exchange 2003 because if the user didn't accessed it it may contain many mails and when we try to migrate the mailbox, the mailbox size on Exchange 2003 may be grater than on the 2010.
On my case after many reading we just see that the user didn't access the mail at all on our Exchange 2003. (Let me know if you need to know how you can check if the user accessed the mail or not or you can just google it). So what we have done is we just
reset the user password on Active Directory. Because as you can see the error is related with Logon Failure.
This solved the issue for me. Can you check this way
Thanks

Exchange 2003/2010 Coexistance - User login Issue

Hello
We have deployed Exchange 2010 SP3 in coexistance with 2003 and created connectors.
2003/2010 both Users are not able to login on 2010 OWA and error showing that username/PW is wrong although they are working on OWA 2003 perfectly.
When i add the same user to the local admin group on the Ex2010 server, it works fine with email send/receive. i am confused please suggest what i am missing....Regards
Waseem

Hello
This is the error that occured during that time.
SACL Watcher servicelet encountered an error while monitoring SACL change.
Got error 1722 opening group policy on system SERVER.DOMAIN in domain MYDOMAIN.
Event ID 6003
Source : MSExchange SACL Watcher
i am not sure if its related to this problem.
Secondly i have also tested to run the "Microsoft Exchange Active Directory Topology Service" with a new user having all the rights of exchange & AD groups but its showing giving the error that it cant run the dependency
services. currently this service is running with the local account rights.
I just add the test users (moved from 2003 and new user created in 2010) to the local admin group and it works fine, please give any idea what may be the problem in rights or something else ??
Regards
Waseem

Providing voicemail in a trusted-domain Exchange 2003 - 2010 upgrade

As a result of a merger, we are upgrading from Exchange 2003 in the same domain as a Unity 5.0 server to an Exchange 2010 server in a trusted domain in a different forest. The Exchange 2003 server is still up, but mailboxes are being moved to the 2010 server. The goal of getting Unity to somehow deliver voicemail to the users who have been moved to the 2010 server in the other domain is only temporary, as we will be replacing our on-premesis system with a hosted solution in a couple of months. So I'm looking for something quick, but it doesn't have to be elegant or permanent.
As Unity cannot connect to a partner Exchange server in a different forest, I see the most likely options as:
Move Unity to the new domain. Wanted to see how easy it would be to do this, as Cisco recommends that the same version of Unity be installed on a server in the new domain as is currently running the server in the old domain. I believe I have the original install disks, but can't speak to whether or not upgrades have been applied to the current (old) server since it went in 5 years ago.
Convert current subscribers into "Internet Subscribers" - This is not currently working, I believe, because Unity's partner server is the 2003 server, which lives in the same domain as the Unity server, but is also a part of the same Exchange group as the 2010 server in the new domain. When I create an "internet subscriber", I'm creating a contact with an email address that already exists in the domain.
For 1., Cisco says I have to install the same version of Unity in the new domain and then restore the database to it. Would I need to roll back items like the Engineering Special that I just installed? As long as the install disk is for 5.0(1) and the server's currently running 5.0(1), am I OK?
For 2., Is it possible to do anything with Internet subscribers? This seems like it would be easier, but also seems like it's not working because of the fact that the partner server is not recognizing addresses for the Internet subscribers as external.
Any assistance or insights would be greatly appreciated.
Kevin

Hi,
We can move the mailbox from Exchange 2003 to Exchange 2010 as a linked mailbox in Exchange 2010. The moved mailbox would be a disabled User Object which is linked to a separate enabled user object in an Account Forest (Exchange 2003 forest).
We can use the Prepare-MoveRequest.ps1 script in the Shell to prepare the cross-forest mailbox moves:
https://technet.microsoft.com/en-us/library/ee861103(v=exchg.141).aspx
Then we can create a remote legacy move request to move mailbox:
https://technet.microsoft.com/en-us/library/dd876952(v=exchg.141).aspx
Additionally, for more information about migration from Exchange 2003 to Exchange 2010, please read:
http://blogs.technet.com/b/schadinio/archive/2010/08/11/exchange-2010-cross-forest-mailbox-moves.aspx
Regards,
Winnie Liang
TechNet Community Support

Exchange 2013 / 2010 co-existence - Outlook won't connect to Exchange 2010 mailboxes

Greetings! I have a lab set up at home where I have been testing co-existence of Exchange 2013 and 2010 for a future corporate upgrade project.
I am running into some odd behavior. Any mailbox that has been migrated to Exchange 2013 works just fine, however, when I try to set up Outlook for a mailbox still on Exchange 2010 I receive errors. OWA works just fine for these Exchange
2010 mailboxes, it is just Outlook that has the problem. This is what I am running into:
1. Outlook uses autodiscover to locate server settings. It fails at the 'logging on to mail server' step saying that Exchange isn't available; Outlook must be connected, etc.
2. It then gives me the settings box for Exchange server and Mailbox. This is auto populated with one of the Exchange 2013 servers (there are 3 of them, all have both MBX and CAS role). If I then change the server to the Exchange 2010 CAS server,
and hit 'check names', it underlines the very same entries (like it found them this time) that were there initially and goes on to finish the configuration.
3. When I launch Outlook with this Exchange 2010 user, it fails to open with the error message that the set of folders couldn't be opened.
I've been doing as much research on this as I can. I've tried disabling IPv6 to no avail. It seems as if perhaps the issue is with Exchange 2013 proxying the request back to the Exchange 2010 servers but I am not sure what to check in that regards.
Any suggestions? Thanks in advance!

Hi,
Don´t disable IPV6 on an Exchange Server, it is, in my opinion not necessary - also applies for AD.
You can use your original SSL Cert for your new Ex 2013 environment.
In dns you want two host A records: mail.domain.com and autodiscover.domain.com
On your 2013 set your internal and external virtual directories to mail.domain.com
leave autodiscover and Powershell alone.
Also set the autodiscover URI to your Certificate name ie. mail.domain.com
Set-ClientAccessServer -Identity "YourCASServer" -AutoDiscoverServiceInternalUri "https://mail.domain.com/autodiscover/autodiscover.xml"
Thanks. I wanted to give some additional info before I run any commands. I currently have an A record for autodiscover and it is pointed to the Exchange 2013 DAG/cluster IP. I have a 3 entries for mail.domain, for DNS round robin; basically
it is listed 3 times for the IP of each of my Exchange 2013 servers. Does any of this sound problematic?

Exchange 2003-2010 co-existence environment

Similar Messages

Maybe you are looking for