MSExchangeGuru.com

Learn Exchange the Guru way !!!

 

Exchange 2010/2007 to 2013 Migration and Co-existence Guide

We don’t have a lot of guides out there helping with a step by step guide for the migration and co-existence of Exchange 2010/2007 to Exchange 2013So, here you go !!!

Migrate using CodeTwo

Update:

If you are planning to employ a third party product for migration – look no further. CodeTwo is a mature and reliable product for full blown Exchange migraiton from

Exchange 2003/2007/2010 – cross forest or cross domain migration:

Take a look here: 

CodeTwo Exchange migration for Exchange 2003 to 2010/2013: Operational review: https://msexchangeguru.com/2013/11/24/codetwo-exchange-migration/

Download here: 

Download Codetwo for free: http://www.codetwo.com/exchange-migration/

Before you proceed with the actual migration steps, these articles may be of interest to you:

Exchange 2013 CAS Role Demystified: https://msexchangeguru.com/2013/05/22/exchange-2013-cas/
Exchange 2013 High Availability demystified: https://msexchangeguru.com/2013/05/23/e2013-ha-demystified/
Load Balancing Exchange Server 2013 – Good to know stuff: https://msexchangeguru.com/2013/06/05/load-balancing/
Public Folders Migration from Exchange 2007/2010 to Exchange 2013: https://msexchangeguru.com/2013/04/18/exchange2013-public-folders/
Upgrade from Exchange 2013 CU1 or RTM to CU2: https://msexchangeguru.com/2013/07/10/install-e2013-cu2/
Monitoring and troubleshooting Exchange using powershell: https://msexchangeguru.com/2013/07/23/monitoring-powershell/

For Complex Exchange 2007 migration check the common errors here – http://blogs.technet.com/b/exchange/archive/2007/09/10/3403885.aspx

Check our multisite url and authentication blog here – https://msexchangeguru.com/2015/08/22/e20132007-urlsauth-multiadsite/

 

Preparing Exchange 2010/2007

  1. Install the hotfix 2550886 for DAG failover improvements on Exchange 2010/2007 DAG servers.

    http://support.microsoft.com/?kbid=2550886

  2. Login to the Exchange 2010/2007 server with Schema Admins, enterprise admins, domain admins and organization management group member id as SP 3 will extend the schema.
  3. Install Exchange 2010/2007 SP3 on all the exchange 2010/2007 servers in CAS then HT then mailbox role order if they are not on the same server

    SP3 can be downloaded from the below link:

    http://www.microsoft.com/en-us/download/details.aspx?id=36768

  4. Check the below link for SP3 installation steps

    https://msexchangeguru.com/2013/04/03/exchange-2010/2007-sp3/

 

Installing Exchange 2013

  1. I would suggest going for Windows 2012 for Exchange 2013 but you can use windows 2008 R2 SP1 as well.
  2. Install the windows 2012 server or Windows 2008 R2 SP1 on a new server and join the domain. It can be virtual or physical. Now Microsoft support virtualized mailbox role.
  3. Run the windows update and install all the recommended updates.
  4. You might like to configure windows NLB if you don’t have NLB hardware. Check the below blog on it. (optional)  https://msexchangeguru.com/2013/08/14/windowsnlb/
  5. For Active Directory preparation check the “step 3 preparing active directory” at the blog mentioned below:       https://msexchangeguru.com/2013/04/29/install-e2013/
  6. Install the following prerequisites for Exchange 2013

For Windows 2012:

  1. Open Windows PowerShell.
  2. Run the following command to install the required Windows components.

    Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation

  3. Restart the server.
  4. http://www.microsoft.com/en-us/download/details.aspx?id=34992

  5. http://www.microsoft.com/en-us/download/details.aspx?id=17062

  6. http://www.microsoft.com/en-us/download/details.aspx?id=26604

For Windows 2008:

  1. Open Windows PowerShell.
  2. Run the following command to load the Server Manager module.

    Import-Module ServerManager

  3. Run the following command to install the required Windows components.

        Add-WindowsFeature Desktop-Experience, NET-Framework, NET-HTTP-Activation, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Web-Server, WAS-Process-Model, Web-Asp-Net, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI

  4. Restart the server
  5. http://msdn.microsoft.com/en-us/library/5a4x27ek(VS.110).aspx

  6. http://www.microsoft.com/en-us/download/details.aspx?id=34595

  7. Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit

    http://www.microsoft.com/en-us/download/details.aspx?id=34992

  8. http://www.microsoft.com/en-us/download/details.aspx?id=17062

  9. http://www.microsoft.com/en-us/download/details.aspx?id=26604

  10. http://support.microsoft.com/?kbid=974405&wa=wsignin1.0

  11. http://support.microsoft.com/?kbid=2619234

  12. http://support.microsoft.com/?kbid=2533623

   6. Restart the server

   7. Exchange 2013 Installation – Please follow the below link for the Exchange 2013 installation: https://msexchangeguru.com/2013/04/29/install-e2013/or Exchange 2013 SP1installation: https://msexchangeguru.com/2014/03/02/e2013sp1-installationupgrade/

