Remove legacy Send connectors from Exchange 2010 after migration

Hello.
I have just removed the last legacy exchange 2003 server form our organisation.
I followed the official MS documentation for this and the remove went to plan with no errors.
The only issue I now have is that I have 2 legacy exchange send connectors in the Hub Transport view.
I have tried to disable and remove them but I get an undocumented error. The warning I get in the exchange server event logs is as follows
Process w3wp.exe () (PID=8148). Object [CN="Connector name",CN=Connections,CN="Organisation Name",CN=Routing Groups,CN="Group Name",CN=Administrative Groups,CN="Org Name",CN=Microsoft Exchange,CN=Services,CN=Configuration,DC="Domain
Name",DC="local"]. Property [HomeMtaServerId] is set to value ["Domain Name"/Configuration/Deleted Objects/Microsoft MTA
DEL:1bfa936f-c57e-4b7d-ad03-258acb560ad3], it is pointing to the Deleted Objects container in Active Directory. This property should be fixed as soon as possible.
Is ADSI edit the best way to remove these entries or is there another way to disable and remove?
Regards
Lee Gregory

Hi,
If the legacy send connector is no longer needed, it is ok to remove it from ADSIEdit.
For reference: select configuration as Connection point > domain > Services > MS Exchange > organizaiton name > Administrative Groups > Exchange Administrative Group > Routing Groups > First Routing Group > Connections 
Regards,
Rebecca Tu
TechNet Community Support

