Migrating AD Exchange 2013 Objects to a new AD Domain

I have a client 'new company' (NC) who is splitting from the 'parent company' (PC). They are using a 3rd party tool to conduct the AD migration/split.
The PC AD domain is on Windows 2012 Servers and has trust relationship with the NC AD domain also running on windows 2012 server. The users and computers have been successfully migrated/stubbed to the NC domain, however, the Exchange 2013 objects
are not migrating over to the NC AD domain using the 3rd party AD migration tool.
Question, does any one have suggestions on how to migrate the exchange 2013 objects from the PC AD to the NC AD ?
What techniques can be used ?
Thanks in advance
RK

What 3rd party tool are you using and have you contacted their support already? You can use the native tools to migrate mailboxes (I do all the time) but I wouldn't try and mix the native tools and a 3rd party tool on the same migration unless I was sure
what the end result would be.

Similar Messages

Mailboxes migrated to Exchange 2013 - some Outlook profiles do not auto-update

** EDIT WITH SIMPLIFIED QUESTION:
Should I be able to manually create a profile in my Exchange 2013 environment without knowing the
GUID@DOMAIN server name? When I specify the Ex2010 server name and Outlook Anywhere settings, the server name does not auto-resolve to the GUID as other threads suggest. I am curious whether others are able to manually
create a profile without knowing the GUID@domain.
Hi all,
Our computers have Outlook configured to automatically configure a profile without any intervention. The profile is pointing to Exchange 2010, which is still running in our environment with Exchange 2013. When a user logs into a computer and
launches Outlook for the first time, Outlook fails to connect and a "Cannot open your default-email folders" error occurs.
I have verified that the Outlook Anywhere settings are configured correctly.
If I delete the profile and create a new one using Autodiscover, everything works fine.
Occurs on all clients - 2007, 2010, 2013, fully patched).
To troubleshoot, I attempted to manually create a new profile. I supplied the Exchange 2010 server name, and configured Outlook Anywhere. When hitting "Check Name", the server name stays to Exchange 2010 (does not switch to
[email protected]). When I launch Outlook, the connection fails. Again, an autodiscovery succeeds.
From my reading, it appears that Outlook should be updating the profile with the new GUID server name when it attempts to connect. The RPCClientAccessServer setting on the Exchange 2013 databases points to the Exchange 2010 CAS Array names.
Any ideas?
Thanks for your hel

Thanks for the reply .
AutodiscoverInternalURI is pointing to the Exchange 2013 environment, and is working fine when auto creating the profile. The Test Autodiscover function returns the correct URL for the mailboxes. The problem comes when manually creating
a profile. Other threads indicate that a manually created profile should auto change the server name when the Check Name option is selected, but mine remains with the Ex2010 cas name listed on the database, and the creation fails.
However, if the user had previously connected to Ex2010 prior to the mailbox move, the profile successfully changes to Ex2013. Only during manual creation does it fail, which is a problem because our existing PCs are configured to create
profiles without autodiscover.

Outlook 2007 on Terminal Server cannot manage Public Folder Favorites after Migration to Exchange 2013

Hi,
we are running a Server 2008 R2 as a Terminal Server with Outlook 2007 SP3 (incl Nov 2012 Update 12.0.6665.5000) which is known as fully supported with Exchange 2013.
With Exchange Server 2007 we did not have any issues. But after having successfully migrated to Exchange 2013 we cannot manage our public folders favorites from these clients anymore.
As we are running Outlook 2007 on a WTS we can not use Exchange Cache Mode and so we can also not download Public-Folders-Favorites as an option. Whenever we try to delete existing favorites or when we try to delete public folders with content or subfolders
there will be an error msg that says that it cannot be deleted and that there may be no sufficient permissions. But this IS NOT the issue NOR the solution as I have full admin rights and am owner of the public folders.
On single fat clients with Outlook 2007 with Exchange Cache Mode enabled we can manage the favorites and the public folders without problem.
We need to be able to manage the favorites of all users (circa 50-60 users) from the WTS with Outlookm 2007. I have no more ideas right now. Does anyone know how to get this settled?
Thanks, Paula