Imp: You can directly install Exchange 2013 CU1 as well. If you directly install CU1 then you can skip step 12 – Testing mailbox move without CU1. If you are installing CU2 make sure you are installing CU2 V2.

If you are doing new installation then you can directly install Exchange 2013 CU1 which itself is a full setup. You can follow same schema update and AD preparation steps.

After Exchange 2013 installation the biggest challenge will be how to login to the EAC, there is no mailbox on Exchange 2013 and redirection or proxy is not configured to use the existing Exchange admin user.

If you are trying to access EAC for the first time and your mailbox is on Exchange 2010, you need to use the URL in the format:

https://Exchange2013ServerName/ecp?ExchClientVer=15

This is because in a co-existence scenario, your mailbox is still housed on the Exchange 2010 mailbox server, the browser will default to the Exchange Server 2010 ECP. Now if you want to access the Exchange 2010 ECP and your mailbox resides on an Exchange 2013 mailbox server, use the following URL:

https://Exchange2010ServerName/ecp?ExchClientVer=14.

Take a look at:

Working with EAC or Exchange administration center in Exchange 2013 – Part1: https://msexchangeguru.com/2013/01/16/eac-exchange-2013/

So you need to create a mailbox to administer Exchange 2013. We will follow the below steps:

    1. Create a mailbox in Exchange 2013 mailbox database.
    2. “New-Mailbox –name 2013Admin –userPrincipalName 2013Admin@domain.com –Database “2013 DBName””
    3. Run Get-mailboxdatabase to check the database name

      4. Give the permission to the mailbox to Administrate EAC.

               Add the following group membership:

                 Domain Admins

                 Schema Admins

                 Enterprise Admins

                 Organization Management

Test mailbox migration without CU1 for Exchange 2013

  1. Now, you should be able to login to EAC by going to the url https://localhost/ECP. If you will test the mailbox migration from Exchange 2010/2007 to Exchange 2013 before CU1 for Exchange 2013, it will be working but full co-existence will not work so it is a necessity to install CU1. As an example my Servers are mentioned below:


     

     

  2. EAC will show Databases from both the servers


 

  • Now I am migrating the mailbox being Exchange 2010/2007 on SP3 and Exchange 2013 without CU1.

 

Created new mailbox in Exchange 2010/2007, you can see 2013 database is not showing here


 

  • Database before move

 


 

  • I have moved the mailbox from Exchange 2013 EAC to Exchange 2013 database. Now click on migration to check the status

 


 

  • Now Refresh and you will see completed depends on the size of mailbox.

 


 

  • Check the Database name has changed

 

 

Continue the Exchange 2013 CU1 installation

       5. If you have not install CU1 version of exchange 2013 then this is the time to install Exchange 2013 Cumulative update 1 so that we avoid any co-existence issue. If you are doing new installation then you can directly install Exchange 2013 CU1 which itself is a full setup. You can follow same schema update and AD preparation steps mentioned in the Exchange 2013 installation article

Update 4/7/2014: Now – We can go for SP1 – https://msexchangeguru.com/2014/03/02/e2013sp1-installationupgrade/

       6. Download the Exchange 2013 from the below link which is an Exchange 2013 setup with Cumulative update

http://www.microsoft.com/en-us/download/details.aspx?id=38176

       7. Install the Exchange 2013 CU 1 with the help of below link:

https://msexchangeguru.com/2013/04/15/e2013-cu1-2/

 

Configuring Exchange 2013 and network

  1. Transport Configuration
  2. Send connector

         1. Exchange 2013 reads exchange 2010/2007 send connector information. Click on the pencil icon to check and add exchange 2013 in the same send connector.

         2. Click on scoping and + icon to add the server

         

         3. Select the server and add, then click on and save. Send connector configuration completed.

         

     3. Receive Connector

        1. Add a receive connector as per the current connector configuration.

        2. Select the 2013 server, oh what we have 5 connectors for what. Let me explain here.

         3. You can see all 5 together here as I have CAS and Mailbox on same server. First 3 are for the CAS connector and remain 2 are for mailbox role.

         4. I would link to explain the transport pipe line here which consists of the following services:

             Front End Transport service – This service runs on all Client Access servers and acts as a stateless proxy for all inbound and outbound external SMTP traffic for the Exchange 2013 organization.  The Front End Transport service doesn’t inspect message content, only communicates with the Transport service on a Mailbox server, and doesn’t queue any messages locally.

             Transport service – This service runs on all Mailbox servers and is virtually identical to the Hub Transport server role in previous versions of Exchange. The Transport service handles all SMTP mail flow for the organization, performs message categorization, and performs message content inspection. Unlike previous versions of Exchange, the Transport service never communicates directly with mailbox databases. That task is now handled by the Mailbox Transport service. The Transport service routes messages between the Mailbox Transport service, the Transport service, and the Front End Transport service.

            Mailbox Transport service – This service runs on all Mailbox servers and consists of two separate services: the Mailbox Transport Submission service and Mailbox Transport Delivery service. The Mailbox Transport Delivery service receives SMTP messages from the Transport service on the local Mailbox server or on other Mailbox servers, and connects to the local mailbox database using an Exchange remote procedure call (RPC) to deliver the message. The Mailbox Transport Submission service connects to the local mailbox database using RPC to retrieve messages, and submits the messages over SMTP to the Transport service on the local Mailbox server, or on other Mailbox servers. The Mailbox Transport Submission service has access to the same routing topology information as the Transport service. Like the Front End Transport service, the Mailbox Transport service also doesn’t queue any messages locally.