Similar Messages

  • Remove Domain Controller role from Exchange 2010 Server

    Hi team,
    There is a client with Domain Controller (2008 R2) running together with Exchange Server 2010 SP3. However there were some huge problems with Exchange and DC therefore since the best practice is to keep those roles seperately, they are in need of doing so.
    Can someone please suggest me the best approach? The server they use right now is with 16GB therefore whatever done, Exchange should be on that machine and DC on the other 6GB.
    Option 01.
    Both Exchange and DC are together
    Install new Exchange on a temporary Server and move everything make that Exchange server the only working primary
    Remove exchange from the DC server
    Promote new Additional DC and promote it with FSMO and make primary
    Demote the old DC from the 16GB server
    Install Exchange again on the 16GB server and move everything from the temporary server
    Or Option 02
    Add new additionall Domain Controller server and make it primary with GC and FSMO
    Run dcpromo to demote the old Domain controller role from where the Exchange Server too is installed
    Once DC role is removed from the exchange server, set up DNS and perform a restart, so Exchange will identify the new GC and domain controller
    Live happily ever after
    Thank You,
    Cheers!!

    Adding/Removing the DC-Role while Exchange is installed, is not supported so forget about your Option 2.
    Here's what I would do:
    1. Install a new GC/DC (move FSMO etc)
    2. Install a new temporary server for Exchange and move everthing over
    3. Decomission the old Exchange Server
    4. Demote the old Domain Controller
    5. Install Exchange on a newly freshly installed OS and move everything over from your temp server
    Martina Miskovic

  • Send connector from exchange 2007

    Currently since I have both environments up, I see that Exchange 2013 is using the send connector that was created in my exchange 2007 environment.  Will this send connector go away once I bring down my exchange 2007 environment? Shoould I create
    a new one for Exchange 2013?

    Hi
    From what i have seen running ex2010 and upgrading to 2013 it stayed (exchange 2013 is clever :-)). you can just modify your send connector and make sure that the settings are for your exchange 2013 server.

  • Apple Mail can't send or receive messages from Exchange 2010, Mountain Lion

    Over the last several weeks, I have been unable to send or recieve e-mails from Exchange 2010 in a corprate environment.  I have deleted and re-added the account several times, and sometimes it will fix the issue.  Other times it won't.  I have also tried deleting the account, clearing the cache in ~/Library/Mail/V2/EWS*, and then re-adding the account.  It resolves the issue temporarily, but then returns to not being able to sync.  I've tested it with a number of other users accounts on the same Exchange system, and it's working as expected.  OSX is version 10.8.4 with current patches as of 10/7/2013.
    The connection doctor shows that the connection to EWS is green.  The activity monitor looks like it's updating the folders properly on sync.
    Here is the message I get in the logs in high volume when Console logging is turned on:
    *** Assertion failure in -[EWSConnection sendMessage:forRequest:], /SourceCache/Message/Message-1508/Message/EWS/EWSConnection.m:555
    Received an unexpected error: Error Domain=EWSExchangeWebServicesErrorDomain Code=277 "The operation couldn’t be completed. (EWSExchangeWebServicesErrorDomain error 277.)" UserInfo=0x7fd1c9a97e70 {EWSErrorMessage=The request failed schema validation., NSUnderlyingError=0x7fd1c85106f0 "The operation couldn’t be completed. (SOAPWebServicesErrorDomain error -1000.)"}, response: (null)
              0   CoreMessage                         0x00007fff86a4a517 -[MFAssertionHandler _handleFailureWithPreamble:description:arguments:] + 141
              1   CoreMessage                         0x00007fff86a4a388 -[MFAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 215
              2   Message                             0x00007fff8daa5a8e -[EWSConnection sendMessage:forRequest:] + 762
              3   Message                             0x00007fff8daaeab3 -[EWSGateway sendMessage:forRequest:] + 69
              4   Message                             0x00007fff8dac543a -[EWSRequestOperation executeOperation] + 110
              5   CoreMessage                         0x00007fff86a65b80 -[MonitoredOperation main] + 219
              6   Foundation                          0x00007fff92475926 -[__NSOperationInternal start] + 684
              7   Foundation                          0x00007fff9247d0f1 __block_global_6 + 129
              8   libdispatch.dylib                   0x00007fff87f4af01 _dispatch_call_block_and_release + 15
              9   libdispatch.dylib                   0x00007fff87f470b6 _dispatch_client_callout + 8
              10  libdispatch.dylib                   0x00007fff87f481fa _dispatch_worker_thread2 + 304
              11  libsystem_c.dylib                   0x00007fff9068ad0b _pthread_wqthread + 404
              12  libsystem_c.dylib                   0x00007fff906751d1 start_wqthread + 13

    Over the last several weeks, I have been unable to send or recieve e-mails from Exchange 2010 in a corprate environment.  I have deleted and re-added the account several times, and sometimes it will fix the issue.  Other times it won't.  I have also tried deleting the account, clearing the cache in ~/Library/Mail/V2/EWS*, and then re-adding the account.  It resolves the issue temporarily, but then returns to not being able to sync.  I've tested it with a number of other users accounts on the same Exchange system, and it's working as expected.  OSX is version 10.8.4 with current patches as of 10/7/2013.
    The connection doctor shows that the connection to EWS is green.  The activity monitor looks like it's updating the folders properly on sync.
    Here is the message I get in the logs in high volume when Console logging is turned on:
    *** Assertion failure in -[EWSConnection sendMessage:forRequest:], /SourceCache/Message/Message-1508/Message/EWS/EWSConnection.m:555
    Received an unexpected error: Error Domain=EWSExchangeWebServicesErrorDomain Code=277 "The operation couldn’t be completed. (EWSExchangeWebServicesErrorDomain error 277.)" UserInfo=0x7fd1c9a97e70 {EWSErrorMessage=The request failed schema validation., NSUnderlyingError=0x7fd1c85106f0 "The operation couldn’t be completed. (SOAPWebServicesErrorDomain error -1000.)"}, response: (null)
              0   CoreMessage                         0x00007fff86a4a517 -[MFAssertionHandler _handleFailureWithPreamble:description:arguments:] + 141
              1   CoreMessage                         0x00007fff86a4a388 -[MFAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 215
              2   Message                             0x00007fff8daa5a8e -[EWSConnection sendMessage:forRequest:] + 762
              3   Message                             0x00007fff8daaeab3 -[EWSGateway sendMessage:forRequest:] + 69
              4   Message                             0x00007fff8dac543a -[EWSRequestOperation executeOperation] + 110
              5   CoreMessage                         0x00007fff86a65b80 -[MonitoredOperation main] + 219
              6   Foundation                          0x00007fff92475926 -[__NSOperationInternal start] + 684
              7   Foundation                          0x00007fff9247d0f1 __block_global_6 + 129
              8   libdispatch.dylib                   0x00007fff87f4af01 _dispatch_call_block_and_release + 15
              9   libdispatch.dylib                   0x00007fff87f470b6 _dispatch_client_callout + 8
              10  libdispatch.dylib                   0x00007fff87f481fa _dispatch_worker_thread2 + 304
              11  libsystem_c.dylib                   0x00007fff9068ad0b _pthread_wqthread + 404
              12  libsystem_c.dylib                   0x00007fff906751d1 start_wqthread + 13

  • Send and receive from Exchange 2010

    Hello,I have a doubt about sending and receiving mail from Exchange 2010. I have an Exchange 2010 organization, with antispam product between Exchange and Internet.I have a receive conector in my Exchange. In the Network tab, I have 0.0.0.0 255.255.255.255, and in the permission tabs, I have all checked (Anonymous, the 3 for Exchange and Partners).This way, I can send and receive all mail, from - to my organization. If I connect from outside and try to send mail without identification (telnet and try a dummy email address without any credentials), the antispam server blocks the rely. But if from inside the company I telnet the Exchange server, I can send mail from any non existing account, to any account inside my Exchange Organization.If I uncheck the Anonymous tick in the permission tab, I stop receive mail from outside.What have I...
    This topic first appeared in the Spiceworks Community

    Hi,
    What’s the user impact? If the issue only occur on specific users, I suggest we firstly take the troubleshooting from the client side.
    If the issue occurs to all the users, it’s seems the Outlook sync issue with the CAS server, not like a database issue. Do you configure the NLB for the CAS server?
    Thanks,
    Simon Wu
    TechNet Community Support

  • How many system mailboxes should be in exchange 2013 after moving from exchange 2010?

    Hi, I am moving mailboxes from exchange 2010 to exchange 2013, I noticed that in exchange 2013, besides discovery search mailbox, there are other 5 system mailboxes.(especially, there are 2 x Microsoft Exchange system mailboxes) Please see the pic attached.
    Does this look right? thanks

    Looks perfectly fine - Why MS decided to name two of the five arbitration mailboxes the same (Microsoft Exchange) is unclear but it is what it is :)
    In EMS:
    Martina Miskovic

  • Message looping between Exchange 2003 & Exchange 2010 after domain type changed to internal relay

    Hi
    We have a coexistence environment where we are currently migrating from Exchange 2003 to 2010 and have 80% of the users already on the Exchange 2010 platform. This is all within the same AD forest, let's call it FOREST1.AD.
    The problem I'm seeking help about is a message routing problem we had this morning where messages bound for the Exchange 2003 users started looping between Exchange 2003 and Exchange 2010. The problem started as a result of changing the accepted domain
    type to 'internal relay domain' for the purposes of establishing SMTP namespace sharing with an external Exchange environment (different forest, let's call it FOREST2.AD). The expectation was that after changing the domain type from authoritative to 'internal
    relay domain', Exchange 2010 would route messages for unknown recipients to the external environment and that would be the only effect of the change. The message routing to the external environment worked completely OK. However, later we noticed that Exchange
    2003 stopped delivering messages to its local users and started routing them to Exchange 2010 which would route the messages back to Exchange 2003 as that's where the recipients existed, only to have Exchange 2003 send them back to Exchange 2010 again.
    The Send connector to route the messages, for the shared namespace, to the external environment used the Exchange 2010 server as the source server. It makes sense and is expected that Exchange 2003 would send messages for any unknown recipients to Exchange
    2010 for onward delivery via the Send connector. But it is not expected for Exchange 2003 to not deliver messages to its own users using the store driver and instead routing them on to Exchange 2010.
    We fixed the problem by reversing the change and not only changed the domain type back to authoritative but also removed the Send connector for the specified shared namespace. However, we do need to understand why this problem happened and how to stop it
    from happening.
    We did test the shared SMTP namespace configuration using a test domain before applying the change to the domain that is used for production email traffic. Test users on Exchange 2003 with email addresses on the test domain did not experience this looping
    problem. This has been tested again after the production domain experienced the problem and there is no looping for the test domain. The only difference I noticed between the configuration for the test domain and the production domain is that while both domains
    existed as accepted domains of type 'internal relay domain' in Exchange 2010, there was a difference in configuration in Exchange 2003 where the test domain was not present on the recipient policy at all and the production domain was present there.
    This also makes me wonder if Exchange 2003 and Exchange 2010 in the same organization keep a separate configuration to determine which domain they are authoritative for. When you install Exchange 2010, it does add all the domains on the recipient policies
    to the accepted domains configuration but any new domains you add in accepted domains in Exchange 2010 are not added to the legacy recipient policy object.
    Can someone please help clarify these grey areas and explain why the message looping was created and how to avoid it. I'm happy to provide any further information.
    Thanks
    Nauman.

    Hello,
    Why do you want to use the 'internal relay domain' authentication?
    Thanks,
    Simon Wu
    TechNet Community Support

  • Error: Not able send mail from OWA 2010. When I send mail, the mails go to Drafts Folder.

    Error: Not able to send mail from OWA 2010. When I send mail, the mails go to Drafts Folder. I have installed everything correctly but when I tried to open the OWA and trying to send mail from OWA. The mails do not deliver and mails become saved in Drafts folder. I tried to re-send messaged from Draft also but not able to send. 
    Screen Shot: http://cid-31ba948d0da4d57e.skydrive.live.com/self.aspx/.Public/Error%20-%20Not%20Able%20to%20Send%20Mail%20from%20OWA%202010.docx
    Scenario: I have below configuration of exchange 2010 server Setup:
    1. Windows Domain Controller with Global Catalog on Windows Server 2008 which only for Windows 2008 Server Native.
    Server Name: WDC2010
    Domain: Blazex.Com
    2. Hub/Client Access Server: It is installed on Windows Server 2008. As per Microsoft recommendation, I have just installed Windows Server 2008 and then join this computer to Blazex.com.
    After that installed the Hub/Client Access Exchange role servers.
    Server Name: HC2010.blazex.com (This is not a Addition Member server or ADC)
    Role: Hub and Client Access Server.
    3. Mailbox Server: It is installed on Windows Server 2008. As per Microsoft recommendation, I have just installed Windows Server 2008 and then join this computer to Blazex.com.
    After that installed the Mailbox Exchange role servers.
    Server Name: MBX2010.blazex.com (This is not a Addition Member server or ADC)
    Role: Mailbox Server.
    4. 2nd  Mailbox Server: It is installed on Windows Server 2008. As per Microsoft recommendation, I have just installed Windows Server 2008 and then join this computer to Blazex.com.
    After that installed the Mailbox Exchange role servers.
    Server Name: 2MBX2010.blazex.com (This is not a Addition Member server or ADC)
    Role: Mailbox Server.
    5. Client Windows 7: It is installed on Windows 7 Ultimate Workstation. As per Microsoft recommendation, I have just installed Windows 7 and then join this computer to Blazex.com.
    Workstation Name: WIN7.blazex.com
    Role: Workstation
    Error Description: I have installed everything correctly but when I tried to open the OWA and trying to send mail from OWA. The mails do not deliver and mails become saved in Drafts folder. I tried to re-send messaged from Draft also but not able to send. 
    Screen Shot (Same As Above): http://cid-31ba948d0da4d57e.skydrive.live.com/self.aspx/.Public/Error%20-%20Not%20Able%20to%20Send%20Mail%20from%20OWA%202010.docx
    I don't know what I am missing but I think there is some configuration I need to do on Hub/Client Access Server (HC2010).  I tried to access the mailbox on XP Client system through OWA. I get the same problem as Win7.
    Can someone please help me on this?
    Thanks and Regards
    Shambhu

    Hi Subhash,
    I have done the troubleshooting but I didn't find any problem at server side. I will send you mail also with all EXBPA report and as well DC, HC and Mailbox servers' Application Log and System Log.
    Below are the questions's answers which was asked by you:
    1.     Please check whether you can send email via Outlook.
    I am not able to open the MS Outlook. Please check all details in this thread : http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/c491c5c7-7d6f-48ff-97fa-6bf83d94e53c
    2.     Please run EXBPA to have a health scan.
    I have run the EXBPA and didn't see any critical Problem. I have took the screen shot and report. Please have a look in below screen shot link:
    a. http://cid-31ba948d0da4d57e.skydrive.live.com/self.aspx/.Public/EXBPA.docx                                                                            - Final Report
    b. http://cid-31ba948d0da4d57e.skydrive.live.com/self.aspx/.Public/ExBPA.BaseLine.200906270226501077.data.xml                        - Baseline Health Check
    c. http://cid-31ba948d0da4d57e.skydrive.live.com/self.aspx/.Public/ExBPA.Connectivity%20Test.200906270223318201.data.xml      - Connectivity Check
    d. http://cid-31ba948d0da4d57e.skydrive.live.com/self.aspx/.Public/ExBPA.Health%20Check.200906270125477730.data.xml            - Health Check with 2 Hr. Baseline option
    e. http://cid-31ba948d0da4d57e.skydrive.live.com/self.aspx/.Public/ExBPA.Permission%20Check.200906270224343377.data.xml      - Permission Report
    The error which I received in EXBPA, that allready ignored by you and told that it is bug in EXBPA. Have a look here: http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/d4bb03bb-db84-4a8b-83ba-19937d7dcacf
    3.     Please check application log, whether any error event logged there. They could come from ADAccess related error or etc.
    I didn't see any ADAccess event on the server. For this I have left my lab PC open and I will check again.
    4.     We find that if mail .que gets corrupt, then this issue will occur, please try to move the affected user to another store and then test the issue.
    I am facing this problem with all users (7 users). Anyway I moved one user from one server Mailbox Database (2mbx2010) to Other Server Mailbox Database (mbx2010). After that
    a) Rebooted the Workstation
    b) Login successfully with same user.
    c) Delete the Old MS Outlook Profile
    d) Create New profile for same user without any problem.
    e) Tried to login in MS Outlook and got the same error. : http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/c491c5c7-7d6f-48ff-97fa-6bf83d94e53c
    f) Open the OWA successfully for Same user.
    g) Tried to send mail but again mail went to Drafts Folder.
    5.     I noticed that you test the issue after you close outlook. I recommend you to reboot your pc and then access
    mailbox via OWA to test the issue.
    I tried you suggested option, but sorry it also couldn't help.
    6.  You also check your disk space.
         All Servers have Enough Disk Space. Check the EXBPA Report.
    7. You may run EXTRA to get log information for further troubleshooting.
      Need more time for this.
    8. Please save application log, system log as *.evt file, then send them with EXTRA,EXBPA report to [email protected] .
       I have sent it as your mentioned mail address OR, you can get the mentioned log from below link also:
       a) http://cid-31ba948d0da4d57e.skydrive.live.com/self.aspx/.Public/WDC2010%7C_APPLICATION.evtx           - DC/GC Application Log
       b) http://cid-31ba948d0da4d57e.skydrive.live.com/self.aspx/.Public/WDC2010%7C_SYSTEMEVENT.evtx          - DC/GC System Log
       c) http://cid-31ba948d0da4d57e.skydrive.live.com/self.aspx/.Public/HC2010%7C_APPLICATION.evtx              - Hub/Client Application Log
       d) http://cid-31ba948d0da4d57e.skydrive.live.com/self.aspx/.Public/HC2010%7C_SYSTEM.evtx                      - Hub/Client System Log
       e) http://cid-31ba948d0da4d57e.skydrive.live.com/self.aspx/.Public/MBX2010%7C_Application.evtx                - Mailbox Application Log
       f) http://cid-31ba948d0da4d57e.skydrive.live.com/self.aspx/.Public/MBX2010%7C_System.evtx                      - Mailbox System Log
    There will be some error log you will be that the system is not able to communicate with DC/DC, MBX or HC at everyday around 3 AM or some time 6 PM Evening also. These error came because I have installed VM on Windows 7 Workstation and after 45 min or one hrs. if I don't work on PC, then pc goes to sleep. so you may ignore these alerts.
    I hope my answer will give you some clue and I expect more help from your side.
    With Best Regards
    Shambhu Sharma

  • OST corrupt when moving Mailbox from Exchange 2010 to Exchange 2010

    Anyone come across this?
    Moving a mailbox on Exchange 2010 to Exchange 2013 - the outlook client wont connect, if you remove the OST and allow outlook to recreate it comes good again.
    outlook client knows the mailbox has moved as it connects to the new server
    Not happening to every mailbox
    thak=nks

    Hi,
    After you move mailbox from Exchange 2010 to Exchange 2013, Outlook should still work.
    Is there any error message when these affected users try to connect? If there is, please post here for further analysis.
    I saw someone failed to connect to the new Exchange server after they moved mailbox, then they restarted the Microsoft Exchange Information Store service and restarted Outlook, it worked.
    If you haven't tried this, you can restart the Microsoft Exchange Information Store service to check the result.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Mirgrating to Exchagne Server 2013 from Exchange 2010

    Hi Team,
    I am in the phase of migrating to Ex 2013 server from Ex 2010 SP3. I've few queries:
    Can I use existing Ex2010 DAG to add Ex2013 Servers?
    If no, then creating a new DAG means I need everything new, such as, storage, network... right?
    Can I use 2010 witness in 2013 DAG and other way around?
    What coexistence means if a new DAG is created.
    and kindly sahre some reading resources about this topic.
    Really appreciete your help.
    Thanks.
    Muhammad Nadeem Ahmed Sr System Support Engineer Premier Systems (Pvt) Ltd T. +9221-2429051 Ext-226 F. +9221-2428777 M. +92300-8262627 Web. www.premier.com.pk

    Hi,
    As DareDevil suggested, you need to setup everything on the new Exchange 2013 servers. After finishing the configuration on Exchange 2013, start to do the migration.
    What's more, I would like to clarify the following thing:
    When migrating a DAG from Exchange 2010 to Exchange 2013, you should first remove the mailbox server from the DAG in Exchange 2010 and then move mailboxes from database in this mailbox server to Exchange 2013. After all mailboxes have been migrated to the
    Exchange 2013 mailbox server, when the new server is ready, it can become a member of the Exchange 2013 DAG.
    For more information, here is a blog for your reference:
    Migrating an Exchange 2010 DAG to Exchange 2013
    http://windowsitpro.com/blog/migrating-exchange-2010-dag-exchange-2013
    Note: Microsoft is providing this information as a convenience to you. The site is not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any information found there. Please make sure that
    you completely understand the risk before retrieving any suggestions from the above link.
    Hope it helps.
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Amy Wang
    TechNet Community Support

  • Cannot send email from Exchange 2007 to Exchange 2013

    Hello Anyone,
    Anyone can help? I've prepare MS Exchange 2013 already, for Migration MS Exchange 2007 and I got the issue.
    My issue is I can't send email from Exchange 2007 to Exchagen 2013, but for Exchange 2013 can send email to Exchange 2007,
    is my issue only internal email for external email both Exchange server is working fine.
    Regards,
    Eakkasak

    Thanks for your reply, when I send email from Exchange 2007 to Exchange 2013 I'm get the error message below.
    Delivery is delayed to these recipients or distribution lists:
    Eakkasak Buajan
    Subject:
    This message has not yet been delivered. Microsoft Exchange will continue to try delivering the message on your behalf.
    Delivery of this message will be attempted until 8/29/2014 8:30:29 PM (GMT+07:00) Bangkok, Hanoi, Jakarta. Microsoft Exchange will notify you if the message can't be delivered by that time."
    I'm already tick  "Exchange server Authentication" in the Default Receive connector properties of Exchange 2013"
    I'm restart services and restart all Exchange Server but doesn't work.
    Thanks,
    Eakkasak
    Sent by Microsoft Exchange Server 2007

  • Exchange 2013 - can no longer move mailboxes from Exchange 2010 to Ex 2013.

    Migrating to Exchange 2013 from Exchange 2010. Created Ex 2013, moved some mailboxes OK. Then could no longer move mailboxes. No errors. The Migration email says complete. Synced: none, Total Mailboxes: none.
    Tried several mailboxes. Same result.
    Ex 2010 is SP3 RU6, (at least it says RU6 is installed in Programs/Features. The build is for SP3 w/o RU6???)
    Ex 2013 is SP1 aka CU4.
    How to proceed???
    john11

    After many attempts to fix the issue (move remaining 4 mailboxes from Exchange 2010 to Exchange 2013) I contacted Microsoft and we resolved the issue. Here's how.
    btw - Thanks for the suggestions from Ed. However, they did not seem to move us forward.
    What did work:
    1. On the Exchange 2010 box, create a new database. (Someone else suggested this also). Then move the remaining Exchange 2010 mailboxes to this new db. Then after that, move the 4 mailboxes to Exchange 2013 using the GUI on Ex 2013. This only worked for one
    of the four mailboxes. The other 3 failed.
    2. Apparently, we need to restart the Microsoft Exchange Mailbox Replication service on the Exchange 2013 after several failed move attempts to clear cache related to the moves.
    3. Then on the Exchange 2013 box, use this Exchange shell command:
    New-MoveRequest -identity "[email protected]" -TargetDatabase "Exchange 2013 DB name" -BadItemLimit '500' -verbose
    This moved the remaining 3 mailboxes including the Discovery mailbox. It took some time. But we could check the progress using
    Get-MoveRequest
    The MS Tech was terrific. Really knew his stuff. And all mailboxes are on Exchange 2013. Well, the last one is still moving, but I am optimistic.
    Thanks for the suggestions. I had to get this done and the MS Tech made that happen. 
    john11

  • Configure send connector for exchange online protection

    Hello Forum members,
    I am trying to configure send and receive connectors for Exchange 2010 to route
    on-premises mailboxes to Exchange OnLine Protection.  The "help" info MS provides
    is for Ex 2013 - and the EAC GUI and config does not lend a close fit to using the 2010
    Exch Management Console.  How can I configure connectors to properly connect to the Exchange Online Protection?
    I have seen where the ip addresses are posted, etc.  I am unclear how to configure the properties on the SBS 2011/EX 2010 server.
    Any tips will help,
    Thanks,
    Eric H.
    Network and Server Installs

    Hello Wesleyhe,
    You cannot use AD anything with EOP - if you mean exchange on-line protection.
    you have to set a smart host on the SBS server to connect to EOP, you may need to add the EOP server ips to your network config
    on the SBS server.  the smart host line (for the send connector on SBS server) is something like: yourdomainname-com.mail.protection.outlook.com.
    Then you need to configure the outside ip for your SBS server access in the EOP admin area.
    Hope this helps.
    eholz
    Network and Server Installs

  • Manually Move Public Folders from Exchange 2010 to 2013

    Hi all,
    I have a issue to finishing my migration from Exchange 2010 to Exchange 2013, I have been trying to migrate my Public folders but always after a couple hours, the migration state is failed.
    The final error is the following:
    FailureCode                      : -2146233088
    FailureType                      : SourceMailboxAlreadyBeingMovedPermanentException
    FailureSide                      :
    Message                          : Error: Couldn't switch the mailbox into Sync Source mode.
                                       This could be because of one of the following reasons:
                                         Another administrator is currently moving
    the mailbox.
                                         The mailbox is locked.
                                         The Microsoft Exchange Mailbox Replication
    service (MRS) doesn't have the correct
                                       permissions.
                                         Network errors are preventing MRS from cleanly
    closing its session with the
                                       Mailbox server. If this is the case, MRS may continue
    to encounter this error for
                                       up to 2 hours - this duration is controlled by the TCP
    KeepAlive settings on the
                                       Mailbox server.
                                       Wait for the mailbox to be released before attempting
    to move this mailbox again.
    So, after seeing this I started to monitoring all process and I realized that after creating hierarchy the process start to fail and keep in StalledDueMailboxlock status, and the error is:
    FailureCode                      :
    FailureType                      :
    FailureSide                      :
    Message                          : Informational: The request has been temporarily postponed because the mailbox is
                                       locked. The Microsoft Exchange Mailbox Replication service
    will attempt to continue
                                       processing the request after 2/14/2015 12:38:20 PM.
    Finally, digging more into reports of migration I  found this:
    MapiExceptionNetworkError: MapiExceptionNetworkError: Unable to open entry ID. (hr=0x80040115, ec=6)_x000A_Diagnostic context:_x000A_ Lid: 40487 EMSMDBMT.EcDoRpcExt2 called [length=73]_x000A_ Lid: 44583 EMSMDBMT.EcDoRpcExt2
    exception [rpc_status=0x6][latency=0]_x000A_ Lid: 62184 _x000A_ Lid: 16280 dwParam: 0x0 Msg: EEInfo: ComputerName: n/a_x000A_ Lid: 8600 dwParam: 0x0 Msg: EEInfo: ProcessID: 51452_x000A_ Lid: 12696 dwParam: 0x0 Msg: EEInfo: Generation Time: 0415-02-14T14:25:40.9210000Z_x000A_
    Lid: 10648 dwParam: 0x0 Msg: EEInfo: Generating component: 2_x000A_ Lid: 14744 dwParam: 0x0 Msg: EEInfo: Status: 6_x000A_ Lid: 9624 dwParam: 0x0 Msg: EEInfo: Detection location: 1741_x000A_ Lid: 13720 dwParam: 0x0 Msg: EEInfo: Flags: 0_x000A_ Lid: 11672 dwParam:
    0x0 Msg: EEInfo: NumberOfParameters: 0_x000A_ Lid: 23260 Win32Error: 0x6_x000A_ Lid: 61553 StoreEc: 0x80040115_x000A_ Lid: 52176 ClientVersion: 15.0.1044.25_x000A_ Lid: 50032 ServerVersion: 14.3.181.6_x000A_ Lid: 50128 _x000A_ Lid: 50288 _x000A_ Lid: 23354
    StoreEc: 0x80040115_x000A_ Lid: 25913 _x000A_ Lid: 21817 ROP Failure: 0x80040115_x000A_ Lid: 22894 _x000A_ Lid: 24942 StoreEc: 0x80040115
    So, would like to know if exist any procedure to migrate/move my Public Folders from Exchange 2010 to 2013 manually, something like Export/Import.
    Regards!

    What script and process you are running to migrate the Public Folders?
    And what do you mean by Manually?
    Cheers,
    Gulab Prasad
    Technology Consultant
    Blog:
    http://www.exchangeranger.comTwitter:
    LinkedIn:
    Check out CodeTwo’s tools for Exchange admins
    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.

  • Forcefully delete user's "Deleted Items" from Exchange 2010 Management shell ?

    After migration from Exchange 2003 to 2010 my organization's some user can't delete items from their deleted items folder, it generate a error message so how can I forcefully delete user's deleted items from their "Deleted Items folder" from
    Exchange 2010 Management shell ? Thanks
    Babu

    Hi Babu ,
    Based on my knowledge i have given some suggestions please have a look in to it.
    1.We cannot use the search-mailbox command specifically for any folder in the mailbox.But we can use it for a whole mailbox.Below is the command which will copy the entire contents of the mailbox to the target folder called as "backup" .
    Search-Mailbox -Identity "problematic mailbox name" -TargetMailbox "test mailbox" -TargetFolder "backup" -LogLevel Full -deletecontent
    Note : Before executing the above command , please execute the below.
    New-ManagementRoleAssignment -Name "Import Export_Enterprise Support" -SecurityGroup "Enterprise Support" -Role "Mailbox Import Export"
    Once the above command is executed then you need to add your admin account to the security group "Enterprise Support" and then use the Search-Mailbox command to copy the entire items to the target mailbox and also it will delete all the copied
    items from the original mailbox.
    2.Another one option is to use the MFCMAPI tool to force delete the items on the deleted items folder.
    Most importantly before doing all the above , please share me the error message what your users are facing while deleting the items from deleted items folder.
    Thanks & Regards S.Nithyanandham

Maybe you are looking for