Issue moving remote user from exchange 2007 to 2013

have moved over 60 people so far from exchange 2007 to 2013, it was going well with no major problems.
during migration I have created a DNS setting called legacy.mydomain.com, and it points to the old exchange server, while mail.mydomain.com points to the new exchange server.  
outlook was working connecting to both servers, and OWA was working on both servers.
couple of remote users who connect via SSL-VPN and outlook 2010 had issues connecting, but as soon as I moved them to 2013 exchange they connected without vpn using outlook anywhere.
but - I have one remote user who even though the mailbox move to the new 2013 server was successful, their outlook still points to the 2007 exchange server.
if I try creating a new profile in outlook 2013, it fails because it cannot contact exchange server, even when ssl-vpn is running.
when I started troubleshooting I found lots of spyware on his laptop, symantec had been blocking some trojans, obviously he had downloaded something he shouldnt have.
could this have caused my outlook connectivity issue?
I ran malawarebytes, and it shows clean now, but still unable to get his outlook to connect.
I had thought about moving his mailbox back to the old server, seeing if it works on outlook, then moving it to the new one again.
any suggestions?

I had thought about moving his mailbox back to the old server, seeing if it works on outlook, then moving it to the new one again.
Hi,
Have you done this step? Sometimes moving mailbox to another database can auto-fix problems.
According to your description, I know that all migrated mailboxes work well except a specific user. I notice that the user's laptop has a lots of spyware, and symantec has been clocking some trojans.
Please try to logon OWA to check whether this user works.
If works in OWA, it seems that the mailbox has been migrated to 2013 successfully.
Generally, re-creating profile can fix this issue. Unfortunately, you have tried it and failed.
Please try to run Outlook under safe mode to avoid AVs and add-ins.
Thanks
Mavis Huang
TechNet Community Support