(from TechNet)

5. Here are the details about the receive connectors

         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.

          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.

         By default we don’t route the outgoing email to CAS. If we have some mailgaurd or compliance requirement on a separate CAS server then we can use it. If we have CAS and mailbox role on the  same server then we don’t need to configure this connector. We can simply disable it.

             

      Client Frontend <server name>   Accepts secure connections, with Transport Layer Security (TLS) applied.

  6. So we have to configure “Default Frontend Servername” connector which is accepting the emails on port 25. Yes this is very important when you have both role on one server then Frontend will be 25 and backend will be 2525

         

         7. You might need to check email address policies, this might needs to re-apply. If we have more than 3000 mailboxes then it is suggest applying from EMS.

         To understand the mailflow we can read the below article: https://msexchangeguru.com/2012/08/09/e2013-mailflow/

 

Exchange 2013 Certificates

Create a new Exchange certificate on Exchange 2013: https://msexchangeguru.com/2013/01/18/e2013-certificate/

Certificates and CAS: Now this is the time when we need to focus on CAS certificate and ensure the CAS 2013 is reachable from internet. We have 2 options:

Use current certificate

For Export and import of the cert Please check here – https://msexchangeguru.com/2013/06/29/import-cert-e2013/

  1. Export the cert from Exchange 2010
  2. Import the cert to Exchange 2013
  3. Configure the external url. This is very simple in exchange 2013. You don’t need to go to every virtual directory property.
  4. Select the wrench mentioned below windows

 

                        

                          5. Then this wizard will open, select the exchange 2013 server and give the external url and save it.


                        6. CAS Authentication will be “Use form-based authentication” on both Exchange 2013 and Exchange 2010/2007.


                       
                              Now you will see every directory got the same External url.
                       

Database availability Group

We would like to configure a DAG for high availability with multiple databases. So we have 2 options.

1. DAG with IP. Check the below link to create a DAG with IP

https://msexchangeguru.com/2013/01/17/e2013-dag/

 

2. DAG without IP – This needs Exchange 2013 SP1 on Windows 2012 R2

Check the below link to create IP less DAG

https://msexchangeguru.com/2014/03/21/e2013sp1-ip-less-dag/

Update Feb 2015: If you have 2 datacenters expanded DAG then now you can configure your FSW in Azure which means your DAG can be configurable to 3 Data center expanded automated DAG. This will allow you to completely shut down the data center without loosing production connectivity. Here is the link to configure FSW in Azure – Using a Microsoft Azure VM as a DAG witness server

 

Move Arbitration and Discovery Search mailboxes

Follow the below steps to move all arbitration and discovery search mailboxes to final 2013 database.

Open EMS with run as administrator and run the following cmds

Get‐Mailbox –Arbitration | New‐MoveRequest –TargetDatabase TargetDBName

Get-Mailbox “*Discovery*” | New‐MoveRequest  –TargetDatabase TargetDBName

 

Unified Messaging: Upgrade Exchange 2010 UM to Exchange 2013 UM

This is the optional step only for unified messaging configured organizations.

Please follow the below link to upgrade exchange 2010 UM to Exchange 2013 UM

http://technet.microsoft.com/en-us/library/dn169226(v=exchg.150).aspx

 

Configure Enabled Outlook Anywhere

For Exchange 2007
Set-OutlookAnywhere -Identity “2010 CasServerNameRpc (Default Web Site)” -ClientAuthenticationMethod Basic -SSLOffloading $False -ExternalHostName mail.domain.com -IISAuthenticationMethods {NTLM,Basic}

For Exchange 2010
Set-OutlookAnywhere -Identity “2010 CasServerNameRpc (Default Web Site)” -ClientAuthenticationMethod Basic -SSLOffloading $False -ExternalHostName mail.domain.com -IISAuthenticationMethods NTLM, Basic

 