Hi,
Based on the description, users could access public folders successfully, but when they tried to manage public folder favorites or wanted to remove specified folders, they got error message of no sufficient permissions.
Is it right?
You mentioned on single fat clients with Outlook 2007 with Exchange Cache Mode enabled, user can operate normally. Is this a WTS with Outlook 2007 installed?
If possible, please switch this Outlook client from cached mode to online mode to check result.
Best regards,
Belinda Ma
TechNet Community Support

Cutover Migration to Exchange 2013 On-premises

I have two clients who will be merging their on-prem Exchange
organizations. Different forests. I've done many cutover migrations to
Office 365 for other clients so I'm familiar with the process. My
question is: Is it possible to do an O365-style cutover migration (create migration endpoint, cutover batch, etc.) from
an on-prem Exchange 2010 server to an on-prem Exchange 2013 server using
the same steps?
Thanks in advance for any input.
Steve

Hi,
Based on my knowledge, the Cutover Migration is used for migration to Exchange online. There is no related document about
Cutover Migration from Exchange 2010 to Exchange 2013.
To perform Exchange 2010 corss-forest migration to Exchange 2013, you need to use Active Directory Migration Tool (ADMT) migrate user accounts.
Here is a related blog which may help you. (Even though this article is for Exchange 2010 corss-forest migration, it's also applies to cross-forest migration from Exchange 2010 to Exchange 2013.)
http://blogs.technet.com/b/meamcs/archive/2011/06/10/exchange-2010-cross-forest-migration-step-by-step-guide-part-i.aspx
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support

After migration to Exchange 2013 the old outlook clients do not automatically reconfigure

After migration to Exchange 2013 the old outlook clients do not automatically reconfigure
we use outlook 2013

Hi ,
I hope you would be having exchange 2013 coexistence environment with exchange 2010 or 2007.
Autodiscover is the feature which will make the outlook profiles to configure automatically.So please make sure the following things are in place.
1.Autodiscover record on the internal dns need to be configured and it has to be resolved properly to the cas servers or else to the LB if you have.
2.Please check the autodiscover internal url.
get-clientaccessserver -identity "server name" | fl *internaluri*
3.Make sure the name used for the autodisocver and internal outlook anywhere are available on the SAN certificate installed in exchange.Same time we need to enable the installed SAN certificate for the exchange services like iis,pop,imap,smtp.
4.You need to have the autodicover name and internal outlook anywhere name on the internet explorer proxy exceptions when you have proxy servers available on your network for internet access.
Note : moreover we need an additional information's from your side about your environment.
Thanks & Regards S.Nithyanandham

Exchange 2013 / 2010 coexistence with different public domains

Currently in my organization
1x Exchange 2010 Standard w/SP3 - Client Access / Hub Transport
1x Exchange 2010 Standard w/SP3 - Unified Messaging Server (we also have Lync 2013 in the environment)
1x Exchange 2010 Standard w/SP3 - Mailbox
In my organization, we have approximately 600 mailboxes - 100 office staff, and 500 field employees using a mixture of Outlook 2007/2010/2013 and various mobile devices. Most of our field employees are in remote locations, several hundred
miles away. We have no IT staff in any of our field locations.
We also have two public domains that we use, though we are trying to phase out the old one to unify everything.
domain-old.com - Used when the company had a different name. All Exchange services are published with this one.
domain-new.com - Used after the company changed names. The goal is to publish all Exchange services with this one.
domain.local - Our internal Active Directory domain.
We use Microsoft Exchange Online Protection for all inbound/outbound email. We publish OWA, ActiveSync, etc. through our Sophos firewall. Also, we have two KEMP LoadMaster appliances that for high availability that we currently use for Lync 2013; they are
severely underutilized.
Goals for the Exchange migration
My primary goal is to introduce high availability into our environment by introducing redundancy on multiple levels. I would like to accomplish this by utilizing Exchange 2013 since we will need to purchase additional licensing anyway. My idea of the
final topology is:
2x KEMP LoadMaster appliances providing reverse proxy and load balancing to the CAS servers
2x Physical servers running Hyper-V, separated physically but in the same AD site. Each one would run:
1x VM with Exchange 2013 Standard w/SP1 - Client Access
1x VM with Exchange 2013 Enterprise w/SP1 - Mailbox - Utilizing DAGs for high-availability
I'd like all the new Exchange services to be published under the domain-new.com domain - such as mail.domain-new.com, mail.domain-new.com/owa, smtp.domain-new.com, etc.
We have purchased two new physical servers that will be Hyper-V hosts running Server 2012R2. My timeframe to start this project is within the next two weeks, so I'll be running the new Exchange 2013 VMs under Server 2012, not R2 as it won't be supported
until Exchange 2013 SP3 is released.
Deployment Plan
Install Exchange 2013 on new VMs.
Create CAS Array object.
Configure Exchange 2013 to publish under the new namespace.
Perform mailbox moves to 2013 for a small group (1-5 users) at a time. Recreate Outlook profiles and mobile device profiles for that group. Test and move to the next group.
Once all users are moved to the new namespace, decommission the Exchange 2010 servers.
Unknowns
My primary unknown is about the namespaces. All of the guides I have read strictly deal with keeping the existing namespace and having the Exchange 2013 CAS proxy requests to Exchange 2010 for mailboxes still on 2010. This should never be an issue for us
since we'll be using the new domain for each mailbox we move.
My question boils down to, is this a supported way to migrate to Exchange 2013? And if so, are there some materials or information to help me perform it this way?

Hi,
From the description, you want to install Exchange 2013 in another domain and then migrate from Exchange 2010 to Exchange 2013.
About DAG, all servers in a DAG must be running the same operating system. If there is only one mailbox server, there is no need to deploy DAG.
About CAS array, we should know that the CAS Array no longer exists in Exchange 2013.
About the namespace, based on my knowledge, we can introduce a new namespace. Just as what you said "This should never be an issue for us since we'll be using the new domain for each mailbox we move".
Here are some articles about how to upgrade from Exchange 2010 to Exchange 2013 in the same organization.
Checklist: Upgrade from Exchange 2010
Install Exchange 2013 in an Existing Exchange 2010 Organization
Upgrade from Exchange 2010 to Exchange 2013
Hope this helps.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Exchange 2007 migrate to Exchange 2013

Dear MS Support,
I did migrate Exchange 2007 to Exchange 2013
The install complete, the exchange 2007 and 2013 can work together successful
DAG has created and work fine
Below is capture on exchange group after migrate
The exchange 2007 work fine with outlook anywhere, all the users can connected and send and receive mail in 5 year
The cerificate enroll with
Alternative Names: mail.biendongpoc.vn
The autodiscover on exchange 2007:
[PS] C:\Windows\system32>Get-ClientAccessServer | ft Identity,*uri* -AutoSize
Creating a new session for implicit remoting of "Get-ClientAccessServer" command...
Identity AutoDiscoverServiceInternalUri
BDPOC-SERVER1 https://mail.biendongpoc.vn/Autodiscover/Autodiscover.xml
I have created new certificate for Two exchange 2013
The certificate enroll with
Alternative Names: cas.biendongpoc.vn
I have create cname cas point to dag on DNS server
I have create A record autodiscover.biendongpoc.vn point to IP of dag.biendongpoc.vn
I did migrate mailbox from exchange 2007 to exchange 2013, the migrate successful , the outlook can
connected to Exchange 2013 and working perfectly
Our problem, the account exchange 2007 work not stable ,
sometime it connect to mail.abc.com, sometime it connect to cas.abc.com
If the outlook connect to cas.biendongpoc.vn, the request put password and i can't connect to exchange 2007, if outlook connect to mail.biendongpoc.vn i can connect
It is not stable for current exchange 2007
Anyone who can help me ?
Thanks

Hi
huynhtrongnhatminh,
I suggest you please go through this article.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
Please check this for step by step guide.
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
Please point your autodiscover and commonname to Exchange2013 CAS
Please configure your URLs. There is no CAS array in Exchange2013 but the concept of single name space remains.
You need to have an A record (e.g. legacy.domain.com) in yout external DNS and add that name (legacy.domain.com) in your certificate for exchange 2007 users to have access externally.
Configure your commonname URLs in Exchange2013. Point commonname and autodiscover to exchange2013 in both external and internal DNS servers
Configure URLshttp://www.mustbegeek.com/configure-external-and-internal-url-in-exchange-2013/
No CASARRAY in 2013http://exchangeserverpro.com/exchange-2013-client-access-server-high-availability/
Please configure splitdns or pinpoint DNS in your internal DNS server if not configured
http://exchange.sembee.mobi/network/split-dns.asp
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Free/Busy not working after mailbox migration to Exchange 2013

I'm in the process of migrating user mailboxes from Exchange 2007 to Exchange 2013
It seems that many of the users (not all) are having problems seeing free/busy once they have been migrated. If we remove the Outlook profile and recreate it, all is good. Problem is that this is happening to more and more people. Everyone
is on Outlook 2010
Test-OutlookWebServices -ClientAccessServer Ex2013 -identity MyName -MailboxCredential $cred    Results in:
Autodiscover: Outlook Provider Failure
Exchange Web Services          Failure
Availability Service           Skipped
Offline Address Book           Failure
The same if I run that command against the Exchange 2007 server.
What am I doing wrong?

I should have mentioned that. Yes, OWA works perfectly for the affected users. Just as deleting their Outlook profile and recreating a new one does.
Results of Get-WebServicesVirtualDirectory:
Identity    : Exch2007Srvr\EWS (Default Web Site)
InternalUrl : https://legacy.company.com/EWS/Exchange.asmx
ExternalUrl : https://legacy.company.com/EWS/Exchange.asmx
Identity    : Exch2013Srvr\EWS (Default Web Site)
InternalUrl : https://mail.company.com/ews/exchange.asmx
ExternalUrl : https://mail.company.com/ews/exchange.asmx
The URL you reference above is actually the site I used to perform migration.
What's interesting (at least to me) is that on my machine I did not have any issues with seeing calendars. The Test E-mail AutoConfiguration (without Guessmart), I get prompted for my password over and over; however, after clicking on cancel I
get:
Attempting URL
https://mail.company.com/autodiscover/autodisconver.xml found through SCP
Autodiscover to
https://mail.company.com/autodiscover/autodisconver.xml starting
GetLastError=0;httpStatus=401
GetLastError=0;httpStatus=401
GetLastError=0;httpStatus=401
GetLastError=0;httpStatus=401
GetLastError=0;httpStatus=401
Autodiscover to
https://mail.company.com/autodiscover/autodisconver.xml Failed (0x80040413)
Attempting URL
https://autodiscover.company.com/autodiscover/autodisconver.xml found through SCP
Autodiscover to
https://autodiscover.company.com/autodiscover/autodisconver.xml starting
GetLastError=0; httpStatus=200.
Autodiscover to
https://autodiscover.company.com/autodiscover/autodisconver.xml Failed (0x800C8203)
Autodiscover to https://company.local/autodiscover/autodiscover.xml starting
GetLastError=12029; httpStatus=0
Autodiscover to https://company.local/autodiscover/autodisconver.xml Failed (0x80004005)
Autodiscover to
https://autodiscover.company.local/autodiscover/autodisconver.xml starting
GetLastError=0; httpStatus=0
GetLastError=0; httpStatus=200
Autodiscover to
https://autodiscover.company.local/autodiscover/autodisconver.xml Failed (0x800C8203)
Local autodiscover for company.local starting
Local autodiscover for company.local Failed (0x8004010F)
Redirect check to
https://autodiscover.company.local/autodiscover/autodisconver.xml starting
Redirect check to
https://autodiscover.company.local/autodiscover/autodisconver.xml Failed (0x800C820D)
Srv Record lookup for hydraforce.ads starting
Srv Record lookup for hydraforce.ads Failed(0x8004010F)
However, when I did this on a system that cannot see any calendars, it all works perfectly.
Browsing to
https://autodiscover.hydraforce.com/autodiscover/autodiscover.xml does result in Error Code 600

Exchange 2007 migration to Exchange 2013

Hello Exchange experts,
I’m Planning an Exchange migration (EX07 to EX13) and despite to have read many many tutorials and technet opinions, I cannot see the correct path to migrate. I hope someone can help me.
- Actual Infrastructure:
     1 Physical server (SERVER_08): DC + Exchange 2007. IP: 192.168.1.10
- Future Infrastructure:
     1 Physical Server (SERVER_2012R2): DC, GC, FS. IP: 192.168.1.50
    1 Physical Server (EX2013): CAS,Mailbox. IP: 192.168.1.51
My questions come once I’ve prepared the squema and I have to start with the Exchange Migration. As far as I know, I think the steps and infrastructure behavior will flow in this way:
Initial State: Only one Exchange2007 installed and all the clients point to this server, and thus in this moment the value of SCP is the initial Exchange Server SERVER_08.
In SERVER_08 there is one self-certificate with this names: SERVER_08.test.local and SERVER_08 and all the Outlook clients and Windows Phones use this certificate. This works perfectly.
I install a secondary Exchange (EX2013) in a new server but in the same internal domain (test.local).
Once the second Exchange server is installed, the SCP is automactly updated with the new SCP pointing to this Exchange 2013 (EX2013).
      So that the clients don’t give them
a prompt message, the SCP must be changed with PowerShell to point the initial    Exchange Server (SERVER_08). (Right?)
Create a A register (mail.test.local) pointing to the new Exchange 2013 (EX2013 - 192.168.1.51).
        At this point, I understand that the clients can coexist with both Exchange Servers (EX07/EX13) and no one will be prompted with new certificate issues. Right?
Once the Mailbox Databases/Connectors are migrated to the new exchange 2013, I need to modify again through PowerShell the SCP value with the new EX2013
(mail.test.local).
When the clients open again the Outlook client, will be prompted to agree the new Exchange 2013 certificate and
everything will work fine during the next 5 years (Exchange 2013 self-certificate lifetime).
I’ve been reading many tutorials and I want to make sure the steps until coexist both Exchange works fine, and obviously
if the experts can suggest me something.
Thanks in advance
Best Regards
Tecnico Superior de Sistemas

There a few things missing in here like the legacy URL specifics, and Outlook client version requirements (do not overlook Outlook, or it will bite you).
I'm curious about this bit "When the clients open again the Outlook client, will be prompted to agree the new Exchange 2013 certificate and
everything will work fine during the next 5 years (Exchange 2013 self-certificate lifetime). "
You should not be advocating the use of self signed certs, they are not supported for Outlook Anywhere. Even if this is testing, install a Windows CA and use that to issue certs of
get a cheap commercial one.
Training users it is OK to click here to see the dancing pigs never bodes well :)
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.