Similar Messages

  • Migrating Users from Exchange 2007 to Exchange 2013 Without redirection through exchange 2013.

    We have all our users and mailboxes on Exchange 2007 and I have introduced two Exchange 2013 servers in my organization and both have mailbox and CAS server installed on them. 
    With Exchange 2007 server, I had not modified any of the internal and external url/uri and had stayed with the defaults.
    For migration most of the documents are suggesting of changing the default internal URL and Auto Discover Service internal URI values.
    In my case, I want to migrate all the users and mailbox (everything that is on Exchange 2007) form 2007 to 2013 and decommission exchange 2007 completely from our organization.
    I am in the phase of transferring users from Exchange 2007 to Exchange 2013 and do not want to change any settings on the existing 2007 servers.
    I have created new dns entry mailx.abc.com with two IPs of both exchange 2013 and changed the Outlook Anywhere internal URL on both Exchange 2013 server to mailx.abc.com.
    So by doing these, I think all existing clients will still connect to exchange 2007 and after moving their mailbox they will be connect to exchange 2013.
    In short I am not redirecting or using 2013 as proxy for 2007 clients and clients whose mailbox is on exchange 2013 will directly connect to 2013 server.
    Questions are, Is this the right way to migrate all the users to Exchange 2013?
    Will it affect the operation of existing Exchange 2007 server?

    Read the below blog on Client Connectivity in Exchange co-existence. There can't be better blog than this on this topic.
    http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
    Clients connect to Exchange from Internal-Outlook, External-Outlook, Web & Active Sync.
    For Internal the configuration that you have mentioned should work as clients would get Autodiscover information from Active Directory (SCP) and get connected to right server.
    However, for external connectivity it makes sense to use External URL on Exchange 2013 servers (keep the Exchange exposed to Internet), configure legacy URL for exchange 2007 and use Exchange 2013 external URL for mailboxes that are Exchange 2007 and Exchange
    2013 for standardization.
    Refer article for configuring URLs -
    http://silbers.net/blog/2014/01/22/exchange-20072013-coexistence-urls/
    - Sarvesh Goel - Enterprise Messaging Administrator

  • Migration from Exchange 2007 to 2013 gives error "Failed to communicate with the mailbox database'

    I have been trying to migrate several databases from Exchange 2007 to Exchange 2013. The migration started successfully, and many of the mailboxes moved successfully (about 70). The remaining mailboxes, failed. Looking deeper, we found a few issues; The
    two 2013 Mailbox servers were on different versions. The Server had run out of disk space, and the NIC drivers needed to be updated.
    Now when we try to migrate a mailbox that had failed in the earlier batch, we get the following error:
    Data migrated:                        
    Migration rate:                        
    Error:                        
    MigrationTransientException: Failed to communicate with the mailbox database. --> Failed to communicate with the mailbox database. --> MapiExceptionNetworkError: Unable to make connection to the server. ‎(hr=0x80040115, ec=-2147221227)‎ Diagnostic
    context:    ......    Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 501    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0    Lid: 11672   dwParam:
    0x0 Msg: EEInfo: NumberOfParameters: 4    Lid: 8856    dwParam: 0x0 Msg: EEInfo: prm[0]: Unicode  string: ncacn_ip_tcp    Lid: 8856    dwParam: 0x0 Msg: EEInfo: prm[1]: Unicode  string: <Server
    FQDN>    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[2]: Long val: 3749909585    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[3]: Long val: 382312662    Lid: 45169   StoreEc: 0x824        
    Lid: 50544   ClientVersion: 15.0.847.32    Lid: 52080   StoreEc: 0x824         Lid: 44273      Lid: 49064   dwParam: 0x1    Lid: 37288  
    StoreEc: 0x6AB         Lid: 49064   dwParam: 0x2    Lid: 59431   EMSMDB.EcDoConnectEx called [length=203]    Lid: 51239   EMSMDB.EcDoConnectEx exception [rpc_status=0x6D9][latency=0]   
    Lid: 62184      Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a    Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 3460    Lid: 12696   dwParam: 0x0 Msg: EEInfo:
    Generation Time: 0414-04-07T16:32:03.2100000Z    Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 2    Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 1753    Lid: 9624   
    dwParam: 0x0 Msg: EEInfo: Detection location: 501    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0    Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 4    Lid: 8856   
    dwParam: 0x0 Msg: EEInfo: prm[0]: Unicode  string: ncacn_ip_tcp    Lid: 8856    dwParam: 0x0 Msg: EEInfo: prm[1]: Unicode  string: <Server FQDN>    Lid: 12952   dwParam: 0x0 Msg: EEInfo:
    prm[2]: Long val: 2767313664    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[3]: Long val: 382312662    Lid: 59505   StoreEc: 0x824         Lid: 50544   ClientVersion:
    15.0.847.32    Lid: 52080   StoreEc: 0x824         Lid: 36081      Lid: 51152      Lid: 52465   StoreEc: 0x80040115   
    Lid: 60065      Lid: 33777   StoreEc: 0x80040115    Lid: 59805      Lid: 52487   StoreEc: 0x80040115    Lid: 19778      Lid: 27970  
    StoreEc: 0x80040115    Lid: 17730      Lid: 25922   StoreEc: 0x80040115
    All of the issues listed above have been corrected, and all of the databases are mounted. Users are able to send and receive mail, but I can not migrate mail using the Migration Batch utility.
    The destination server is a Hyper-V Guest running Server 2012, SP1, and Exchange 2013
    The Source Server is Running Exchange 2007.
    I have tried doing a test move to another destination server that is also Server 2012, and Exchange 2013, and the migration also failed.
    I would appreciate any help you can give me!
    Thanks,
    Jon

    Any update if you have resolved the issue.
    Not similar, but this thread can be helpful while you migrate the mailboxes from exchange 2007 to 2013. Please check :http://social.technet.microsoft.com/Forums/exchange/en-US/721f0ae4-623a-4b02-adaf-f561d86c0426/move-mailboxes-and-public-folders-from-exchange-2007-to-exchange-2013?forum=exchangesvrdeploy&prof=required

  • Can only access emails through OWA after migration from exchange 2007 to 2013

    can only access emails through OWA after migration from exchange 2007 to 2013, in other words unable to access mails through outlook or from other Applications services.
    needed RCA ... plz help..

    Hi,
    From your description, you can send and receive messages only when you use OWA after migration from Exchange 2007 to Exchange 2013. If I have misunderstood your concern, please let me know.
    In your case, I recommend you create a new test mailbox in your Exchange 2013 and check if you can send and receive messages on Outlook. If yes, it is recommended to create a new profile to solve this issue.
    Hope this can be helpful to you.
    Best regards,
    Amy Wang
    TechNet Community Support

  • How to migrate from exchange 2007 to 2013 step by step tutorials please

    Hi
    I am running Windows Server 2008 standard, with exchange 2007 SP2 on it.
    We have 800 mailbox in total
    Our domain controllers are
     Win2012 R2 and I would like to upgrade to Exchange 2013 on Windows server 2012 R2.
    I am running a VM, on VMware environment, so my Windows 2012 R2 is a VM.
    Is there a website or document that explains in detail, step by step how to upgrade from 2007 to 2013.
    I currently only have 1 exchange server 2007, with all the roles on the one server.  I would like to keep that same as
    well with exchange 2013.
    Thanks

    Exchange server deployment assistant is always a good service provider to achieve this task as it simply ask few questions about your current environment and proceed further accordingly.
    You can refer to this blog explained by technet team that will assist you further to gather more information in depth : http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
    Moreover, to avoid the interruptions and proceed a hassle-free migration from exchange 2007 to 2013, this application (http://www.exchangemigrationtool.com/) could also be a good approach to accomplish
    migration task in more secure way.

  • Exchange active sync cannot connect to server after migration mailbox user from exchange 2007 to exchange 2013 coexistence

    Hello, everyone, my name is rafl
    I have a problem with exchange 2013 active sync.
    I have installed exchange 2013 coexistence with legacy exchange 2007, I have to migrate user mailboxes: [email protected] from exchange 2007 to exchange 2013.
    but any problem with active sync connection on the mobile device after moving mailbox user. I reconfigure the exchange ActiveSync external connection domain (latest.domain.com) on mobile device replacing legacy exchange ActiveSync external connection domain
    (legacy.domain.com)
    the process of moving mailboxes successfully without error.
    Access OWA for exchange 2007 and exchange 2013 is running normally
    access mail from Outlook running normally
    Certificate request has been installed and has no problem with it
    The OWA virtual directory is configured for internal and external connections and different from the legacy exchange
    The autodiscover virtual directory is configured for internal and external connections and different from the legacy exchange
    ActiveSync virtual directory is configured for internal and external connections and different from the legacy exchange
    user mailboxes are still on exchange 2007 is not problematic.
    only problem with Exchange Active Sync on mobile devices, where I set up an email with android, iphone, windows phone. the error message: cannot connect to the server.
    but, if I create a new user and create user mailboxes directly in exchange server 2013, ActiveSync can run without error on mobile device, access through OWA, MsOutlook, Outlook Anywhere also run normally.
    only the results of user migration from exchange 2007 to exchange 2013 which is troubled with exchange ActiveSync connection.
    any ideas for this problem, and what should I check on the exchange server ..?

    i have run the activesync test connectivity and get some error :
    Testing TCP port 443 on host domain.co.id to ensure it's listening and open.
    The specified port is either blocked, not listening, or not producing the expected response.
    A network error occurred while communicating with the remote host.
    Elapsed Time: 3091 ms.
    Testing TCP port 443 on host autodiscover.domain.co.id to ensure it's listening and open.
    The specified port is either blocked, not listening, or not producing the expected response.
    A network error occurred while communicating with the remote host.
    Elapsed Time: 21072 ms.
    Testing TCP port 80 on host autodiscover.domain.co.id to ensure it's listening and open.
    The specified port is either blocked, not listening, or not producing the expected response.
    A network error occurred while communicating with the remote host.
    Elapsed Time: 21049 ms.
    I have allowed access to port 443 (https) and 80 (http) on the firewall and re-run testconnectivity, but still with the same results. if I enable active sync for users who created directly in Exch 2013 there is no problem with the ActiveSync, just a problem
    for users who moved from Exch 2007 to Exch 2013. @Android, iPhone, and Blackberry the error message "cannot connect to the server"

  • Public Folder Migration from Exchange 2007 to 2013

    Hi Guys,
    I have a general Exchange 07-13 migration question about migrating the PF's and System Folder Information, I read somewhere that the SystemFolder info doesn't come across, can someone shed some light on this for me please?
    Thanks,
    Ray

    Hi Ray,
    Free/Busy information is stored in system public folder. If you want to decommission the Exchange 2007 Server, you need to add the replicas to Exchange 2013 Server.
    What's more, if the users use Outlook 2003, they will rely on the Free/Busy folders. If the users are using Outlook 2007 or newer, then Outlook utilizes something called the Availability Service and no longer relies on the Free/Busy folder.
    Please refer to the following article to migrate public folders from Exchange 2007 to Exchange 2013.
    Migrate Public Folders to Exchange 2013 From Previous Versions
    http://technet.microsoft.com/en-us/library/jj150486.aspx
    Besides, here is a helpful thread for your reference.
    move/migrate Public Folder from Exchange 2007 to Exchange 2010
    http://social.technet.microsoft.com/Forums/exchange/en-US/44b29a93-0149-4734-8e19-6679ad7701ce/movemigrate-public-folder-from-exchange-2007-to-exchange-2010?forum=exchange2010
    Hope it helps.
    If there are any problems, please feel free to let me know.
    Best regards,
    Amy
    Amy Wang
    TechNet Community Support

  • Public Folder Migration from Exchange 2007 to 2013 fails RelinquishedWlmStall budget limitations

    I have been trying to migrate approx 50 public folders from Exchange 2007 to Exchange 2013 for several months.  I have followed every link I can find on how to do the migration properly.  It will stay in a queued state for hours until the MRS is
    restarted.  It will then start copying messages.  After reaching 28% I get RelinquishedWlmStall as Status Detail.  Running the Get-PublicFolderMigrationRequestStatistics -IncludeReport | fl command I get the following: (truncated)
    Status                           : InProgress
    FailureTimestamp                 :
    IsValid                          : True
    ValidationMessage                :
    OrganizationId                   :
    RequestGuid                      : ff4af794-f31e-4334-959f-7d6c4ccbe310
    RequestQueue                     : PublicFolders
    ExchangeGuid                     : b12c1f83-c4ae-46bb-a26a-0422d90800e4
    Identity                         : eddf983d-5827-4a2a-98ef-820321ebebd0\ff4af794-f31e-4334-959f-7d6c4ccbe310
    DiagnosticInfo                   :
    Report                           
                                       4/23/2015 8:49:37 AM [pionexxxx] Request processing started.
                                       4/23/2015 8:49:37 AM [pionexxxxx] Cleared sync state for request
                                       00000000-0000-0000-0000-000000000000 due to 'CleanupOrphanedMailbox'.
                                       4/23/2015 8:49:38 AM [pionexxxxxx] Stage: CreatingFolderHierarchy. Percent complete:
                                       10.
                                       4/23/2015 8:49:38 AM [pionexxxxxx] Initializing folder hierarchy from mailbox '': 50
                                       folders total.
                                       4/23/2015 8:49:38 AM [pionexxxx] Folder creation progress: 0 folders created in
                                       mailbox 'b12c1f83-c4ae-46bb-a26a-0422d90800e4'.
                                       4/23/2015 8:49:38 AM [pionexxxxx] Warning: Failed to find or link recipient object
                                       'FF-D5-EF-1A-0A-95-D7-4B-89-02-A6-9E-DA-4D-23-4B' in active directory for mail
                                       enabled public folder 'Public Root/IPM_SUBTREE/AccountingFaxes' with EntryId '00-00
                                       00-00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-3B-C3-C1-30-22-E0-BE-4E
                                       98-03-B9-14-4F-B4-12-C1-00-00-00-0F-C3-4C-00-00'. This folder can be linked
                                       manually by running Enable-MailPublicFolder cmdlet after the migration completes.
                                       4/23/2015 8:49:39 AM [pionexxxx] Warning: Failed to find or link recipient object
                                       'D8-46-09-BE-0B-3D-6E-4A-95-10-8F-C5-AA-0B-88-50' in active directory for mail
                                       enabled public folder 'Public Root/IPM_SUBTREE/AccountingFaxes/CashRec/Inventory'
                                       with EntryId '00-00-00-00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-3B-
                                       3-C1-30-22-E0-BE-4E-98-03-B9-14-4F-B4-12-C1-00-00-00-12-6A-F5-00-00'. This folder
                                       can be linked manually by running Enable-MailPublicFolder cmdlet after the
                                       migration completes.
                                       4/23/2015 8:49:39 AM [pionexxxx] Warning: Failed to find or link recipient object
                                       'A6-12-DA-05-7D-21-DE-44-90-61-64-23-8C-62-41-F4' in active directory for mail
                                       enabled public folder 'Public Root/IPM_SUBTREE/AccountingFaxes/CashRec/Ulysses'
                                       with EntryId '00-00-00-00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-3B-
                                       3-C1-30-22-E0-BE-4E-98-03-B9-14-4F-B4-12-C1-00-00-00-0F-C3-7C-00-00'. This folder
                                       can be linked manually by running Enable-MailPublicFolder cmdlet after the
                                       migration completes.
                                       4/23/2015 8:49:40 AM [pionexxxx] Warning: Failed to find or link recipient object
                                       '96-76-90-F1-A5-B7-DB-41-A7-A3-D6-8D-86-AE-45-A5' in active directory for mail
                                       enabled public folder 'Public Root/IPM_SUBTREE/CSR Schedule' with EntryId '00-00-00
                                       00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-3B-C3-C1-30-22-E0-BE-4E-98
                                       03-B9-14-4F-B4-12-C1-00-00-00-0E-34-FF-00-00'. This folder can be linked manually
                                       by running Enable-MailPublicFolder cmdlet after the migration completes.
                                       4/23/2015 8:49:40 AM [pionexxxx] Warning: Failed to find or link recipient object
                                       '82-72-47-AA-D7-68-85-4C-91-92-41-45-8A-20-EA-6D' in active directory for mail
                                       enabled public folder 'Public Root/IPM_SUBTREE/DC 24 Hr Schedule' with EntryId '00-
                                       0-00-00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-85-62-89-2A-52-C3-92-
                                       5-93-F8-5A-6F-56-5D-D1-D4-00-00-00-00-27-37-00-00'. This folder can be linked
                                       manually by running Enable-MailPublicFolder cmdlet after the migration completes.
                                       4/23/2015 8:49:41 AM [pionexxxx] Folder hierarchy initialized for mailbox
                                       'b12c1f83-c4ae-46bb-a26a-0422d90800e4': 46 folders created.
                                       4/23/2015 8:49:41 AM [pionexxxx] Stage: CreatingInitialSyncCheckpoint. Percent
                                       complete: 15.
                                       4/23/2015 8:49:41 AM [pionexxxx] Initial sync checkpoint progress: 0/50 folders
                                       processed. Currently processing mailbox 'b12c1f83-c4ae-46bb-a26a-0422d90800e4'.
                                       4/23/2015 8:49:42 AM [pionexxxx] Initial sync checkpoint completed: 46 folders
                                       processed.
                                       4/23/2015 8:49:42 AM [pionexxxx] Stage: LoadingMessages. Percent complete: 20.
                                       4/23/2015 8:49:43 AM [pionexxxx] Messages have been enumerated successfully. 40607
                                       items loaded. Total size: 149 MB (156,253,810 bytes).
                                       4/23/2015 8:49:43 AM [pionexxxx] Stage: CopyingMessages. Percent complete: 25.
                                       4/23/2015 8:49:43 AM [pionexxxx] Copy progress: 0/40607 messages, 0 B (0
                                       bytes)/149 MB (156,253,810 bytes), 11/50 folders completed.
                                       4/23/2015 9:04:37 AM [pionexxxx] Stage: CopyingMessages. Percent complete: 28.
                                       4/23/2015 9:04:37 AM [pionexxxxx] Copy progress: 3660/40607 messages, 7.015 MB
                                       (7,355,409 bytes)/149 MB (156,253,810 bytes), 11/50 folders completed.
                                       4/23/2015 9:04:37 AM [pionexxxx] Relinquishing job because of large delays due to
                                       unfavorable server health or budget limitations.
    ItemsTransferred                 : 3660
    PercentComplete                  : 25
    4/23/2015 9:04:37 AM [pionexxxx] Relinquishing job because of large delays due to
    unfavorable server health or budget limitations.
    It never tries to restart.  Can anyone please help?  The server checks for health all come back ok.   I will be more than glad to include further information.  

    Hi,
    Basic on the error message, I notice that public folder migrate slow and display that “Relinquishing job because of large delays due to unfavorable server health or budget limitations” .
    If I misunderstand your concern, please do not hesitate to let me know.
    Since it is just slow and not failing, please do not stop the batch, it might connect to another server for sync.
    Meanwhile, please refer to below link so that get details about Exchange Online migration performance and best practices:
    https://technet.microsoft.com/library/dn592150(v=exchg.150).aspx
    If the issue persists, please collect the relevant migration report for further troubleshooting.
    Thanks
    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]
    Allen Wang
    TechNet Community Support

  • Concurrent mailbox moves from Exchange 2007 to 2013

    We are in the process of migrating from Exchange 2007 to Exchange 2013. We have about 200 mailboxes and we want to move them in groups of 40-50 at a time. I am trying to get more then 1 mailbox to actually sync to the new database at once.
    I start the batch with 49 mailboxes but only 1 mailbox is showing any progress when I go to details. They all have a status of "syncing" but only one has any "items synced".
    I have run multiple articles about increasing concurrent migrations from 2007 to 2010 and 2010 to 2013 and they all mention going to MsExchangeMailboxReplication.exe.config on the destination server and setting the “MaxActiveMovesPerTargetMDB" value
    to something larger. By default 2013 has it set to 20 would should be more than enough  for me. However despite this setting I still only see 1 mailbox syncing at a time.
    Is there someplace I should be making a similar change on the 2007 box? I can't find a file with that name so I am not sure if there is something to change or if it's even needed.
    Why is this not working? Any help is much appreciated. Thanks!

    Outlook will show the infamous login popup and users will not be able to access Exchange 2013 Public Folders.
    You can check the Outlook Clients version in Exchange Management Shell with Get-LoginStatistics (ex. Outlook 2010):
    Get-Logonstatistics | select-object username,clientversion | where {$_.clientversion -gt "14.0*" -AND $_.clientversion -lt "14.0.6117.5001"}
    Step by Step Screencasts and Video Tutorials

  • Moving from Exchange 2007 to 2013 (leaving the DNS Server for it's own dedicated server)

    Hello! I am quite new to Exchange and Server management in general. I will do my best to explain my situation.
    I am looking to move my Exchange server off of our DNS server. When we installed them on the same server, we did not have the funds to buy 2 separate servers. I am told that it is best to separate the two. I have followed the Microsoft instructions for installing
    the prerequisites for Exchange 2013 on a 2012 R2 server, and i am at the point where it wants me to configure AD LDS. As I have active directory running on the current server, I was a little hesitant to just install it without understanding what i am doing.
    After the AD LDS is configured, I believe i can move forward with installing Exchange 2013 (all 3 roles will be hosted on the new server), export the mailboxes from 2007 server and import them into the new Exchange 2013 server. After 2013 is up and stable,
    I plan on removing 2007 from the old server (DNS server).
    What are my next steps after importing the mailboxes? Am i missing important details that I need to change or migrate?
    My biggest fear is that nothing works after the installation and moving the mailboxes over. For that case, it makes sense to keep 2007 installed as a fallback for when my installation fails and all i have lost is just my time :)
    Current Server:
    Windows Server 2008 Standard (64 bit)
    1. Roles: Active Directory, DNS, IIS
    2. Software: Exchange 2007
    New Server:
    Windows 2012 R2 Server
    1. Roles: ???
    1. Software to install: Exchange 2013
    Thank you for any help you can provide!

    These are good resources, but i am still caught up with the active directory issue.  Am I able to keep the old Domain/DNS/Active directory on it's current server and move Exchange 2007 off onto a new server (with Exchange 2013)?
    In the first example, he is moving everything (domain controller, exchange, users, etc) onto a different server and decommissioning it.I've been told that it would be better practice to keep the domain and exchange on 2 different servers. Is this true?
    I go to run commands like:
    .\setup /PrepareAD /OrganizationName: orgname /IAcceptExchangeServerLicenseTerms
    on the new exchange server, as a prerequisite and it doesnt recognize the command - even after following the steps before. Is this because the new server is not a domain controller? does it have to be? What are the best practices for setting up a server(s)
    with exchange + domain controller?
    Thanks for responding.

  • Move Mailbox from Exchange 2007 to 2013 creates additional Contacts and Junk E-mail folders in Outlook Clients

    I have moved a handful of mailboxes from my Exchange 2007 server to my new Exchange 2013 server.  When the users logon to Outlook, usually Outlook 2007 Pro, they have a new default Contacts folder and Junk Email folder that are empty.  I
    have to copy all the user's contacts into the new default folder and delete the old one.  Not sure why this is happening.  Any information would be appreciated.  Thanks.

    Are you sure your Outlook 2007 is compatible with Exchange 2013?
    http://technet.microsoft.com/en-us/library/aa996719(v=exchg.150).aspx
    http://support.microsoft.com/default.aspx?kbid=2687404
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Public Folder Migration Fails from Exchange 2007 to 2013

    I am attempting to sync public folders between Exchange 2007 and Exchange 2013.  All the data has been copied over to the Exchange 2013 server but I am getting an error when creating the folders and their permissions.  
    I saw a previous thread which looked similar and I have set the bad item limit to one million as well as set mail-disable on the source public folders but I am still receiving these errors.
    I set the following commands
    Get-PublicFolderMigrationRequest | Set-PublicFolderMigrationRequest -baditemlimit 1000000
    Get-PublicFolderMigrationRequest | Resume-PublicFolderMigrationRequest
    and on the source mailbox server:  
    Get-publicfolder \Non_IPM_subtree -Recurse | Disable-MailPublicFolder
    12/2/2013 12:56:18 PM [ex01] The Microsoft Exchange Mailbox Replication service
    'ex01.domain.LOCAL' (15.0.712.11 caps:3F) is examining the request.
    12/2/2013 12:56:18 PM [ex01] Connected to target mailbox
    'f5f50f32-d256-4639-840e-cf161edfb538', database 'mdb01', Mailbox server
    'ex01.domain.LOCAL' Version 15.0 (Build 712.0), proxy server 'ex01.domain.LOCAL'
    15.0.712.11 caps:FFCB07FFFF.
    12/2/2013 12:56:24 PM [ex01] Connected to source mailbox '', database
    '01SRV\Second Storage Group\Public Folder Database', Mailbox server
    '01SRV.domain.LOCAL' Version 8.3 (Build 327.0).
    12/2/2013 12:56:25 PM [ex01] Request processing continued, stage LoadingMessages.
    12/2/2013 12:56:34 PM [ex01] Copying messages is finished. Copying rules and
    security descriptors.
    12/2/2013 12:56:35 PM [ex01] A corrupted item was encountered: Folder ACL
    "schema-root"
    12/2/2013 12:56:36 PM [ex01] A corrupted item was encountered: Folder ACL
    "microsoft"
    12/2/2013 12:56:36 PM [ex01] A corrupted item was encountered: Folder ACL
    "exchangeV1"
    12/2/2013 12:56:36 PM [ex01] A corrupted item was encountered: Folder ACL "Default"
    12/2/2013 12:57:06 PM [ex01] A corrupted item was encountered: Folder ACL "ORG
    Contacts"
    12/2/2013 12:57:08 PM [ex01] A corrupted item was encountered: Folder ACL "ORG"

    Here we go again...
    This the full text from the migration report
    15.0.775.35 caps:07FFCB07FFFF.
    12/13/2013 6:11:00 AM [ex01] Connected to source mailbox '', database
    'DOMAINSRV\Second Storage Group\Public Folder Database', Mailbox server
    'DOMAINSRV.DOMAIN.LOCAL' Version 8.3 (Build 327.0).
    12/13/2013 6:11:00 AM [ex01] Request processing continued, stage LoadingMessages.
    12/13/2013 6:11:34 AM [ex01] Messages have been enumerated successfully. 124813
    items loaded. Total size: 69.88 GB (75,027,907,074 bytes).
    12/13/2013 6:11:34 AM [ex01] Stage: CopyingMessages. Percent complete: 81.
    12/13/2013 6:11:34 AM [ex01] Copy progress: 119253/124813 messages, 56.57 GB
    (60,737,390,033 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
    12/13/2013 6:16:34 AM [ex01] Stage: CopyingMessages. Percent complete: 81.
    12/13/2013 6:16:34 AM [ex01] Copy progress: 119670/124813 messages, 56.78 GB
    (60,967,399,787 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
    12/13/2013 6:21:52 AM [ex01] Stage: CopyingMessages. Percent complete: 82.
    12/13/2013 6:21:52 AM [ex01] Copy progress: 120208/124813 messages, 56.99 GB
    (61,189,806,498 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
    12/13/2013 6:26:55 AM [ex01] Stage: CopyingMessages. Percent complete: 82.
    12/13/2013 6:26:55 AM [ex01] Copy progress: 120850/124813 messages, 57.19 GB
    (61,401,994,205 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
    12/13/2013 6:30:54 AM [ex01] Transient error TimeoutErrorTransientException has
    occurred. The system will retry (1/60).
    12/13/2013 6:31:27 AM [ex01] The Microsoft Exchange Mailbox Replication service
    'ex01.DOMAIN.LOCAL' (15.0.775.35 caps:3F) is examining the request.
    12/13/2013 6:31:28 AM [ex01] Connected to target mailbox
    '543ef8dc-c797-44d4-b1f0-82c13ef9a8b3', database 'mdb01', Mailbox server
    'ex01.DOMAIN.LOCAL' Version 15.0 (Build 775.0), proxy server 'ex01.DOMAIN.LOCAL'
    15.0.775.35 caps:07FFCB07FFFF.
    12/13/2013 6:31:31 AM [ex01] Connected to source mailbox '', database
    'DOMAINSRV\Second Storage Group\Public Folder Database', Mailbox server
    'DOMAINSRV.DOMAIN.LOCAL' Version 8.3 (Build 327.0).
    12/13/2013 6:31:32 AM [ex01] Request processing continued, stage LoadingMessages.
    12/13/2013 6:32:18 AM [ex01] Messages have been enumerated successfully. 127721
    items loaded. Total size: 69.88 GB (75,027,907,074 bytes).
    12/13/2013 6:32:18 AM [ex01] Stage: CopyingMessages. Percent complete: 82.
    12/13/2013 6:32:18 AM [ex01] Copy progress: 120850/127721 messages, 57.19 GB
    (61,401,994,205 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
    12/13/2013 6:37:20 AM [ex01] Stage: CopyingMessages. Percent complete: 82.
    12/13/2013 6:37:20 AM [ex01] Copy progress: 121456/127721 messages, 57.39 GB
    (61,624,479,276 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
    12/13/2013 6:42:23 AM [ex01] Stage: CopyingMessages. Percent complete: 82.
    12/13/2013 6:42:23 AM [ex01] Copy progress: 122010/127721 messages, 57.59 GB
    (61,841,264,369 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
    12/13/2013 6:47:27 AM [ex01] Stage: CopyingMessages. Percent complete: 82.
    12/13/2013 6:47:27 AM [ex01] Copy progress: 122471/127721 messages, 57.81 GB
    (62,071,372,686 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
    12/13/2013 6:52:28 AM [ex01] Stage: CopyingMessages. Percent complete: 83.
    12/13/2013 6:52:28 AM [ex01] Copy progress: 122799/127721 messages, 58.03 GB
    (62,313,820,476 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
    12/13/2013 6:57:32 AM [ex01] Stage: CopyingMessages. Percent complete: 83.
    12/13/2013 6:57:32 AM [ex01] Copy progress: 123165/127721 messages, 58.26 GB
    (62,551,175,147 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
    12/13/2013 7:02:47 AM [ex01] Stage: CopyingMessages. Percent complete: 83.
    12/13/2013 7:02:47 AM [ex01] Copy progress: 123403/127721 messages, 58.48 GB
    (62,788,359,363 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
    12/13/2013 7:07:46 AM [ex01] Stage: CopyingMessages. Percent complete: 83.
    12/13/2013 7:07:46 AM [ex01] Copy progress: 123578/127721 messages, 58.68 GB
    (63,006,399,077 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
    12/13/2013 7:12:49 AM [ex01] Stage: CopyingMessages. Percent complete: 83.
    12/13/2013 7:12:49 AM [ex01] Copy progress: 123860/127721 messages, 58.89 GB
    (63,236,856,689 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
    12/13/2013 7:18:08 AM [ex01] Stage: CopyingMessages. Percent complete: 84.
    12/13/2013 7:18:08 AM [ex01] Copy progress: 124003/127721 messages, 59.14 GB
    (63,502,560,871 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
    12/13/2013 7:23:16 AM [ex01] Stage: CopyingMessages. Percent complete: 84.
    12/13/2013 7:23:16 AM [ex01] Copy progress: 124256/127721 messages, 59.37 GB
    (63,748,493,498 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
    12/13/2013 7:28:32 AM [ex01] Stage: CopyingMessages. Percent complete: 84.
    12/13/2013 7:28:32 AM [ex01] Copy progress: 124324/127721 messages, 59.62 GB
    (64,020,061,704 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
    12/13/2013 7:33:34 AM [ex01] Stage: CopyingMessages. Percent complete: 84.
    12/13/2013 7:33:34 AM [ex01] Copy progress: 124431/127721 messages, 59.85 GB
    (64,264,685,207 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
    12/13/2013 7:38:35 AM [ex01] Stage: CopyingMessages. Percent complete: 85.
    12/13/2013 7:38:35 AM [ex01] Copy progress: 124708/127721 messages, 60.08 GB
    (64,506,162,189 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
    12/13/2013 7:43:40 AM [ex01] Stage: CopyingMessages. Percent complete: 85.
    12/13/2013 7:43:40 AM [ex01] Copy progress: 125322/127721 messages, 60.31 GB
    (64,754,561,945 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
    12/13/2013 7:49:07 AM [ex01] Stage: CopyingMessages. Percent complete: 85.
    12/13/2013 7:49:07 AM [ex01] Copy progress: 125707/127721 messages, 60.56 GB
    (65,029,278,117 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
    12/13/2013 7:54:13 AM [ex01] Stage: CopyingMessages. Percent complete: 85.
    12/13/2013 7:54:13 AM [ex01] Copy progress: 125851/127721 messages, 60.82 GB
    (65,302,611,480 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
    12/13/2013 7:59:31 AM [ex01] Stage: CopyingMessages. Percent complete: 86.
    12/13/2013 7:59:31 AM [ex01] Copy progress: 126373/127721 messages, 61.02 GB
    (65,518,015,156 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
    12/13/2013 8:04:41 AM [ex01] Stage: CopyingMessages. Percent complete: 86.
    12/13/2013 8:04:41 AM [ex01] Copy progress: 126552/127721 messages, 61.16 GB
    (65,674,209,110 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
    12/13/2013 8:09:48 AM [ex01] Stage: CopyingMessages. Percent complete: 86.
    12/13/2013 8:09:48 AM [ex01] Copy progress: 126895/127721 messages, 61.34 GB
    (65,861,675,410 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
    12/13/2013 8:14:49 AM [ex01] Stage: CopyingMessages. Percent complete: 86.
    12/13/2013 8:14:49 AM [ex01] Copy progress: 127557/127721 messages, 61.53 GB
    (66,063,603,306 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
    12/13/2013 8:19:57 AM [ex01] Stage: CopyingMessages. Percent complete: 86.
    12/13/2013 8:19:57 AM [ex01] Copy progress: 128005/128325 messages, 61.69 GB
    (66,237,927,764 bytes)/69.88 GB (75,027,907,074 bytes), 192/5034 folders completed.
    12/13/2013 8:25:13 AM [ex01] Stage: CopyingMessages. Percent complete: 86.
    12/13/2013 8:25:13 AM [ex01] Copy progress: 128475/139047 messages, 61.86 GB
    (66,421,418,453 bytes)/69.87 GB (75,027,615,351 bytes), 204/5034 folders completed.
    12/13/2013 8:30:19 AM [ex01] Stage: CopyingMessages. Percent complete: 87.
    12/13/2013 8:30:19 AM [ex01] Copy progress: 128835/139047 messages, 62.07 GB
    (66,645,530,813 bytes)/69.87 GB (75,027,615,351 bytes), 204/5034 folders completed.
    12/13/2013 8:35:26 AM [ex01] Stage: CopyingMessages. Percent complete: 87.
    12/13/2013 8:35:26 AM [ex01] Copy progress: 129166/139047 messages, 62.25 GB
    (66,842,856,718 bytes)/69.87 GB (75,027,615,351 bytes), 204/5034 folders completed.
    12/13/2013 8:40:27 AM [ex01] Stage: CopyingMessages. Percent complete: 87.
    12/13/2013 8:40:27 AM [ex01] Copy progress: 129621/139047 messages, 62.45 GB
    (67,056,383,800 bytes)/69.87 GB (75,027,615,351 bytes), 204/5034 folders completed.
    12/13/2013 8:46:30 AM [ex01] Stage: CopyingMessages. Percent complete: 87.
    12/13/2013 8:46:30 AM [ex01] Copy progress: 129846/139047 messages, 62.65 GB
    (67,268,508,177 bytes)/69.87 GB (75,027,615,351 bytes), 204/5034 folders completed.
    12/13/2013 8:56:48 AM [ex01] Stage: CopyingMessages. Percent complete: 88.
    12/13/2013 8:56:48 AM [ex01] Copy progress: 130475/139047 messages, 63.06 GB
    (67,715,144,500 bytes)/69.87 GB (75,027,615,351 bytes), 204/5034 folders completed.
    12/13/2013 9:01:58 AM [ex01] Stage: CopyingMessages. Percent complete: 88.
    12/13/2013 9:01:58 AM [ex01] Copy progress: 130823/139047 messages, 63.28 GB
    (67,942,071,073 bytes)/69.87 GB (75,027,615,351 bytes), 204/5034 folders completed.
    12/13/2013 9:07:02 AM [ex01] Stage: CopyingMessages. Percent complete: 88.
    12/13/2013 9:07:02 AM [ex01] Copy progress: 131336/139047 messages, 63.44 GB
    (68,121,053,596 bytes)/69.87 GB (75,027,615,351 bytes), 204/5034 folders completed.
    12/13/2013 9:12:18 AM [ex01] Stage: CopyingMessages. Percent complete: 88.
    12/13/2013 9:12:18 AM [ex01] Copy progress: 131776/139047 messages, 63.63 GB
    (68,323,645,651 bytes)/69.87 GB (75,027,615,351 bytes), 204/5034 folders completed.
    12/13/2013 9:17:49 AM [ex01] Stage: CopyingMessages. Percent complete: 88.
    12/13/2013 9:17:49 AM [ex01] Copy progress: 131940/139047 messages, 63.75 GB
    (68,452,787,403 bytes)/69.87 GB (75,027,615,351 bytes), 204/5034 folders completed.
    12/13/2013 9:23:02 AM [ex01] Stage: CopyingMessages. Percent complete: 89.
    12/13/2013 9:23:02 AM [ex01] Copy progress: 132194/139047 messages, 63.9 GB
    (68,614,192,595 bytes)/69.87 GB (75,027,615,351 bytes), 204/5034 folders completed.
    12/13/2013 9:28:19 AM [ex01] Stage: CopyingMessages. Percent complete: 89.
    12/13/2013 9:28:19 AM [ex01] Copy progress: 132405/139047 messages, 64.05 GB
    (68,773,962,785 bytes)/69.87 GB (75,027,615,351 bytes), 204/5034 folders completed.
    12/13/2013 9:33:22 AM [ex01] Stage: CopyingMessages. Percent complete: 89.
    12/13/2013 9:33:22 AM [ex01] Copy progress: 132617/139047 messages, 64.17 GB
    (68,906,275,781 bytes)/69.87 GB (75,027,615,351 bytes), 204/5034 folders completed.
    12/13/2013 9:38:34 AM [ex01] Stage: CopyingMessages. Percent complete: 89.
    12/13/2013 9:38:34 AM [ex01] Copy progress: 132865/139047 messages, 64.36 GB
    (69,106,121,613 bytes)/69.87 GB (75,027,615,351 bytes), 204/5034 folders completed.
    12/13/2013 9:43:53 AM [ex01] Stage: CopyingMessages. Percent complete: 89.
    12/13/2013 9:43:53 AM [ex01] Copy progress: 133061/139047 messages, 64.56 GB
    (69,316,087,375 bytes)/69.87 GB (75,027,615,351 bytes), 204/5034 folders completed.
    12/13/2013 9:48:53 AM [ex01] Stage: CopyingMessages. Percent complete: 89.
    12/13/2013 9:48:53 AM [ex01] Copy progress: 133269/139047 messages, 64.78 GB
    (69,553,487,559 bytes)/69.87 GB (75,027,615,351 bytes), 204/5034 folders completed.
    12/13/2013 9:53:59 AM [ex01] Stage: CopyingMessages. Percent complete: 90.
    12/13/2013 9:53:59 AM [ex01] Copy progress: 133631/139047 messages, 64.98 GB
    (69,772,059,026 bytes)/69.87 GB (75,027,615,351 bytes), 204/5034 folders completed.
    12/13/2013 9:59:29 AM [ex01] Stage: CopyingMessages. Percent complete: 90.
    12/13/2013 9:59:29 AM [ex01] Copy progress: 133853/139047 messages, 65.19 GB
    (70,002,477,102 bytes)/69.87 GB (75,027,615,351 bytes), 204/5034 folders completed.
    12/13/2013 10:04:33 AM [ex01] Stage: CopyingMessages. Percent complete: 90.
    12/13/2013 10:04:33 AM [ex01] Copy progress: 134089/139047 messages, 65.36 GB
    (70,179,472,038 bytes)/69.87 GB (75,027,615,351 bytes), 204/5034 folders completed.
    12/13/2013 10:09:04 AM [ex01] Transient error TimeoutErrorTransientException has
    occurred. The system will retry (1/60).
    12/13/2013 10:09:40 AM [ex01] The Microsoft Exchange Mailbox Replication service
    'ex01.DOMAIN.LOCAL' (15.0.775.35 caps:3F) is examining the request.
    12/13/2013 10:09:43 AM [ex01] Connected to target mailbox
    '543ef8dc-c797-44d4-b1f0-82c13ef9a8b3', database 'mdb01', Mailbox server
    'ex01.DOMAIN.LOCAL' Version 15.0 (Build 775.0), proxy server 'ex01.DOMAIN.LOCAL'
    15.0.775.35 caps:07FFCB07FFFF.
    12/13/2013 10:09:48 AM [ex01] Connected to source mailbox '', database
    'DOMAINSRV\Second Storage Group\Public Folder Database', Mailbox server
    'DOMAINSRV.DOMAIN.LOCAL' Version 8.3 (Build 327.0).
    12/13/2013 10:09:48 AM [ex01] Request processing continued, stage LoadingMessages.
    12/13/2013 10:10:20 AM [ex01] Messages have been enumerated successfully. 139047
    items loaded. Total size: 69.87 GB (75,027,615,351 bytes).
    12/13/2013 10:10:20 AM [ex01] Stage: CopyingMessages. Percent complete: 90.
    12/13/2013 10:10:20 AM [ex01] Copy progress: 134097/139047 messages, 65.39 GB
    (70,216,735,350 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
    12/13/2013 10:11:21 AM [ex01] Stage: CopyingMessages. Percent complete: 90.
    12/13/2013 10:11:21 AM [ex01] Copy progress: 134133/139047 messages, 65.42 GB
    (70,245,991,410 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
    12/13/2013 10:11:22 AM [ex01] Stage: CopyingMessages. Percent complete: 90.
    12/13/2013 10:11:22 AM [ex01] Copy progress: 134133/139047 messages, 65.42 GB
    (70,245,991,410 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
    12/13/2013 10:11:22 AM [ex01] The long-running job has been temporarily postponed.
    It will be picked up again when resources become available.
    12/13/2013 10:11:26 AM [ex01] The Microsoft Exchange Mailbox Replication service
    'ex01.DOMAIN.LOCAL' (15.0.775.35 caps:3F) is examining the request.
    12/13/2013 10:11:26 AM [ex01] Connected to target mailbox
    '543ef8dc-c797-44d4-b1f0-82c13ef9a8b3', database 'mdb01', Mailbox server
    'ex01.DOMAIN.LOCAL' Version 15.0 (Build 775.0), proxy server 'ex01.DOMAIN.LOCAL'
    15.0.775.35 caps:07FFCB07FFFF.
    12/13/2013 10:11:31 AM [ex01] Connected to source mailbox '', database
    'DOMAINSRV\Second Storage Group\Public Folder Database', Mailbox server
    'DOMAINSRV.DOMAIN.LOCAL' Version 8.3 (Build 327.0).
    12/13/2013 10:11:32 AM [ex01] Request processing continued, stage LoadingMessages.
    12/13/2013 10:11:49 AM [ex01] Messages have been enumerated successfully. 139047
    items loaded. Total size: 69.87 GB (75,027,615,351 bytes).
    12/13/2013 10:11:49 AM [ex01] Stage: CopyingMessages. Percent complete: 90.
    12/13/2013 10:11:49 AM [ex01] Copy progress: 134097/139047 messages, 65.39 GB
    (70,216,735,350 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
    12/13/2013 10:17:02 AM [ex01] Stage: CopyingMessages. Percent complete: 90.
    12/13/2013 10:17:02 AM [ex01] Copy progress: 134444/139047 messages, 65.61 GB
    (70,448,693,136 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
    12/13/2013 10:22:08 AM [ex01] Stage: CopyingMessages. Percent complete: 90.
    12/13/2013 10:22:08 AM [ex01] Copy progress: 134729/139047 messages, 65.82 GB
    (70,668,635,903 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
    12/13/2013 10:27:16 AM [ex01] Stage: CopyingMessages. Percent complete: 91.
    12/13/2013 10:27:16 AM [ex01] Copy progress: 135103/139047 messages, 66 GB
    (70,867,621,766 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
    12/13/2013 10:32:27 AM [ex01] Stage: CopyingMessages. Percent complete: 91.
    12/13/2013 10:32:27 AM [ex01] Copy progress: 135380/139047 messages, 66.19 GB
    (71,070,869,590 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
    12/13/2013 10:39:14 AM [ex01] A large item was encountered: Item (IPM.Note)
    Subject:"Ellicott Barge Models", Size: 77.95 MB (81,733,960 bytes), Folder:"x 7)
    Ellicott Filed"
    12/13/2013 10:39:14 AM [ex01] Stage: CopyingMessages. Percent complete: 91.
    12/13/2013 10:39:14 AM [ex01] Copy progress: 135611/139047 messages, 66.44 GB
    (71,343,628,026 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
    12/13/2013 10:44:44 AM [ex01] Stage: CopyingMessages. Percent complete: 91.
    12/13/2013 10:44:44 AM [ex01] Copy progress: 135911/139047 messages, 66.63 GB
    (71,544,181,750 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
    12/13/2013 10:51:00 AM [ex01] Stage: CopyingMessages. Percent complete: 91.
    12/13/2013 10:51:00 AM [ex01] Copy progress: 136252/139047 messages, 66.85 GB
    (71,779,294,348 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
    12/13/2013 10:56:06 AM [ex01] Stage: CopyingMessages. Percent complete: 92.
    12/13/2013 10:56:06 AM [ex01] Copy progress: 136462/139047 messages, 67.05 GB
    (71,995,944,420 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
    12/13/2013 11:01:11 AM [ex01] Stage: CopyingMessages. Percent complete: 92.
    12/13/2013 11:01:11 AM [ex01] Copy progress: 136594/139047 messages, 67.26 GB
    (72,223,775,275 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
    12/13/2013 11:06:15 AM [ex01] Stage: CopyingMessages. Percent complete: 92.
    12/13/2013 11:06:15 AM [ex01] Copy progress: 136726/139047 messages, 67.43 GB
    (72,406,316,662 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
    12/13/2013 11:11:17 AM [ex01] Stage: CopyingMessages. Percent complete: 92.
    12/13/2013 11:11:17 AM [ex01] Copy progress: 136801/139047 messages, 67.6 GB
    (72,586,529,915 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
    12/13/2013 11:16:32 AM [ex01] Stage: CopyingMessages. Percent complete: 92.
    12/13/2013 11:16:32 AM [ex01] Copy progress: 136879/139047 messages, 67.8 GB
    (72,801,385,018 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
    12/13/2013 11:21:34 AM [ex01] Stage: CopyingMessages. Percent complete: 93.
    12/13/2013 11:21:34 AM [ex01] Copy progress: 136953/139047 messages, 67.98 GB
    (72,993,383,384 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
    12/13/2013 11:26:47 AM [ex01] Stage: CopyingMessages. Percent complete: 93.
    12/13/2013 11:26:47 AM [ex01] Copy progress: 137103/139047 messages, 68.19 GB
    (73,218,959,998 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
    12/13/2013 11:31:57 AM [ex01] Stage: CopyingMessages. Percent complete: 93.
    12/13/2013 11:31:57 AM [ex01] Copy progress: 137533/139047 messages, 68.39 GB
    (73,429,774,999 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
    12/13/2013 11:37:01 AM [ex01] Stage: CopyingMessages. Percent complete: 93.
    12/13/2013 11:37:01 AM [ex01] Copy progress: 137720/139047 messages, 68.58 GB
    (73,633,221,526 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
    12/13/2013 11:42:15 AM [ex01] Stage: CopyingMessages. Percent complete: 93.
    12/13/2013 11:42:15 AM [ex01] Copy progress: 137812/139047 messages, 68.74 GB
    (73,809,270,838 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
    12/13/2013 11:47:27 AM [ex01] Stage: CopyingMessages. Percent complete: 94.
    12/13/2013 11:47:27 AM [ex01] Copy progress: 138129/139047 messages, 68.95 GB
    (74,030,024,926 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
    12/13/2013 11:52:32 AM [ex01] Stage: CopyingMessages. Percent complete: 94.
    12/13/2013 11:52:32 AM [ex01] Copy progress: 138322/139047 messages, 69.17 GB
    (74,265,630,831 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
    12/13/2013 11:57:36 AM [ex01] Stage: CopyingMessages. Percent complete: 94.
    12/13/2013 11:57:36 AM [ex01] Copy progress: 138505/139047 messages, 69.36 GB
    (74,471,042,974 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
    12/13/2013 12:03:18 PM [ex01] Stage: CopyingMessages. Percent complete: 94.
    12/13/2013 12:03:18 PM [ex01] Copy progress: 138696/139047 messages, 69.52 GB
    (74,643,441,657 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
    12/13/2013 12:10:25 PM [ex01] A large item was encountered: Item (IPM.Note)
    Subject:"Walkway Hose Mystery", Size: 93.98 MB (98,540,300 bytes), Folder:"Sent
    Items"
    12/13/2013 12:10:25 PM [ex01] Stage: CopyingMessages. Percent complete: 94.
    12/13/2013 12:10:25 PM [ex01] Copy progress: 138848/139047 messages, 69.71 GB
    (74,851,776,952 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
    12/13/2013 12:14:42 PM [ex01] Copying messages is finished. Copying rules and
    security descriptors.
    12/13/2013 12:14:52 PM [ex01] A corrupted item was encountered: Folder ACL
    "schema-root"
    12/13/2013 12:14:52 PM [ex01] A corrupted item was encountered: Folder ACL
    "microsoft"
    12/13/2013 12:14:53 PM [ex01] A corrupted item was encountered: Folder ACL
    "exchangeV1"
    12/13/2013 12:14:53 PM [ex01] A corrupted item was encountered: Folder ACL "Default"
    12/13/2013 12:15:11 PM [ex01] A corrupted item was encountered: Folder ACL "DOMAIN
    Contacts"
    12/13/2013 12:15:13 PM [ex01] A corrupted item was encountered: Folder ACL "DOMAIN"
    12/13/2013 1:41:05 PM [ex01] Initial seeding completed, 139047 items copied, total
    size 69.87 GB (75,027,615,351 bytes).
    12/13/2013 1:41:06 PM [ex01] Stage: CopyingMessages. Percent complete: 95.
    12/13/2013 1:41:06 PM [ex01] Copy progress: 139047/139047 messages, 69.87 GB
    (75,027,615,351 bytes)/69.87 GB (75,027,615,351 bytes), 47/5034 folders completed.
    12/13/2013 1:41:06 PM [ex01] Fatal error TooManyLargeItemsPermanentException has
    occurred.
    ObjectState : New
    [PS] C:\Windows\system32>Get-PublicFolderMigrationRequest | Get-PublicFolderMigrationRequestStatistics
    Name StatusDetail SourceDatabase PercentComplete
    PublicFolderMigration FailedOther DOMAINSRV\Second Storage Group\Public... 95
    [PS] C:\Windows\system32>

  • Outlook cannot connect after mailbox move from Exchange 2007 to 2013

    I am in the middle of migrating an Exchange Server 2007 to 2013. Everything went fine up until I moved the first mailbox. I can access the mailbox via OWA, but not Outlook 2010. When I checked the account settings, the server is incorrect. It shows [email protected]
    If I manually enter the name of the Exchange 2007 server, it changes to the Exchange 2013 server, as it should. I save the settings, open Outlook, the connection fails, and the server setting is changed to [email protected]
    I then ran the Microsoft Connectivity Analyzer. There are 2 lines which caught my attention:
    AutoDiscoverInternalRpcClientServer
    [email protected]
    AutoDiscoverHomeMdbDn
    /o=mydomainMail/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=[email protected]/cn=Microsoft Private MDB
    I've checked and rechecked everything and can't seem to locate my error.
    Any thoughts? Thanks.

    Totally correct!
    If you don't plan to maintain Outlook then you plan to fail :( 
    Additional links etc are in here:
    http://blogs.technet.com/b/rmilne/archive/2013/07/18/patching-exchange-don-t-overlook-outlook.aspx 
    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.

  • Migrate from Exchange 2007 to 2013 without modifying client devices

    Let's use contesso.com as an example.  Let's say the Exchange 2007 server's internal and external
    name are currently mail.contesso.com.  Now I am going to introduce a new Exchange 2013 server named mail2.contesso.com.  The Exchange Server Deployment Assistant says that we should make the external DNS entry point mail.contesso.com to the 2013
    server and legacy.contesso.com point to the 2007 server.  That takes care of external clients.  I don't understand how internal clients will find the correct server because they are all configured for mail.contesso.com which internally points to
    the 2007 server.  We have over 200 users with multiple devices.  We do not want to be forced to create new Outlook profiles or change the configuration of their mobile devices.
    Thanks,
    Tina
    Tina M. White Boundless Data

    Hi,
    Mail.contesso.com -> Exchange 2013 OWA/ActiveSync/OA
    Legacy.contesso.com -> Exchange 2007 OWA/ActiveSync/OA
    Autodiscover.Contesso.com
    Make sure the Redirection settings are configured properly.
    Regards,
    Simon Wu
    TechNet Community Support

  • Intermittent OWA authtication issue for new users on Exchange 2007

    Hi
    We are experiencing a strange issue with OWA authentication and its happening with new users only including me. We are a small organization with approx. 70 users. Issue is with
    new user accounts only.
    Access to OWA stops working from any machine for the new users also they get authentication error on their phones. I have checked permissions on Virtual Directory on exchange server,
    all seems to be in place. I have checked event viewer but it doesn't have any event for auth. failure.
    IIS logs have the following Message,
    2014-02-05 09:37:28 W3SVC1 (EXCHANGE SERVER IP) GET /owa/ - 443 myusername 77.88.97.134 Mozilla/5.0+(Windows+NT+6.3;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko
    401 1 1326
    Server details
    Server 2003 Ent. x64 R2
    Exchange Server 2007 Version: 08.03.0342.000
    IIS 6.0
    Rebooting the exchange server resolves the issue sometime for 2 days sometime for 3-4 weeks.
    Please advise.
    Best Regards
    Prabhash

    Hi,
    According to your description, new users cannot login OWA .
    And to narrow down the cause, I recommend the following troubleshooting:
    1. Check if the option"User must change password on next login" has been selected for the new users.
    2. Check if the new users can login Outlook when the issue happens.
    3. Check if it’s configured to use Integrated Windows authentication for OWA web site:
    http://support.microsoft.com/kb/871179
    If you have any question, please feel free to let me know. 
    Thanks,
    Angela Shi
    TechNet Community Support

Maybe you are looking for