Configure OAB

Run the below command to configure OAB for all databases

Get-MailboxDatabase | Set-MailboxDatabase -OfflineAddressBook “Default Offline Address List (Ex2013)”

Default Offline Address List (Ex2013) can be replaced by your custom named OAB.

Enabling and Configuring Outlook Anywhere

For Exchange 2007
Get-ExchangeServer | Where {($_.AdminDisplayVersion -Like “Version 8*”) -And ($_.ServerRole -Like “*ClientAccess*”)} | Get-ClientAccessServer | Where {$_.OutlookAnywhereEnabled -Eq $False} | Enable-OutlookAnywhere -ClientAuthenticationMethod Basic -SSLOffloading $False -ExternalHostName mail.domain.com -IISAuthenticationMethods NTLM, Basic

For Exchange 2010
Get-ExchangeServer | Where {($_.AdminDisplayVersion -Like “Version 14*”) -And ($_.ServerRole -Like “*ClientAccess*”)} | Get-ClientAccessServer | Where {$_.OutlookAnywhereEnabled -Eq $False} | Enable-OutlookAnywhere -ClientAuthenticationMethod Basic -SSLOffloading $False -ExternalHostName mail.domain.com -IISAuthenticationMethods NTLM, Basic

 

SCP – Service Connection Point Configuration:

Run the below command to configure SCP on Exchange Management Shell of 2007/2010/2013 separately:

get-ClientAccessServer | Set-ClientAccessServer -AutoDiscoverServiceInternalUri https://autodiscover.domainname/autodiscover/autodiscover.xml

SCP might be already configured on 2007/2010 server so you can also check it and use the same -AutoDiscoverServiceInternalUri. Run the below cmd to get current SCP on 2013 Shell
get-ClientAccessServer | fl name,AutoDiscoverServiceInternalUri

 

RemoteDomain:

Run the below cmd in EMS to allow auto forwarding, oof, auto reply and disable the possibility of winmail.dat from domino server.

Set-remoteDomain -AutoReplyEnabled $True -AutoForwardEnabled $True -TNEFEnabled $False -AllowedOOFType External 

Pop/IMAP: 

If you have pop3/imap4 users then you might like to configure 2013 for some addition configuration.

1. Configure the Basic authentication on EAC for CAS 2013

2. Start the services and change them to automatic.

 

Email address policy:

You might need this step if you organization was initially created on Exchange 2003.

1. Create a new email address policy if there is only one “Default Policy”.

2. Change the attributes of existing email address policy by running the below cmd
Get-emailaddresspolicy | Set-EmailAddressPolicy -RecipientFilter “Alias -ne $null” -IncludedRecipients AllRecipients

3. If you see the below error for the default policy then Remove “Default Policy” which was created in 2003 and will be in ready only mode in Exchange 2013.

emailaddresspolicy error

 

Clean up health mailboxes:

When you remove default mailbox database, it does not remove health mailboxes which we can check by running the cmd and below warning will come. Health mailboxes are for the health service and they are specific for every database so we don’t need to move them rather we need to remove them.

                         Get-mailbox –monitoring

Mailboxes/HealthMailbox94863fe5394447619ec45c4e6b2dd971 has been corrupted, and it’s in an inconsistent state.

The following validation errors happened: WARNING: Database is mandatory on UserMailbox.

 

To fix this we need to delete user account in dsa.msc at yourdomain/Microsoft Exchange System Objects/Monitoring Mailboxes

 

Important: At the point configure your outlook for Exchange 2007/2010 mailbox and 2013 mailbox. If both are working from Internet then move to the next step.

 

CutOver :Updated 2007 part Feb 2015

Now it is the time to do cutover means point the connections to Exchange 2013. It can be done in few simple steps.

1. Create or change Public and Private DNS pointers.

a. autodiscover.domain.com will be pointing to the CAS 2010/2007 or Load balancer of CAS 2010/2007. So change the IP from  Exchange  2010/2007 to 2013. In case of new installation or exchange 2007 environment we need to create new host record in DNS. This will be done on both internal and external

b. mail.domain.com (OWA/activesync/RPCoverhttp/mapioverhttp) Change the IP from Exchange 2010/2007 to Exchange 2013 CAS servers or Load balancer.

c. Create Legacy.domain.com host record in case of exchange 2007 co-existence in both public and private DNS. This will point to Exchange 2007 CAS servers or  Exchange 2007 l0ad balancer CAS VIP.

2. Point your Spam Guard to forward all the emails to exchange 2013 to receive incoming mail via Exchange 2013.

3. Configure Spam Guard to accept emails from all Exchange 2013 Mailbox servers.

4. Configure all other application to send email to the Exchange 2013 Mailbox Servers.

5. Update PTR and SPF record if Exchange 2013 are sending the emails out directly.