Cross-forest migration to Exchange 2013 SP1 and Outlook 2013 SP1

Hello! I have two forest: Exchange 2010 SP2 RU5 - resource forest and Exchange 2013 SP1 - account forest. I make cross-forest migration from resource forest (linked mailboxes with account forest) to forest with Exchange 2013 SP1.
I have moved mailbox from resource forest exchange 2010 to exchange 2013 sp1 forest.
Outlook 2010 connect to migrated mailbox without any problem, but outlook 2013 sp1 cannot connect to migrated mailbox.
Error look like - cannot find exchange server.
I created new mailbox in Exchange 2013 organization and can connect to it with outlook 2010 and outlook 2013 sp1.
Someone have the same problem with migrated mailbox? How to solve it?
Truly, Valery Tyurin

You can use New-MoveRequest to perform a cross-forest move. Here is a well post and step-wise explanation you can check for cross forest migration from exchange 2010 to exchange 2013(http://msexchangeguru.com/2013/11/03/e2013crossforestmigration/).
Moreover, you can try this utility (
http://www.exchangemigrationtool.com/ ) to accomplish this task.

Exchange2010 migration to Exchange 2013 federation trust failed (Outlook Provider Failure)

We are in a migration Exchange 2010 to Exchange 2013.
On the 'old' Exchange 2010 we are using a Federation Trust to 2 order company's. The federation trust for mailbox's on the exchange 2013 wont work.
We removed the federation trust on the old exchange 2010 server and create a new federation trust on the new Exchange 2013 server. We also changes the DNS TXT records. Creating the new federation trust without errors. But when the 2 order company's trying
to connect (add our company name for trust) they get a error.
A have trying to run a couple tests on the new Exchange 2013 server and found this error:
[PS] C:\Windows\system32>Test-OutlookWebServices -debug -Identity [email protected] -MailboxCredential(Get-Credential
cmdlet Get-Credential at command pipeline position 1
Supply values for the following parameters:
Credential
Source                              ServiceEndpoint
Scenario                       Result Latency
(MS)
AM111.AM.LAN                        autodiscover.company.nl            Autodiscover: Outlook
Provider Failure     144
AM111.AM.LAN                        webmail.company.nl
Exchange Web Services          Success     134
AM111.AM.LAN                        webmail.company.nl
Availability Service           Success     207
AM111.AM.LAN
Offline Address Book           Skipped       0

Hi,
Are you add primary SMTP domain as a federated domain? If not, please run below command to achieve this function:
Add-FederatedDomain -DomainName contoso.com
Configure federated sharing for the Exchange 2013 organization. Complete the steps in
Configure federated sharing.
Configure federated delegation (previous name for federated sharing) for the Exchange 2010 SP2 organization. Complete the steps in
Configure federated delegation.
Besides, I find an similar thread about Autodiscover service failed within federated trust, for your convenience:
https://social.technet.microsoft.com/Forums/ie/en-US/ea192e0a-1363-4cb6-9fc4-2973f64afc23/the-response-from-the-autodiscover-service-at?forum=exchange2010
Best Regards,
Allen Wang

MS Exchange 2010 Sp3 Ent Migration to Exchange 2013

Hello,
We currently have 2 Exchange 2010 SP3 servers in 1 DAG. Both servers host CAS, Mailbox and Hub Role.
I want to introduce a 3rd Exchange 2013 Server and slowly move users onto a new DAG I build in Exchange 2013.
Can I create a 3rd Exchange 2013 Server with CAS and Mailbox Server Role and make the 3rd Exchange server (2013) a member of the existing (2010) CAS array then slowly perform local move requests for users mailboxes
from my Exchange 2010 DAG to the Exchange 2013 DAG without any disruption to my outlook, OWA and AS clients?
Exchange 2010 (Windows 2008 R2)
Exchange 2013 (Windows 2012 R2 DataCenter)

Hi,
In Exchange 2013, all Outlook connectivity (Internal and External) takes place over Outlook Anywhere(RPC/HTTP). Thus, CAS array which is used internal for RPC/TCP protocol (MAPI) no longer exists in Exchange 2013.
For your coexistence environment and the plan to migrate all mailboxes to Exchange 2013 in the future,
we need to set all virtual directories for CAS 2013 and enable Outlook Anywhere for Exchange 2010. If the mailbox is moved to Exchange 2013, the Outlook client would connect to the server which is set in Outlook Anywhere External host name
and Internal host name instead of CAS array. If all configurations are proper, CAS 2013 would also proxy the service requests for Exchange 2010 users.
Here are some reference about Client Connectivity in an Exchange 2013 Coexistence Environment:
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
Exchange 2013 Client Access Server Role
http://blogs.technet.com/b/exchange/archive/2013/01/25/exchange-2013-client-access-server-role.aspx
Exchange Server 2013 Client Access Server High Availability
http://exchangeserverpro.com/exchange-2013-client-access-server-high-availability/
Exchange 2010/2007 to 2013 Migration and Co-existence Guide
http://msexchangeguru.com/2013/05/10/exchange2013-migration/
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please
make sure that you completely understand the risk before retrieving any suggestions from the above link.
Regards,
Winnie Liang
TechNet Community Support

Exchange 2010 dag migration to exchange 2013 help

If I want to use the Same mailbox servers and upgrade them to exchange 2013, what is the recommended way? I have a 4 member exchange 2010 DAG.
I was thinking (where A,B,C,D are mailbox servers, A,B are in one site and C,D another active directory site):
A B -------------- C D
Remove A and C from the 2010 DAG, Format and install Exchange 2013 on both, and create a 2013 dag :
A1 ----------- C1
B ------------- D
Then move across all mailboxes from B to A1. Upgrade B and D to exchange 2013 and put them in the DAG
A1 B1 ----------- C1 D1
Does this make sense ? I am trying to do this while having as much high availability as possible during the transition. I have no extra servers so I have to use the existing server hardware.
Anand_N

Hi,
When you want to migrate a DAG from Exchange 2010 to Exchange 2013, you should first remove the mailbox server from the DAG in Exchange 2010 and then move mailboxes from database in this mailbox server to Exchange 2013. After all mailboxes have been migrated
to the Exchange 2013 mailbox server, when the new server is ready, it can become a member of the Exchange 2013 DAG.
Here is an article about migration DAG from Exchange 2010 to Exchange 2013 for your reference.
Migrating an Exchange 2010 DAG to Exchange 2013
http://windowsitpro.com/blog/migrating-exchange-2010-dag-exchange-2013
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
sure that you completely understand the risk before retrieving any suggestions from the above link.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Should we migrate to Exchange 2013?

Exchange 2010 SP3, two hubs, two mbs
i'm trying to decide if we should migrate to 2013 Exchange. so far, what I see are mostly cosmetics gains like in OWA, EAC, but it does talk about "site mailboxes". will "site mailboxes" benefit us if we're not using sharepoint?

I wouldn't compare the end-user cosmetic changes but rather focus on service availability that end users are getting... Exchange 2013 has changed drastically with New
managed store process means entirely rewritten information store process in C# with
granular management of resource consumptions, Managed Availability that helps to do internal monitoring to prevent failure and self-healing with various service restoration, Automatic reseed
helps to quickly restore the DB redundancy after disk failure and counting...
Check details here :
What's New in Exchange 2013
Blog |
Get Your Exchange Powershell Tip of the Day from here

Migration to Exchange 2013 from 2010 - Client side issues

Hi Everyone,
I've been having issues with clients connecting to an existing Exchange server (Getting login prompt- but not usual reason).
We currently run Exchange 2010 with approx 200 mailboxes on the server. Last night I renewed the certificate on the 2010 server (go daddy SAN cert, all ok) and added the cert to my new Exchange 2013 server. I tested it with my account, and a
test account approx 12 times, and had not login prompt when launching Outlook. All seemed ok, until this morning.....
This morning, most (not all) users are getting the login prompt. We are able to get by this by inputting domain\username and Outlook opens fine and is able to connect. No users are on the Exchange 2013 server yet (only 1 test account)
I've been googling all morning and I'm not seeing anything directly relating to my issue. I've read about the Anon vs Negotiate issues (KB2834139) - But - the strange thing is all clients are set to negotiate network security (And encrypt data) This
is opposite of what the MS article says. CLients are all Outlook 2010
Here are my outlook anywhere settings:
ServerName : exchange2010
IISAuthenticationMethods : {Basic}
ServerName : exchange2013A
IISAuthenticationMethods : {Basic, Ntlm}
ServerName : exchange2013B
IISAuthenticationMethods : {Basic, Ntlm}
Identity ClientAuthenticationMethod IISAuthenticationMethods
exchange2010\Rpc (Default Web Site) Basic {Basic}
exchange2013a\Rpc (Default Web Site) Ntlm {Basic, Ntlm}
exchange2013b\Rpc (Default Web Site) Ntlm {Basic, Ntlm}
If I change the Exchange 2010 server to NTLM, will this resolve what I'm seeing? And do I need to restart RPC Client Access and Transport Service to make changes take effect? Or reboot the whole server?
If you need more info or logs please let me know
Thank you for any help!
-Jeff

Hi,
Please confirm if the Login prompt issue occurs when users open the Outlook client at first time after renewing Exchange certificate or happens when opening the Outlook every time.
I noticed that the user can connect to Exchange server after inputting domain\username. Please confirm if the issue happens to external users who use Outlook Anywhere. For Outlook Anywhere coexistence,
please choose NTLM for IIS authentication.
Set-OutlookAnywhere -Identity "exchange2010\Rpc (Default Web Site)" -IISAuthenticationMethods Basic,Ntlm
Regards,
Winnie Liang
TechNet Community Support

Migrating AD Exchange 2013 Objects to a new AD Domain

Similar Messages

Maybe you are looking for