Exchange 2010 - 2003 coexistence "unable to relay"

Hi
I have a customer with a Exchange 2010 / 2003 coexistence. 
The Exchange 2010 has 3 CAS/HT servers. 
When sending mails from 2003 to the outside world, one of the CAS/HT is giving me "unable to relay".
Right now I have removed it from the routing group connector, but do you have any ideas where to look?
BR
Steen

Hello,
If there is only AD site, the receive connector is not needed.
If there are multiple AD sites, when you send message to other AD sites, the receive conenctor is needed. If you send message from exchange 2003 to exchange 2010 or exchange 2010 to exchange 2003, the routing group connector is needed.
Cara Chen
TechNet Community Support

Similar Messages

  • External emails not received after shutdown of Exchange 2010 in coexistence with Exchange 2013

    I have exchange 2013 and exchange 2010 in coexistence mode. All mailboxes have been moved to Exchange 2013 and firewall/spamfilters already pointed to Exchange 2013 CAS server. I can receive/send from and to external addresses, however when I shutted down
    the Exchange 2010 all incoming external mails were not received. What could be the cause?

    Start by re-checking how the device that takes the traffic from the external MX IP to internal is configured.
    Sniff the traffic to ensure that it is hitting 2013 directly.
    Cheers,
    Rhoderick
    Microsoft Senior Exchange PFE
    Blog:
    http://blogs.technet.com/rmilne 
    Twitter:   LinkedIn:
      Facebook:
      XING:
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

  • 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."

  • Use Exchange 2010 Hybrid Edition for SMTP relay

    Thanks guys.
    hmmm.
    I did try and telnet on port 25 to the hybrid and get the welcome, when i enter the mail from command and enter a valid email address, i get "530 5.7.1 Client was not authenticated"
    I have exchange 2003 admin experiance and and learning my way around the 365 environment still
    

    Hi all,
    we recently moved our Exchange 2003 to Office 365 using a Hybrid Exchange 2010 to migrate the users.
    the migration is complete and we have kept the Exchange 2010 Hybrid Edition running to enable us to mail enable new AD users after the DirSync has synchronized the user to the tenant.
    has anyone used this limited version of Exchange as an smtp relay for network devices, copiers etc?
    This topic first appeared in the Spiceworks Community

  • Move mailbox from exchange 2010 2003 , Transient error MapiExceptionLogonFailed has occurred.

    We are currently migrating from Exchange 2003 to Exchange 2010, same domain.
    We have successfully moved some mailboxes from exchange 2003 to exchange 2010 without any problems.
    Now we need to move 1 mailbox back from exchange 2010 to exchange 2003.
    After creating the moverequest it stucks on 0% and the log shows the error below.
    After using Bing I found this post -> http://social.technet.microsoft.com/Forums/exchange/en-US/ef41ae05-8816-4c0c-968a-c48f0e3d50b5/move-mailbox-back-from-exchange-2010-to-exchange-2003-failure?forum=exchangesvrdeploylegacy
    This suggest -> 
    After I give FULL permissions to each Mailbox Stores on Exchange 2003 server, I was able to move my mailbox back onto the Exchange 2003 server. In details:
    Simply right click Storage Group\Mailbox Store and go to Security, in there you may see Exchange Servers group already there, if no add it in, then give it FULL permissions! and thats it!
    Create a new move request but still stuck on 0% and error as below
    20-3-2014 16:32:10 [ex2010p11] 'contoso.com/Users/exadmin' created move request.
    20-3-2014 16:32:11 [ex2010p21] The Microsoft Exchange Mailbox Replication service 'exchangep21.contoso.com' (14.3.151.0 caps:07) is examining the request.
    20-3-2014 16:32:11 [ex2010p21] Connected to target mailbox 'Primary (82b54f9e-27ff-44d2-9142-f949d567e1e7)', database 'ex2003\Basic\Basic', Mailbox server 'ex2003.contoso.com' Version 0.0 (Build 7638.0).
    20-3-2014 16:32:11 [ex2010p21] Connected to source mailbox 'Primary (82b54f9e-27ff-44d2-9142-f949d567e1e7)', database 'EX2010DB', Mailbox server 'ex2010p20.contoso.com' Version 14.3 (Build 174.0).
    20-3-2014 16:32:11 [ex2010p21] Request processing started.
    20-3-2014 16:32:11 [ex2010p21] Transient error MapiExceptionLogonFailed has occurred. The system will retry (1/60).
    Error details: MapiExceptionLogonFailed: Unable to make connection to the server. (hr=0x80040111, ec=1010)
    Diagnostic context:
        Lid: 13720   dwParam: 0x6D9      Msg: EEInfo: Flags: 0
        Lid: 11672   dwParam: 0x6D9      Msg: EEInfo: NumberOfParameters: 4
        Lid: 8856    dwParam: 0x6D9      Msg: EEInfo: prm[0]: Unicode string: ncacn_ip_tcp
        Lid: 8856    dwParam: 0x6D9      Msg: EEInfo: prm[1]: Unicode string: ex2003
        Lid: 12952   dwParam: 0x6D9      Msg: EEInfo: prm[2]: Long val: -545057711
        Lid: 12952   dwParam: 0x6D9      Msg: EEInfo: prm[3]: Long val: 382312662
        Lid: 45169   StoreEc: 0x824     
        Lid: 44273  
        Lid: 59431   EMSMDB.EcDoConnectEx called [length=163]
        Lid: 34855   EMSMDB.EcDoConnectEx returned [ec=0x3F2][length=56][latency=0]
        Lid: 56945  
        Lid: 59431   EMSMDB.EcDoConnectEx called [length=163]
        Lid: 34855   EMSMDB.EcDoConnectEx returned [ec=0x3F2][length=56][latency=0]
        Lid: 59505   StoreEc: 0x3F2     
        Lid: 52465   StoreEc: 0x3F2     
        Lid: 60065  
        Lid: 33777   StoreEc: 0x3F2     
        Lid: 59805  
        Lid: 52209   StoreEc: 0x3F2     
        Lid: 56583  
        Lid: 52487   StoreEc: 0x3F2     
        Lid: 19778  
        Lid: 27970   StoreEc: 0x3F2     
        Lid: 17730  
        Lid: 25922   StoreEc: 0x3F2     
       at Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, SafeExInterfaceHandle iUnknown, Exception innerException)
       at Microsoft.Mapi.ExRpcConnection.Create(ConnectionCache connectionCache, ExRpcConnectionCreateFlag createFlags, ConnectFlag connectFlags, String serverDn, String userDn, String user, String domain, String password, String httpProxyServerName,
    Int32 ulConMod, Int32 lcidString, Int32 lcidSort, Int32 cpid, Int32 cReconnectIntervalInMins, Int32 cbRpcBufferSize, Int32 cbAuxBufferSize, Client xropClient, Byte[] clientSessionInfo, TimeSpan connectionTimeout)
       at Microsoft.Mapi.MapiStore.OpenMapiStore(String serverDn, String userDn, String mailboxDn, Guid guidMailbox, Guid guidMdb, String userName, String domainName, String password, String httpProxyServerName, ConnectFlag connectFlags, OpenStoreFlag
    storeFlags, CultureInfo cultureInfo, Boolean wantRedirect, String& correctServerDN, ClientIdentityInfo clientIdentity, String applicationId, Client xropClient, Boolean wantWebServices, Byte[] clientSessionInfo, TimeSpan connectionTimeout)
       at Microsoft.Mapi.MapiStore.OpenMailbox(String serverDn, String userDn, String mailboxDn, String userName, String domainName, String password, String httpProxyServerName, ConnectFlag connectFlags, OpenStoreFlag storeFlags, CultureInfo cultureInfo,
    WindowsIdentity windowsIdentity, String applicationId)
       at Microsoft.Exchange.MailboxReplicationService.MapiUtils.OpenSystemMailbox(Guid mdbGuid, String serverDN, String dcName, NetworkCredential cred, String& systemMailboxDn)
       at Microsoft.Exchange.MailboxReplicationService.LocalMailbox.OpenSystemMailbox()
       at Microsoft.Exchange.MailboxReplicationService.LocalMailbox.Microsoft.Exchange.MailboxReplicationService.IMailbox.SaveSyncState(Byte[] key, String syncStateStr)
       at Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.<>c__DisplayClass57.<Microsoft.Exchange.MailboxReplicationService.IMailbox.SaveSyncState>b__56()
       at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation)
       at Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.Microsoft.Exchange.MailboxReplicationService.IMailbox.SaveSyncState(Byte[] key, String syncState)
       at Microsoft.Exchange.MailboxReplicationService.MailboxCopierBase.ClearSyncState()
       at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.<>c__DisplayClass23.<CleanupOrphanedDestinationMailbox>b__22(MailboxMover mbxCtx)
       at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.ForeachMailboxContext(MailboxMoverDelegate del)
       at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.CleanupOrphanedDestinationMailbox(Object[] wiParams)
       at Microsoft.Exchange.MailboxReplicationService.CommonUtils.CatchKnownExceptions(GenericCallDelegate del, FailureDelegate failureDelegate)
    Error context: --------
    Operation: IMailbox.SaveSyncState
    OperationSide: Target
    Primary (82b54f9e-27ff-44d2-9142-f949d567e1e7)
    Key: F2FA63B0116C564EA4C598D69786443D9E4FB582FF27D2449142F949D567E1E7E0CA914F6695624C98892FA527AAA91E
    SyncStateLength: 0
    20-3-2014 16:32:41 [ex2010p21] The Microsoft Exchange Mailbox Replication service 'ex2010p21.contoso.com' (14.3.151.0 caps:07) is examining the request.
    20-3-2014 16:32:41 [ex2010p21] Connected to target mailbox 'Primary (82b54f9e-27ff-44d2-9142-f949d567e1e7)', database 'ex2003\Basic\Basic', Mailbox server 'ex2003.contoso.com' Version 0.0 (Build 7638.0).
    20-3-2014 16:32:41 [ex2010p21] Connected to source mailbox 'Primary (82b54f9e-27ff-44d2-9142-f949d567e1e7)', database 'EX2010DB', Mailbox server 'ex2010p20.contoso.com' Version 14.3 (Build 174.0).
    20-3-2014 16:32:41 [ex2010p21] Request processing started.
    20-3-2014 16:32:41 [ex2010p21] Transient error MapiExceptionLogonFailed has occurred. The system will retry (2/60).

    Hello，
    When you move mailbox from exchange 2010 to exchange 2003, please check if the following situations exist:
    http://technet.microsoft.com/en-us/library/dd638157(v=exchg.141).aspx
    Before you move mailbox again, please clear the previous move request.
    I recommend you use EXBPA to check your exchange server 2003 and exchange 2010.
    Please check if inheritable permission is missing on the mailbox store on Exchange Server 2003.
    Cara Chen
    TechNet Community Support

  • Exchange Server 2013 OAB Web Distribution Configuration in Exchange 2010 & 2013 Coexistence.

    Hi,
    We have OAB Issue for Exchange 2010 Users in our Organization.
    We have Exchange 2010 and Exchange 2013 Coexistence.While Checking in Exchange Server 2010 Server OAB properties in Org Configuration--> Mailbox-->OAB Properties -->Distribution we are not seeing any CAS servers and Its Grayed Out.
    Please let us know How to add Exchange 2010 CAS in Exchange 2013 Web distribution.

    They made alot changes with the OAB in Exchange 2013, and it doesn't really function in the same manner as it did in 2010.  It might be best to take a look at the following blog posts from the Exchange Team, they should give you a better understanding
    on how it works and how to manage it going forward.
    http://blogs.technet.com/b/exchange/archive/2012/10/26/oab-in-exchange-server-2013.aspx
    http://blogs.technet.com/b/exchange/archive/2013/01/14/managing-oab-in-exchange-server-2013.aspx
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

  • 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

  • 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 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 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    

  • 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 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 Server 2003 :: ActiveSync :: Unable to send out attachments

    Hi All,
    I am facing a weird issue with SBS 2003 (windows server 2003 sp2 with microsoft exchange 2003 sp2) Microsoft Exchange ActiveSync. ActiveSync users are able to configure the devices just fine, send and receive email fine as well but when they try to send
    any attachment the email will stay in the outbox.
    So far i have tried the following fixes
    made sure the permissions on the exchange vdirs and activesync vdir are correct
    c:\windows\temp and %temp% location has read/write access to authenticated users
    uploadreadaheadsize (thru adsutil.vbs) and messagesizelimit for oma reg key are bumped up (20MB each)
    testremoteexchange connectivity analyzer shows all green
    Now, if i make user the member of administrators group and try to send an email with attachment (i am sending a screenshot of 2.3mb) it goes out fine.
    IIS logs shows HttpServerStatusError 500used logparserstudio to parse the iis file
    cs-username
    cs-uri-stem
    HTTPstatus
    w3-status-details
    domain\testas
    /Microsoft-Server-ActiveSync
    500
    HttpStatusServerError
    any pointers how this issue can be dealt with and resolved, will be appreciated.
    Regards,
    Nav
    Regards, Navdeep [a.k.a v-2nas]

    any ninjas out there to crack this problem........
    Regards, Navdeep [a.k.a v-2nas]

  • Exchange 2010 Local Move Request with Error (hr=0x80004005, ec=1292)

    Trying to migrate from exchange 2003 to 2010.
    Ran a Local move request and received the following error.
    What can I do?
    Summary: 1 item(s). 0 succeeded, 1 failed.
    Elapsed time: 00:00:01
    Aman Amiri
    Failed
    Error:
    MapiExceptionMailboxInTransit: Unable to open message store. (hr=0x80004005, ec=1292)
    Diagnostic context:
        Lid: 45095   EMSMDB.EcDoRpcExt2 called [length=121]
        Lid: 61479   EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=48][latency=18]
        Lid: 23226   --- ROP Parse Start ---
        Lid: 27962   ROP: ropLogon [254]
        Lid: 17082   ROP Error: 0x50C     
        Lid: 26937  
        Lid: 21921   StoreEc: 0x50C     
        Lid: 31418   --- ROP Parse Done ---
        Lid: 22753  
        Lid: 21817   ROP Failure: 0x50C     
        Lid: 26297  
        Lid: 16585   StoreEc: 0x50C     
        Lid: 32441  
        Lid: 1706    StoreEc: 0x50C     
        Lid: 24761  
        Lid: 20665   StoreEc: 0x50C     
        Lid: 25785  
        Lid: 29881   StoreEc: 0x50C     
    Exchange Management Shell command attempted:
    'RWR.local/MyBusiness/Users/SBSUsers/Aman Amiri' | New-MoveRequest -TargetDatabase 'Mailbox Database 1110868248' -BadItemLimit '0'
    Elapsed Time: 00:00:01

    Hi
    Is the database on Exchange 2010/2003 mounted and all services started?
    Is your account part of Organization Management and able to perform the move requests?

  • Migrate & coexist Exchange 2010 to 2010 in two different site under same domain

    Hi all,
    The initial plan was planning to coexist Exchange 2010 (old data center) & 2013 (new data center) .
    Unfortunately there was a problem of upgrading the existing exchange 2010 sp2 to 2010 sp3 and Microsoft said they don't support this anymore.
    So the only plan I can think of is build another exchange 2010 with SP3 (new data center)  to coexist with existing exchange 2010 SP2 first then followed by exchange 2013.
    I don't see any relevant info on the Internet for the coexistence of exchange 2010 SP2 and SP3. can you please share some detailed steps or info?
    Thank you very much in advanced.

    Hi all,
    The initial plan was planning to coexist Exchange 2010 (old data center) & 2013 (new data center) .
    Unfortunately there was a problem of upgrading the existing exchange 2010 sp2 to 2010 sp3 and Microsoft said they don't support this anymore.
    So the only plan I can think of is build another exchange 2010 with SP3 (new data center)  to coexist with existing exchange 2010 SP2 first then followed by exchange 2013.
    I don't see any relevant info on the Internet for the coexistence of exchange 2010 SP2 and SP3. can you please share some detailed steps or info?
    The last database upgrade exchange 2010 SP3 is unable to mount server with Exchange 2010 SP2 i.e., there is no database schema upgrade from SP1 or SP2 to SP3. Please check this link :
    https://www.youtube.com/watch?v=M4hJfdqTe5s
    You may download exchange Server 2010 Service Pack 3 from here :http://www.microsoft.com/en-us/download/details.aspx?id=36768
    This Exchange Server 2010 SP3 software may be used to perform a new installation or to update an existing Exchange Server 2010 installation to Service Pack 2 (SP2) level.
    Moreover, to migrate the mailbox database from exchange 2010 to 2013, you may consider on this exchange migration tool (http://www.exchangemigrationtool.com/) that can be a good approach for you.

Maybe you are looking for