6. In case of Exchange 2007, we need to update the following URLs and Authentications as well.

  • EWS – Run the below cmd on Exchange 2007 EMS

Get-WebServicesVirtualDirectory | Set-WebServicesVirtualDirectory -ExternalUrl https://legacy.Domain.com/EWS/Exchange.asmx -internalurl https://legacy.Domain.com/EWS/Exchange.asmx

  • OWA – Run the below cmd on Exchange 2007 EMS

Get-OWAVirtualDirectory | Set-OWAVirtualDirectory -ExternalUrl https://legacy.Domain.com/OWA -internalurl https://legacy.Domain.com/OWA

  •  OWA – Run the below command to change the authentication method in Exchange 2007 EMS

Get-owaVirtualDirectory -identity “CASName1OWA (Default web site)” | Set-OwaVirtualDirectory -ExternalAuthenticationMethods FBA,basic

 

Exchange 2013 Mailbox Migration

So what are we waiting for… Let us begin the mailbox migration.

  1. Now you can run the following cmdlet to move bulk or single mailbox

Get-Mailbox –Database “Exchange 2010/2007/2007 Database” –OrganizationUnit “DN of the OU” | New-Move Request –TargetDatabase “Exchange 2013 Database”

    2. You can monitor the migration by running the following cmdlet or going to the migration tab in EAC:

       Get-MoveRequest


    3. Once completed it will show the below window


For Cross forest mailbox migration check this link: https://msexchangeguru.com/2013/11/02/e2013crossforestmigration/

Public Folder Migration

  1. Once we complete all mailbox migration then we can start the Public Folders migration.

    For Public Folder migration use the below Link:

    https://msexchangeguru.com/2013/04/18/exchange2013-public-folders/

  2. Test everything working and shutdown Exchange 2010/2007 server for 1 production week and observe if no issue reported then go ahead with the Exchange 2010/2007 removal process.

 

Known Issues:

Active Sync Config without Domain Name: https://msexchangeguru.com/2013/08/06/e2013mobiledomain/

OWA redirection broken page and SSL: http://www.expta.com/2013/05/owa-2013-cu1-redirection-is-broken-for.html – This was fixed in CU3

If you have pop/imap user go for CU2: https://msexchangeguru.com/2013/08/04/e2013popimapauth/

Mailflow misconfiguration: https://msexchangeguru.com/2013/08/03/e2013-2010mailflowissue/

Certifacate and cryptographic provider Issue: http://msitpros.com/?p=1770

 

Legacy Removal

  1. Now we are in a position to remove exchange 2010. We can follow the below link for the exchange 2010/2007 removal.

    https://msexchangeguru.com/2013/09/01/e20102007decomposte2013mig/

Hit us with questions

Prabhat Nigam | MVP Exchange

Team @MSExchangeGuru

Keywords: Exchange 2010 to exchange 2013 migration, how to migrate to Exchange 2013

