Copy emails (entire mailbox) to another exchange server 2013

Hi,
We are a hosted Exchange server 2013 solution provider, and we want to migrate customer mailboxes (from exchange 2007, 2010) to Exchange 2013 using some API, as we have a web portal for other admin tasks too. Someone told us that we can use EWS Managed API
for this purpose.
Is there any article  in this regard, which can help us?
Or, is there any other API which we can use?
Thanks in anticipation.
Regards, David Johnson

Hi,
Glen thanks a lot for your reply. You are always a great help.
We are currently exporting\importing using powershell manually, but there are some difficulties in automating it using a web based app, as we don't want our customers to do any manual changes, while also, from our server, we cannot execute powershell commands
on remote Exchange 2007 servers.
Automating Cross forest migration is also very diificult, as you know that it has many steps, which are hard to automate, and also there is no api for MRS, as we know.
We have seen some migration utilities doing migration using EWS API, like CodeTwo, and also Transend
Migrator. Can you please tell, if you know, how they are doing it.
Thanks.
Regards, David Johnson

Similar Messages

  • Internal NAV2013 to relay email externaly through our internal exchange server 2013

    ello,
    We are using NAV 2013 to externally relay email outside and inside through our in house Exchange server 2013.
    I created a new Frontend connected with "TYPE" Custom and selected specific ip to configure relay through exchange server.
    Once created the Receive connectors I want only Anonymous permission to be set under permission group and not exchange users as this is allowing external 3rd party exchange server to relay emails through our exchange server.
    When i edit the properties of the exchange server to uncheck Exchange Server it gives me an error
    "You must set the value for the PermissionGroups parameter to ExchangeServers when you set the AuthMechanism parameter to a value of ExternalAuthoritative."
    My motive is that I want to allow only the NAV2013 to relay emails through our exchange and no other exchange server or any other application for security reasons.
    Once i created a Receive Connectors bydefault TLS is selected and then i put a tick mark on Anonymous but as soon as i save i get error "You must set the value for the PermissionGroups parameter to ExchangeServers when you set the AuthMechanism parameter
    to a value of ExternalAuthoritative." and it doesn't let me save unless i select Exchange Server
    I have followed the same link that you provided me.
    There is another problem as well, I have restricted a distribution group from receiving email from external to the organisation but as soon as i created this relay connectors this group starts receiving email external to the organisation which is very strange.
    I tested by disabling the relay connector and then sending email from gmail and then i get a bounce in gmail and the DG doesn't receive email but as soon as I enable relay connector the distribution group starts receiving email.
    I have also recreated the connector as well but still the same issue.
    Please help

    Hi,
    Please double check whether the "You must set the value for the PermissionGroups parameter to ExchangeServers when you set the AuthMechanism parameter to a value of ExternalAuthoritative" is an error, we can safely ignore it if it
    is only a warning message. 
    I found a related KB for your reference even if the Exchange server version is mismatched.
    Exchange 2010: Get-ReceiveConnector warns that an Exchange 2007 connector is corrupted and in an inconsistent state
    http://support.microsoft.com/kb/2291884
    Please double confirm the following setting:
    Authentication tab: Checked TLS and Externally Secured.
    Permission Groups: Anonymous users, Exchange Servers
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • Blocking Spam Emails by subject name in Exchange Server 2013

    Hello Guys,
    I need to know how to block spams by subject from Exchange Server 2013's Anti-spam/message filter.
    In general, I'm using Exchange's anti-spam agents and configured spam blocking by domain name.. but I need to filter unnecessary emails by subject name also.
    So, if you know how to resolve this issue, please post here the real solution..
    Thanks a lot,

    Hi GMG,
    Thank you for your question.
    We could install Exchange 2013 edge server, then we could create item which block spam base on subject name in “Protection”, we could refer to the following link:
    https://technet.microsoft.com/en-us/library/bb124701%28v=exchg.150%29.aspx
    There is a another method, we could use transport rule to filter spam by subject name by the following link:
    https://technet.microsoft.com/en-us/library/dd351127(v=exchg.150).aspx
    If there are any questions regarding this issue, please be free to let me know. 
    Best Regard,
    Jim
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Jim Xu
    TechNet Community Support

  • How can i get newly added contacts for a Mailbox User in Exchange Server 2013

    Hi all,
    I need to synchronize contacts in Exchange Server and Sugar CRM Application, for that
    i need to get newly added contacts for a User in Exchange Server 2013 by using EWS Managed API.
    I know how get the list of all contacts for a particular user , but in the list how i can find
    new contacts ?

    Hi Dora,
    that's the fun thing:
    You add your own property (and it'll be invisible to outlook users, not to worry).
    Extended Properties allow you to define custom property on Exchange Items. And it has a
    method for setting those too.
    Here's a short post doing a very simple intro on using Extended Properties.
    Glen's Exchange Blog is a generally useful resource when working with EWS, I'm confident you'll be able to find lots of tips there as well.
    Cheers,
    Fred
    There's no place like 127.0.0.1

  • Recover mailbox from Exchange server 2010 information store to exchange server 2013

    I have a big issue. I have a correct exchange server 2010 where the active directory is corrupt but the information store is good.
    I would like to recover a couple of mailboxes to an exchange server 2013.
    Can anyone give me a detailed walk through of how I can accomplish this?
    Thank in advance

    Well if your AD is messed up that leaves you in a jam for sure because;
    1. Database portability ONLY works within the same organization, so you cannot just install a new 2010 server in a completely different forest and then move the DB in hopes that DB portability will work.
    2. As Ed said you should build a new Exchange 2010 server and use portability but it has to be in the same organization.
    3. Here is a good article on how to accomplish
    http://exchangeserverpro.com/exchange-2010-database-portability-disaster-recovery/
    4. Now if you by chance have an AD backup before it went south you could build a separate network with same names etc just keep it isolated from the production server and then restore AD to that environment and you could then use DB portability.
    That said if you don't have any other machines to work with then you are in a bit of a pickle and will have to use a 3rd party product to get to that data within the 2010 DB.   We make a product that can do this (DigiScope), however if you don't
    have any budget to handle its a non-issue.
    The only other thing you could consider is to restore your AD from a previous point in time, however BE VERY CAREFUL if you consider this since it could cause more issues then you have now.
    BTW if you AD is messed up, where are you putting this new 2013 server?
    Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 -->
    2007 --> 2010 --> 2013 with Lucid8's
    DigiScope

  • Exchange Server 2013 Mailbox - High CPU Usage

    Hi,
    We are having an issue with our Exchange 2013 Mailbox Server.
    The process Microsoft.Exchange.Store.Worker consumes most of the CPU utilization.
    Have anyone encountered this issue? How were you able to resolve it?
    Thanks

    Hi,
    According to your description, your database is not active. And to understand more about the issue, I’d like to confirm if there is some user experience slow connection or other performance issue.
     However, since in Exchange 2013 single Store Worker Process is only responsible for one database, we can firstly confirm if the specific mailbox database causes the high CPU:
    http://msexchangeteam.in/how-to-identify-which-microsoft-exchange-store-worker-process-is-owned-by-mailbox-database-in-exchange-server-2013/
    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.
    If you have any question, please feel free to let me know.
    Thanks,
    Angela Shi
    TechNet Community Support

  • Exchange Server 2013 and RADIUS server(freeRADIUS2)

    I am a student and doing an internship. I have to test Microsoft Exchange Server 2013.
    I am using Windows Server 2012, I already installed Exchange
    Server 2013 on it and everything works as intended.
    But I couldn't find out how to configure my Windows Server 2012 in order to authenticate my mailbox users from Exchange Server 2013 with a RADIUS
    server which is not on my Windows Server 2012. I have to use their RADIUS server ( freeRADIUS2 ), the RADIUS server from
    the company where I am doing my internship.
    I already did the checklist that is on http://technet.microsoft.com/en-us/library/cc772591.aspx. I configured the NPS as
    a RADIUS proxy, because that's what I need.
    So after doing everything that is on that checklist, my question is:
    Is it possible that the Exchange Server 2013 will use my NPS which is now configured as a NPS RADIUS proxy to authenticate my mailbox users that I have on my Exchange Server 2013?

    thanks for such a quick response.
    Just a small question about the link that you put. Does member server mean other server other than domain controller?
    Regards,
    Yes, Also the server on which you are installing Exchange should have exchange installed.
    Cheers,
    Gulab Prasad
    Technology Consultant
    Blog:
    http://www.exchangeranger.com    Twitter:
      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.

  • Exchange Server 2013 with RADIUS authentication

    Hello,
    I am a student and doing an internship. I have to test Microsoft Exchange Server 2013.
    I am using Windows Server 2012, I already installed Exchange Server 2013 on it and everything works as intended.
    But I couldn't find out how to configure my Windows Server 2012 in order to authenticate my mailbox users from Exchange Server 2013 with a RADIUS server which is not on my Windows Server 2012. I have to use their RADIUS server, the RADIUS server from the
    company where I am doing my internship.
    I already created a NPS and added the RADIUS Client + Remote RADIUS Server Groups. I created a Connection Request Policies with the condition:
    User Name *
    I forwarded the Connection Request to the Remote RADIUS server that I created in Remote RADIUS Server Groups and then I registered the NPS in th AD. But it's still not working. 
    Maybe I did something wrong or I misunderstood something or does this even work with Exchange Server 2013? To authenticate mailbox users with a RADIUS server before they can login into their mailbox and use their mailbox?
    Thanks in advance.

    On Wed, 26 Mar 2014 09:21:25 +0000, DavidIntern wrote:
    I already put the NPS as a RADIUS proxy. I followed this check list http://technet.microsoft.com/en-us/library/cc772591.aspx
    But the things is I want to make it work with our freeRADIUS2 that we have in place here. Without changing our freeRADIUS2. But I found out this is not possible since we are not using any Active Directory with it. Since I am still a newbie in this environment,
    I am not sure if it is possible.
    But my main question was if it was possible to use freeRADIUS2 and that my NPS would be the RADIUS proxy. So my question is answered, if I understood right, without making any changes to our freeRADIUS2 this is not going to be possible right? Because we have
    no AD?
    Our setup is freeRADIUS2 + MySQL database where all the users are stored.
    As I mentioned in my previous response this really isn't the right place
    for this question but why would you want to try to use a MySQL store for
    authenticating against Exchange in the first place when you've already got
    an authentication store (Active Directory) that is tightly integrated with
    Exchange?
    I still really don't understand what it is you're trying to accomplish nor
    why you're trying to use such a complicated, convoluted method to
    authenticate Exchange users.
    Paul Adare - FIM CM MVP
    Any sufficiently advanced bug is indistinguishable from a feature.

  • Exchange Server 2013 with a RADIUS server (freeRADIUS).

    Hello,
    I am a student and doing an internship. I have to test Microsoft Exchange Server 2013.
    I am using Windows Server 2012, I already installed Exchange Server 2013 on it and everything works as intended.
    But I couldn't find out how to configure my Windows Server 2012 in order to authenticate my mailbox users from Exchange Server 2013 with a RADIUS server which is not on my Windows Server 2012. I have to use their RADIUS server (freeRADIUS), the RADIUS server
    from the company where I am doing my internship.
    I already created a NPS and added the RADIUS Client + Remote
    RADIUS Server Groups. I created a Connection Request Policies with the condition:
    User Name *
    I forwarded the Connection Request to the
    Remote RADIUS server that I created in Remote RADIUS Server Groups and then I registered the NPS in th AD. But it's still not working. 
    Maybe I did something wrong or I misunderstood something or does this even work with Exchange Server 2013? To authenticate mailbox users with a RADIUS server before they can login into their mailbox and use their mailbox?
    Thanks in advance.

    Hi,
    I suggest we refer to the following article to double confirm the Network Policy Server is registered properly.
    http://technet.microsoft.com/library/cc732912.aspx
    Thanks,
    Simon Wu
    TechNet Community Support

  • Moving the mailbox database copy from one exchange server to another exchange server 2010 DAG

    Hello Team
    is it possible to the move the passive copy of database and logs from one server to another exchange server in the same DAG with out removing  and deleting the mailbox database copies in exchange 2010
    normaly procedure is
    Remove the mailbox database copies and manually delete the .edb files and logs from the physical location and re-add the mailbox database copy to the new server in the DAG.
    is that any way to achieve to move the passive database copy to another exchange 2010 server in the same DAG ?

    From your note, you appear to have a two-member DAG (with a server hosting your active database, and a second hosting the passive copy), and you want to move your passive database copy from the current passive server to another.  Your note
    about what "the normal procedure is" isn't 100% correct - there are many ways to handle this task, and all can be considered "normal". Why not just add the third server to the DAG and
    add a database copy on that third server?  Once it is fully seeded, you can remove the current passive copy.  This way, you never lose your redundancy.
    Yes i can add the third and fourth  serve in DAG , but i cannot add the mailbox database copies to the 3rd and 4th mailbox server in DAG as am using RTM version of exchange 2010 which is allowing to have only 5 database inclding mailbox datbase copies
    and also currently my lab setup is  two member dag (with a server hosting your active database,
    and a second hosting the passive copy) in the same site named SITE A
    and recently i have created new SITE B and included the 3rd and 4th DAG members in the same DAG
    i want the  mailbox database copies from the mailbox server  database  in SITE A  to
    Mailbox server database in  SITE B as  passive copy
    That is why i want to move the mailbox database without deleting / removing it manually
    Hope you understand my situation!

  • Help with Moving Emails from Exchange Server 2013

    Hi Team,
    Help, I need a solution on how to copy incoming and outgoing emails together with their attachments and was hoping someone could help with a solution I need to find for this problem.
    1) I have a need to copy all incoming and outgoing emails & attachments from Exchange Server 2013 mailboxes on a daily basis, so they can be archived into an external 3rd party database overnight.
    I believe that the first step is that I can set up another Exchange mailbox, through Journaling to receive these emails. 
    Is there any way that these emails can then be moved direct from the Journaling mailbox that I have created, to a shared folder on the network? If so what format would they be sent out as e.g. .msg, .ems and what is the process?
    Failing that, could they be sent to an Outlook client (not another Exchange mailbox) on the network and stored in a .pst file? (I have a program that will export them from .pst)
    I would really appreciate any assistance that you can provide in this matter.
    Regards, Greg.

    Hi,
    You can set auto-forward on journaling mailbox and auto-forward emails to another mailbox. Why don’t directly archive the emails from the journaling mailbox “an external
    3rd party database”.
    Thanks,
    Simon Wu
    TechNet Community Support

  • Best way for Email Notifications in EWS Managed API 2.0 [ Exchange Server 2013]

    Hi ,
    I want to know best way for Email Notifications in Exchange server. My
    organisation has 
    10 users, i want to get notification if any user mailbox got any new mail.
    i need to create API,
    that was consumed by another Team in their Application.
    I am using Exchange server 2013.
    Please share Your Ideas.
    Thank you

    Take a look at EWS Notifications
    http://msdn.microsoft.com/en-us/library/office/dn458791(v=exchg.150).aspx .
    Cheers
    Glen

  • Exchange Server 2013 - Lab setup with internal emails only

    Hi,
    I'm new to Exchange Server 2013. I've started a POC on the product by setting up a Lab environment with one 1 AD server and 1 Exchange server (Both Windows 2012 R2). As this is a POC I just need the internal email communication. I don't want the mails to
    go over the internet. 
    I've completed the installation part and just started to configure Send/Receive connectors and got stuck with the question whether the connectors are required or not.
    Could someone please help me out in configuring internal email setup for Exchange 2013 lab setup.
    Regards,
    Nithin

    Hi,
    You need not to configure send/receive connectors for internal email.
    The following article for your reference:
    http://technet.microsoft.com/en-us//library/aa996395(v=exchg.150).aspx
    Default Receive connectors created during setup
    Certain Receive connectors are created by default when you install the Mailbox server role.
    Default Receive connectors created on a Mailbox server running the Transport service
    When you install a Mailbox server running the Transport service, two Receive connectors are created. No additional Receive connectors are needed for typical operation, and in most cases the default Receive connectors don't require a configuration change.
    These connectors are the following:
    Default <server name>   Accepts connections from Mailbox servers running the Transport service and from Edge servers.
    Client Proxy <server name>   Accepts connections from front-end servers. Typically, messages are sent to a front-end server over SMTP.
    Each connector is assigned a TransportRole value. You can use it to determine the role the connector is running in. This can be helpful in cases where you are running multiple roles on a single server. In the case of each Receive connector previously
    mentioned, their TransportRole value is HubTransport.
    To view the default Receive connectors and their parameter values, you can use the
    Get-ReceiveConnector cmdlet.
    Default Receive connectors created on a Front End Transport server
    During installation, three Receive connectors are created on the Front End transport, or Client Access server. The default Front End Receive connector is configured to accept SMTP communications from all IP address ranges. Additionally, there is a Receive
    connector that can act as an outbound proxy for messages sent to the front-end server from Mailbox servers. Finally, there is a secure Receive connector configured to accept messages encrypted with Transport Layer Security (TLS). These connectors are the following:
    Default FrontEnd <server name>   Accepts connections from SMTP senders over port 25. This is the common messaging entry point into your organization.
    Outbound Proxy Frontend <server name>   Accepts messages from a Send Connector on a back-end server, with front-end proxy enabled.
    Client Frontend <server name>   Accepts secure connections, with Transport Layer Security (TLS) applied.
    In a typical installation, no additional Receive connectors are required.
    Niko Cheng
    TechNet Community Support

  • Exchange Server 2013: incoming messages are not delivered into user mailboxes occasionally

    Exchange Server 2013 CU1, two mailbox servers (DAG, only one mail database), two CAS servers (NLB cluster). Two Sendmail/CentOS-based SMTP relays route mail between Exchange servers and Internet (incoming mail is routed to NLB cluster name).
    Usually mail flow is OK: messages are sent and received normally. However, I've got several complains from different users. They state that occasionally they don't receive messages that were sent to them from outside. Tomorrow morning I've decided to
    investigate the issue.
    So, we have a message sent from Gmail account that was not delivered in user mailbox. It was received and routed to Exchange by Sendmail host:
    Jun 27 22:06:37 MX01 sendmail[12169]: r5RG6HC8012166: to=<USER_ADDRESS>, delay=00:00:19, xdelay=00:00:19, mailer=smtp, pri=124702, relay=NLB-FQDN [NLB-IP], dsn=2.0.0, stat=Sent (<CAHgK_sjEkj41htuVsutMP3XhgR5RRDs8-EgSC-UfHoaiHWFj=A@mail.gmail.com>
    [InternalId=13069585481819] Queued mail for delivery) 
    Running Get-MessageTrackingLog applet on the mailbox servers displayed the followed log entries for the message:
    DB Server #1:
        22:11:18 HAREDIRECT
        22:11:18 RECEIVE
        22:11:18 AGENTINFO
    DB Server #2:
        22:11:18 HARECEIVE
        22:12:44 HADISCARD
    So, we can see that the message was placed into shadow queues, but was NOT delivered into mailbox (no DELIVER status entries). Also pay attention to the timing. Time on all the servers is in sync, but Sendmail timestamp is 22:06, and Exchange timestamps
    are 5 minutes behind it.
    Today a message sent to the same address from the same Google mailbox was received by Exchange and placed into user mailbox with no glitches.
    We use Exchange antispam system activated on Exchange mailbox servers. Spam is never dropped silently. It is either returned to sender (SCL 9) or placed into quarantine mailbox (SCL 6 and above). I'm pretty sure that the lost message was not in the quarantine
    mailbox this morning, and the sender didn't receive any NDRs.
    Any ideas what to investigate next?

    Hi,
    Do you mean the emails are placed in the Shadow Redundancy queue?
    Shadow Redundancy
    http://technet.microsoft.com/en-us/library/dd351027(v=exchg.150).aspx
    Thanks,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Simon Wu
    TechNet Community Support

  • Exchange Server 2013 SP1 - Internal Email Flow slowness

    Hi Fellows,
    I have a brand new implementation of Exchange Server 2013 SP1 with three mailbox servers and 3 CAS servers.
    I am facing a considerable slow transportation of email internally. although there are just 3 mailboxes on the infrastructure at the moment.
    When a user sends email to himself or other two accounts, delivery takes from 15 seconds to 35 seconds to be delivered.
    Experience is same even if the email is sent from OWA, ActiveSync or Outlook.
    Header analysis shows the message exchange between mailbox servers is taking time. any clue?
    Decreasing Tarpit interval on Mailbox server receive connectors will be helpful?
    Network communication, Storage performance, Server performance are all as good as we love to.
    Thanks.
    J.A

    Hello,
    When a user send message to a internal user in a AD site, the connector will not be used. I recommend you use message tracking to check the issue occur on server side or transport process. Please use queue viewer to check if there is mail traffic.
    Cara Chen
    TechNet Community Support

Maybe you are looking for