867 Responses to “Exchange 2010/2007 to 2013 Migration and Co-existence Guide”

  1. Felix Kondon Says:

    Hi PN:
    No I can’t see this user on the moverequest display list

  2. Felix Kondon Says:

    Hi Prabhat,

    Some users when I migrated them, result as “completed with error” and details as “this mailbox has a completed moverequest associated with it, before you create a new moverequest, run the remove moverequest command to clear the completed moverequest”
    After i reove remove the initial moverequest, and then do a moverequest, it comes up with the first issue i have mentioned above, ie
    Completed successfully;
    synced mailboxes:0
    finalized mailboxes:0
    failed mailboxes:0

  3. Felix Kondon Says:

    Hi PN:
    Please ignore above.

  4. Felix Kondon Says:

    Hi PN:
    I have moved a mailbox for a user successfully and after this his outlook is disconnected. Please how can i fix this issue?

    thanks, Felix

  5. Felix Kondon Says:

    Hi Prabhat,

    I need your tips, I have tried some tips but still no luck, please let me know.
    issue: I have moved a mailbox for a user successfully and after this his outlook is disconnected. Please how can i fix this issue?

    regards, Felix

  6. Felix Kondon Says:

    Hi Prabhat,

    I have a outlook 2010 client having disconnected from exchange 2010 server, ie keeps prompting for outlook password (same as the domain credentials) and even he enters his correct password, it keeps prompting (even after resetting the password). What I did was created another outlook profile under control panel, mail and then restart the outlook and now it can get connected to the exchange server, but the issue is, the user’s emails in inbox and folders on his initial profile are not updated (synchronized) with this new profile. When we connect using the initial profile, the mails and the folders are all there but are not updated in his new profile here. His outlook is cached.

    Any workaround or fix to this issue please.

    appreciate, thanks -felix.

  7. David Susemiehl Says:

    We are migrating from 2010 to 2013, at the same time we are building a new forest to make up for some of the issues left over from previous administrators. I have already built the 2013 Exchange environment and configured the cross forest mail. My problem is synchronizing the GAL during the coexistence phase (probably 6 months) I think FIM is the way to go but we are only a 1000 user organization. What is the best way to go? Do you have any links 🙂

    Thanks, Dave

  8. Prabhat Nigam Says:

    @Dave
    For over 1000 mailboxes 6 months time is too long, we should be able to finish them within a week unless migration is over the WAN. Use the cross Forest migration blog here. https://msexchangeguru.com/2013/11/03/e2013crossforestmigration/

    Yes, FIM is the best for GAL sync. I have not written any blog on FIM yet. Try this blog but test in your lab 1st.
    http://setspn.blogspot.com/2010/05/fim-gal-sync-my-first-steps.html

  9. Felix Kondon Says:

    Hi PN;

    You know why this error is happening?
    us-smtp-1.mimecast.com rejected your message to the following e-mail addresses:

    rgds, Felix,

  10. Prabhat Nigam Says:

    @Felix
    Share the full NDR.

    If you will share your issues here then you will get more replies (not just me) and faster as well. http://social.technet.microsoft.com/Forums/office/en-US/home?category=exchangeserver&filter=alltypes&sort=lastpostdesc

  11. Felix Kondon Says:

    Hi PN:

    Just today, users getting two different errors (email bounce back) when sending out mails:

    1st. ns30.small-dns.com rejected your message to the following e-mail addresses:joeblow@xxx.com
    Service unavailable; Client host [exchange server name] blocked using Barracuda Reputation

    2nd. mx7.domain rejected your message to the following email addresses:

    peterjoe@domain (peterjoe@domain)

    mx7.domain gave this error:
    Domain/IP address is blocked by the reputation server.

  12. Prabhat Nigam Says:

    @Felix,
    Your outgoing IP is blocked or blacklisted. Check the IP black listing at mxtoolbox.com, if it is not black listed then ask receiving domain’s system admin to add your IP in safe sender list. Else remove IP from black listing.

  13. Felix Kondon Says:

    Hi PN: What do I do if it is blacklisted?

    thanks, felix

  14. Prabhat Nigam Says:

    Contact blacklisted domain and request to remove from blacklist. Some of the website has link on their website.

  15. Felix Kondon Says:

    thanks PN:

    Just a question:
    1.Using this command “BadItemLimit XXX” in a moverequest, what does it actually do, ie Does it leave those bad mails behind or does it allow those bad mails to move across?
    2. If those bad mails are left behind during the move, what happens to them, are they still in initial database incase I might need them later??

    thanks, felix

  16. Prabhat Nigam Says:

    1. Yes bad items will stay in old mailbox.
    2. Yes, Until the mailbox cleanup run.

  17. Felix Kondon Says:

    thanks PN!

  18. Felix Kondon Says:

    Hi PN:

    477: I have moved some mailboxes over to 2013 and they were under “Disconnected mailbox” folder in 2010 for the last 2-3 weeks after the move, but they are no longer there now. I think retention period is set less the 2-3 weeks or so. But how can i retrieve so i can connect back?

    thanks -felix

  19. Henri Feinberg Says:

    Hi again,

    we moved most of the mailboxes from E2010 to E2013 without a problem except:
    1. the discovery mailbox had a corrupted tag on it
    2. Some Outlook users complained that they cannot see their old Outlook Tasks and even when creating a new task it does not show, on the E2010 everything was Okay.

    Any insight regarding these two issue will be very welcome.
    Thanks again.

    Henri.

  20. Prabhat Nigam Says:

    1. You are supposed to migrate old discovery mailbox. If you didn’t then New-mailbox -discovery will create new discovery mailbox.
    2. Not sure about tasks at this moment. Share the error and I will check.

  21. Henri Feinberg Says:

    Thank for a quick replay.
    Indeed the first move to E2013 was the Discovery mailbox, so when the move was over that when I sow that it was under curropted tag.

    As for the taks, no errors showing up only empty entries.

    Thanks,
    Henri

  22. Prabhat Nigam Says:

    Create new discovery mailbox. This mailbox comes into play when you have implemented litigation hold and need to investigate any mailbox.

  23. Lee Says:

    Would appreciate some help on 2010 > 2013 PF migration if anyone out there is feeling charitable. so far i have exported all the PF info but i am having difficulties creating the new PF mailbox with -holdformigration. I get an AD error {Access Denied and insufficient rights} I have checked over the inherit permissions using ADSI edit and re ran domain prep.

    Any Ideas would be great.

    Thanks

  24. Prabhat Nigam Says:

    @Lee
    Read the blog carefully. you have missed the PF migration blog under the topic “Before you proceed with the actual migration steps, these articles may be of interest to you:”

    Go to the PF migration blog and tell us you are stuck on which step. Also comment on PF migration blog.

  25. Lee Says:

    Hi Prabhat
    firstly thanks for your reply.

    I am stuck on the PF migration process.
    https://msexchangeguru.com/2013/04/18/exchange2013-public-folders/

    Step 5 create the public folder mailbox. I seem to get some AD permissions/insufficient rights – access denied error, although I can create a “normal” mailbox.

  26. Prabhat Nigam Says:

    Please post your issue below the PF migration blog.

  27. SaurabhGautam Says:

    Hi, Thanks Prabhat, Such a nice article and only place where you find all coexistence activities under one link. One question, It is clear that within same AD site CAS 2010 and 2013 can have same URLs configured. if AD site of Exchange 2010 CAS and Exchange 2013 CAS is different and we promote Exchange 2013 CAS as internet facing then can the same URL be used in both CAS or we need different URLs for CAS2010 ? CAS 2010 is removed from internet facing. Thanks.

  28. Prabhat Nigam Says:

    Hi Saurabh,

    Good one, you found me here. Thank you.

    Did you go through the links Tushar shared on Facebook Exchange 2013 group. The link explain the working of exchange cas.
    No need of different urls. You can configure same url.

  29. Heni Feinberg Says:

    Hi Prabhat again,

    when I run the .\PublicFolderToMailboxMapGenerator.ps1 5000MB I get 2 mailboxes ‘Malbox1’and ‘Mailbox2’ as oppose to one ‘Mailbox1’ with a value of 20000MB for a single mailbox.
    We have a total of 10MB PF and I need room for expansion so if I specify 5GB it will create TWO mailboxes of a size of 5GB each total 10GB which is too small. Note that I cannot specify a smaller value that the largest public folder which is 2GB. But if I specify 2GB I get 5 Mailboxes entries with 2GB each, again a total of 10GB.

    What option will be the best?

    Thanks again Prabhat

  30. Prabhat Nigam Says:

    @Heni

    I am answering on the PF migration blog.

  31. Andy Says:

    Hi,

    A very good step by step guide – I have been working on this “mini” project of Exchange 2007 to Exchange 2013 migration since beginning of July. I am stuck on getting outlook to recognise a users mailbox has been moved to 2013. I have checked certificates and autodiscover – all appears to be ok. Any pointers you can offer to troubleshoot this. Also I cannot send/receive from a migrated mailbox – although I have added the send and receive connectors on the new 2013 setup so the two problems may well be related….

    Thanks

    Andy

  32. Felix Kondon Says:

    Hi PN,

    I have a user complaining of his emails for Jan-June missing in his inbox. This period he was away from work and when he returned to work, he realized that this period’s mails were missing. I have checked his PC for any pst, ost, or even archive files but were not.

    He confirmed he did not delete his of his mail.

    Any idea how i can retrieve his mails?

    thanks -felix

  33. Prabhat Nigam Says:

    Check the retention policy and users mailbox size which might be full. Who gets 6 months vacation. mostly during the time company disable the mailbox.

    Option 1 you have is to check what you have in the recover deleted items folder in outlook.

    Option 2 if you have enabled litigation hold then we can do a search which is only in Exchange 2010 and 2013.

    Option 3 restore the backup for every month and extract his mailbox.

  34. Felix Kondon Says:

    Thanks PN for your response.I go through the options and see.

    thanks, felix

  35. JoBlack Says:

    Install prerequisite and roles
    Install Exchange 2013
    Configure send connectors
    Migrate mailboxes

    Hi Prabhat, I am happy i stumbled across your site. Awesome by the way. I am about to install 2013 myself i a coexistence setup with exchange 2007. My problem is finding the correct steps to complete without messing the existing users. I was wondering if you by any chance have a quick list of steps (in the recommended order of completion). i.e.

    Install Prerequisites and roles
    Install Exchange 2013
    Configure send connector (or not)
    Migrate mailboxes
    Migrate PFs
    Setup the virtual director for OWA and routing to the new exchange
    Migrate certificate
    Configure DNS
    Cleanup
    Decomission Exchange

    I was hoping to find a way to set the 2013 as the front end right a way, then take my time migrating mailboxes across with out issues. Greatly appreciated.

  36. Prabhat Nigam Says:

    Just follow the blog.

  37. computer monitor Says:

    Very good write-up. I definitely appreciate this website.
    Stick with it!

  38. roy Says:

    prabhat I have a kidn of complicated scenario.

    I have a cross forest 2003 to 2007/10 environment. we are not fully off the 03 as some mailboxes still sit there but that’s in a different AD forest/domain. we stood up a new domain/forest and I installed 07 then upgrade 2010 but still have 1 2007 server running for migrating users over from 2003 over.

    im trying to do the following now.
    i currently have exchange 2010 sp3 setup as follows

    2 cas/ht using windows nlb for array.internal.com as the nlb name

    2 mailbox servers using 1 dag for replication between them.

    I would like to stand up 2 new CAS 2013 sp1 servers(2012 r2) and use our netscaler hlb to load balance and do ssl offloading.
    id like to use the hlb to load balance and ssl offload all possible traffic not just owa, i.e. activesync etc.
    the netscaler is running version 10.5.

    id like to make this as seamless as possible for the user, so no owa name change or anything like that.

    any ideas?

  39. Prabhat Nigam Says:

    1. You need to remove exchange 2003 else you can’t install exchange 2013.
    2. You need to remove exchange 2007 else we need to configure 2 URLs for owa which does not proxy.

    3. If we are just left with 2010 then everything always go seem less. I have done many migration like this.

  40. Almir Says:

    Hello Prabhat,

    first of all I would thank you for your excelent article.
    I have one question for cross forest OWA coexistence.
    I have the old-org.com and the new-org.com. Moving users works fine. There is a AD trust, certificates are fine.
    In the Coexistence Phase the IP point now to the neworg.com CAS Exchange 2013 and he should route/proxy the neworg.com User to Exchange 2013 and oldorg.com to Exchange 2010.
    In migration environments in the same forest this works automaticaly but how can i configure it in this cross forest case?

  41. roy Says:

    i need to remove 2003 even though its a completely different exchange forest?
    also do you have any guides or ideas as to how to migrate the 2010cas array to a 2013 netscaler Load balance solution?

  42. Prabhat Nigam Says:

    @Roy
    If 2003 is in different forest then you don’t need to remove it but you will not be able to migrate anything to 2013 once you install 2013 in the 2nd forest.

    Load balancer is different than CASArray. Load balancer has a many configurations depending on your infra. We can configure the LB but a Product guide will be better.

  43. Prabhat Nigam Says:

    @Almir
    You need to use 2 different URLs one for each forest.

  44. Amit kumar Says:

    Hi Prabhat,

    We have Exchange 2010 running currently, We are planning to Migrate Exchange to 2013 Sp1 on Windows 2012 OS.

    Below is the requirement
    1. We want to use current OWA (mail.domain.com) URL to Exchange 2013 server. Please do let me know how to achieve this, Can i use exisiting certificate 2010 Certificate on Exchange 2013 ? If yes, then what are all things i need to consider.

    An early reply would be appreciated !!
    Thanks,
    Amit kumar

  45. Prabhat Nigam Says:

    @Amit
    Yes, you can use same url and cert with 2013
    It is simple. Install, configure and do the cut over. Basically follow this guide

    Exchange 2013 proxy to exchange 2010 and does not need the different owa url.

  46. Amit kumar Says:

    Thanks Prabhat for quick clarification…. Still i am missing something or i am bit confused on steps … !!

    I have around 26000 Mailboxes that need to migrate from Exchange 2010 to Exchange 2013. As i stated earlier, I want to use Exchange 2010 URL (mail.xyz.com) to Exchange 2013… As users cannot migrate it one go hence, migration would take 1 to 2 months of time…. By the time, i want User of 2010 & 2013 can access OWA url (mail.xyz.com).

    For this what settings i need to do on Exchange 2010 & 2013 server….. I can use same certificate ??

    Thanks,

    Amit kumar

  47. Prabhat Nigam Says:

    Hi Amit,

    I have already answered your concern. If you are not confident then I would recommend to hire some consultant like me to design the migration which is 4-8 weeks works depends on the scope.

    Make sure support client versions are already deployed and you count PF migration time. There will not be PF replication in Exchange 2013.

    Let me know if there is a need for a consultant otherwise this blog is a complete migration guide. You can write to my email id prabhat@MSExchangeGuru.com

  48. Raman Says:

    Hi Prabhat,

    I am moving Exchange 2010 mailboxes to Exchange 2013 SP1 in production. When I move 2010 mailbox Outlook, OWA works fine but ActiveSync (HTTPProxy log shows on CAS 2013 server that it is still re-directing it to Exchange 2010 CAS servers). Sometimes ActiveSync starts working with in few minutes and sometimes it takes hours before it starts to see that mailbox is moved to Exchange 2013. I am certain it is not ActiveDirectory replication since all other clients are working.
    Is there anything I can do right after the move to make it quick,
    Thanks,
    Raman

  49. Felix Kondon Says:

    Hi PN:

    How can a deploy a standardized signature to all users in the organization from the exchange 2013 management console.

    thanks, felix

  50. Raman Says:

    Hi,
    I would really appreciate if someone provide explanation on “RPCCLientAccessServer” property under Get-MailboxDatabase . Why is it even there? Since, Exchange 2013 does not use RPC. I am not seeing any issues but I am wondering we are running Exchange 2010 and Exchange 2013 co-existence environment.
    Thanks
    Raman

Leave a Reply

Categories

Archives

MSExchangeGuru.com