Exchange 2010: Virtualized Exchange 2010 Datacenter Migration

We have a virtualized Exchange 2010 production implementation that needs to be relocated to a new datacenter. We will be leveraging SAN based replication and VMWare to cutover.
Some background info:
3 CAS/HUB servers
4 Node DAG across 2 sites (3 production Mailbox servers in the site to be migrated, 1 mailbox server will not move and be left in DR)
Since I need to shutdown 3 mailbox servers in a 4 node DAG, the cluster will go offline and the databases will dismount. I could run a datacenter switchover to preserve service, but I have the OK to take Exchange completely down.
Knowing that:
1) What are the best practices to shutdown and start up all the CAS servers and Mailbox servers (both in prod and DR)?
2) Should I suspend replication or dismount the databases in advance and prevent them from automatically mounting on boot up? Is the StartDagServerMaintenance script relevant in this situation?
Any suggestions on the proper way to go about this is much appreciated. Thanks for reading.

-->1) During the shutdown...would it make sense to turn off the 4th mailbox server in the DAG which is located in our DR site? I'm thinking that leaving the DR mailbox server powered off and powering it up last among the DAG members would prevent
any database copies from being activated in DR.
You already have a planned outage. I suggest you shut down the server in DR and start that after starting
all the 3.
2) To be able to mount a database in a 4 node DAG, I need to have the file share witness and two mailbox servers available first...correct?
Your fileshare witness should be online first otherwise none of your databases will get mounted.
If your DAG contains odd number of members filesharewitness will be ignored, (even number of DAG members will use filesharewitness)http://blog.credera.com/technology-insights/microsoft-solutions/when-do-dags-need-a-file-share-witness/
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.

Similar Messages

Exchange 2010 to Exchange 2013 Migration and Architect a resilient and high availability exchange setup

Hi,
I currently have a single Exchange 2010 Server that has all the roles supporting about 500 users. I plan to upgrade to 2013 and move to a four server HA Exchange setup (a CAS array with 2 Server as CAS servers and one DAG with 2 mailbox Servers). My
goal is to plan out the transition in steps with no downtime. Email is most critical with my company.
Exchange 2010 is running SP3 on a Windows Server 2010 and a Separate Server as archive. In the new setup, rather than having a separate server for archiving, I am just going to put that on a separate partition.
Here is what I have planned so far.
1. Build out four Servers. 2 CAS and 2 Mailbox Servers. Mailbox Servers have 4 partitions each. One for OS. Second for DB. Third for Logs and Fourth for Archives.
2. Prepare AD for exchange 2013.
3. Install Exchange roles. CAS on two servers and mailbox on 2 servers. Add a DAG. Someone had suggested to me to use an odd number so 3 or 5. Is that a requirement?
4. I am using a third party load balancer for CAS array instead of NLB so I will be setting up that.
5. Do post install to ready up the new CAS. While doing this, can i use the same parameters as assigned on exchange 2010 like can i use the webmail URL for outlook anywhere, OAB etc.
6. Once this is done. I plan to move a few mailboxes as test to the new mailbox servers or DAG.
7. Testing outlook setups on new servers. inbound and outbound email tests.
once this is done, I can migrate over and point all my MX records to the new servers.
Please let me know your thoughts and what am I missing. I like to solidify a flowchart of all steps that I need to do before I start the migration.
thank you for your help in advance

Hi,
okay, you can use 4 virtual servers. But there is no need to deploy dedicated server roles (CAS + MBX). It is better to deploy multi-role Exchange servers, also virtual! You could install 2 multi-role servers and if the company growths, install another multi-role,
and so on. It's much more simpler, better and less expensive.
CAS-Array is only an Active Directory object, nothing more. The load balancer controls the sessions on which CAS the user will terminate. You can read more at
http://blogs.technet.com/b/exchange/archive/2014/03/05/load-balancing-in-exchange-2013.aspx Also there is no session affinity required.
First, build the complete Exchange 2013 architecture. High availability for your data is a DAG and for your CAS you use a load balancer.
On channel 9 there is many stuff from MEC:
http://channel9.msdn.com/search?term=exchange+2013
Migration:
http://geekswithblogs.net/marcde/archive/2013/08/02/migrating-from-microsoft-exchange-2010-to-exchange-2013.aspx
Additional informations:
http://exchangeserverpro.com/upgrading-to-exchange-server-2013/
Hope this helps :-)

Exchange Migration 2007 2010 to Exchange 2013

Let me lay it all out. We are running an Exchange 2007 environment with 2-CAS, 2-HT's and 2-MBX's clustered. We started a migration to Exchange 2010 and after starting the migration it was decided that we would instead got to Exchange 2013. In Exchange 2010
we have 3-CAS, 2-HT's and 2-MBX's. We have moved our external connections over to Exchange 2010 and only have test mailboxes on 2010 and that's where we stopped.
We installed Exchange 2013 3-CAS, 2-MBX's. We are testing out 2013 installation. We can access 2013 Web App with the 2013 test accounts. I can access 2013 test mailbox with outlook 2010 by configuring outlook for rpc/https. I am not getting free/busy
form 2007 or 2013 when logged into my 2013 test mailbox. My virtual directories are configured as the following:
Exchange 2007 - mail2007.domain.com\
Exchange 2010 - mail.domain.com\
Exchange 2013 - mail2013.domain.com\

Hello,
Please check internalurl of the Exchange 2007 and 2010 EWS virtual, you can use:
Get-WebservicesVirtualDirectory | select internalurl
If they are not set to their own FQDN, please change it back and restart the IIS services.
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Exchange 2003 to Exchange 2010 migration steps

HI ,
I have migrated windows 2003 to windows 2008.Its successfully migrated.
Second phase i have a plan to migrate exchange 2003 to exchange 2010.
My current setup
windows 2008 64bit (DC)
exchange 2003 sp2
1
Bring the Exchange organization to Exchange Native Mode.
2
Upgrade all Exchange Servers to Exchange Server 2003 Service Pack 2.
3
Bring the AD forest and domains to Windows Server 2003 Functional (or higher) levels.
4
Upgrade at least one Global Catalog domain controller in each AD site that will house Exchange Server
to Windows Server 2003 SP2 or greater.
5
Prepare a Windows Server 2008 (RTM or R2) x64 edition server for the first Exchange 2010 server.
6
Install the AD LDIFDE tools on the new Exchange 2010 server (to upgrade the schema).
7
Install any necessary prerequisites (WWW for CAS server role).
8
Run setup on the Exchange 2010 server, upgrade the schema, and prepare the forest and domains. (Setup runs all in one step or separate
at the command line.)
9
Install CAS server role servers and configure per 2010 design. Validate functionality.
10
Transfer OWA, ActiveSync, and Outlook Anywhere traffic to new CAS servers.
11
Install Hub Transport role and configure per 2010 design.
12
Transfer inbound and outbound mail traffic to the HT servers.
13
Install mailbox servers and configure Databases (DAG if needed).
14
Create public folder replicas on Exchange 2010 servers using pfmigrate.wsf script, AddReplicaToPFRecursive.ps1, or Exchange 2010
Public Folder tool.
15
Move mailboxes to Exchange Server 2010 using Move Mailbox Wizard or Power Shell.
16
Rehome the Offline Address Book (OAB) generation server to Exchange Server 2010.
17
1Rehome the public folder hierarchy on the new Exchange Server 2010 admin group.
18
Transfer all Public Folder Replicas to Exchange Server 2010 Public folder store(s).
19
Delete Public and Private Information Stores from Exchange 2003 server(s).
20
Delete Routing Group Connectors to Exchange Server 2003.
21
Delete Recipient Update Service agreements using ADS Edit.
22
Uninstall all Exchange 2003 servers.
This is my plan to migrate.But i have a doubt in installing exchange 2010 in this scenario.
Is it necessary to use
Setup.com /PrepareLegacyExchangePermissions,
Please help me what excactly i have to do

I think that <a href="http://www.micronobal.com/blog/2014/5/1/exchange-server-migration-to-the-cloud-ensure-a-seamless-transition" title="Exchange Server Migrations">Exchange Server
Migration</a> is a very delicate project and to be taken very seriously as it is a detailed work as well. You are giving us some great tips.
Some Articles I would like to share as well:
<a href="http://www.micronobal.com/blog/2014/5/1/exchange-server-migration-to-the-cloud-ensure-a-seamless-transition" title="Exchange Server Migration to the Cloud - Seamless Transition.">
Exchange Server Migration to the Cloud</a>
It takes a lot of time and effort to get it right. Thank you for helping
Here some information about services for migrations
<a href="http://www.micronobal.com/business/cloud/advancedtechnologyservices" title="Migrate your email to the cloud.">Business Email migration</a>

Exchange 2010 to Exchange Online migration Error

Hello,
I am in the middle of an Exchange 2010 to Office 365 cutover migration and i keep getting errors when trying to create a migration endpoint on Office 365 hence the migration can't progress.
I have sucessfully completed step one which is to verify the on premises domain and the Office 365 domain but it seems i am stucked on connecting with Outlook Anywhere using each available method on Microsoft Remote Connectivity Analyzer.
The first error message that i am getting when connecting through Microsoft Remote Connectivity Analyzer is that the
"The certificate chain could not be built. You may be missing required intermediate certificate". On a side note, this works on internal LAN and Outlook clients are able to connect using autodiscover.
The second error message i get, is when trying to connect using "Test-MigrationServerAvailability -ExchangeOutlookAnywhere -Autodiscover -EmailAddress <email address for on-premises administrator> -Credentials $credentials"
on a Exchange Online Powershell session i am getting:
"The migration service failed to detect the migration endpoint using the Autodiscover service."
I just can't understand why the Autodiscover tests won't pass. I am aware that Microsoft Remote Connectivity Analyzer would show error because it misses the root certificate but what should i do in order to have it running properly?
Please note that i am using an internal CA-Server which is the Exchange Server it self so i have self signed certificates.
I wonder, am i missing the big picture here?
For the migration endpoint/batch to work, is it mandatory to have a valid certificate or to be able to use autodiscover?
Thanks.

You need valid publicly trusted certificate to create the migration endpoint. You can get one for free from sites like startssl or comodo.

TS4136 Apple Mail ActiveSync issue during Exchange 2007 to Exchange 2010 migration

When customer configures the ActiveSync account on Apple Mail (using Exchange Server 2010 CAS array name) for the user whose mailbox is on Exchange Server 2007, they are not able to get any mail and account displays offline. It shows the mailbox empty as well, even though mailbox has the email items in it.
But when same account is configured using ActiveSync (using Exchange 2007 CAS Server name) it works fine.
ActiveSync & Web Services URLs for Exchange 2010 and Exchange 2007 are given as below:
S#
Virtual Directory
URL
Exchange Server 2010
Exchange Server 2007
1
Web Services Virtual Directory
Internal URL
https://email2.domain.ae/EWS/Exchange.asmx
https://email.domain.ae/EWS/Exchange.asmx
2
Web Services Virtual Directory
External URL
https://email2.domain.ae/EWS/Exchange.asmx
https://email.domain.ae/EWS/Exchange.asmx
3
ActiveSync Virtual Directory
Internal URL
https://email2.domain.ae/Microsoft-Server-ActiveSync
https://email.domain.ae/Microsoft-Server-ActiveSync
4
ActiveSync Virtual Directory
External URL
https://email2.domain.ae/Microsoft-Server-ActiveSync
https://email.domain.ae/Microsoft-Server-ActiveSync
Following error is logged on Console on Mac when this issue happens:
30/10/12 3:27:28.398 AM
Mail
*** Assertion failure in -[EWSConnection _fetchRootFolderId:], /SourceCache/Message/Message-1278/MessageStores.subproj/EWSConnection.m:202
EWS fetchRootFolderId: expected one folder in response, received: 0
0   Message                             0x00007fff8cdeeef8 -[MFAssertionHandler _handleFailureWithPreamble:description:arguments:] + 116
1   Message                             0x00007fff8cdef08e -[MFAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 185
2   Message                             0x00007fff8cd1c8db -[EWSConnection _fetchRootFolderId:] + 768
3   Message                             0x00007fff8cd1deba -[EWSConnection _connectAndAuthenticateUsingAccount:] + 650
4   Message                             0x00007fff8cd1c42d -[EWSConnection connectUsingAccount:] + 462
5   Message                             0x00007fff8cd1996a -[EWSAccount authenticatedConnection] + 437
6   Message                             0x00007fff8cd2c00e -[EWSGateway connection] + 55
7   Message                             0x00007fff8cd2dddf -[EWSGateway sendMessage:forRequest:] + 43
8   Message                             0x00007fff8cd3e54c -[EWSRequestOperation executeOperation] + 108
9   Message                             0x00007fff8ce0f97f -[MonitoredOperation main] + 228
10 Foundation                          0x00007fff94aae6b4 -[__NSOperationInternal start] + 705
11 Foundation                          0x00007fff94ac1912 ____NSOQSchedule_block_invoke_2 + 124
12 libdispatch.dylib                   0x00007fff8adc8a86 _dispatch_call_block_and_release + 18
13 libdispatch.dylib                   0x00007fff8adc9965 _dispatch_worker_thread2 + 255
14 libsystem_c.dylib                   0x00007fff8a32c3da _pthread_wqthread + 316
15 libsystem_c.dylib                   0x00007fff8a32db85 start_wqthread + 13

Hi Akebono,
Let's check a few things in your server:
1. From the Organization Configuration - Client Access - Exchange Activesync policies - Default: Verify if the option "Allow non-provisionable devices" is ON.
2. From Server Configuration - pointing <YourExchange2010> - Certificates: Verify if your SSL certificate is assigned to IIS. (You should also be able to see this certificate from OWA https session)
3. The problem may also reside in iPhone outdated software, try to test activesync connection from iPhone with the latest OS version.
4. Take a look at logs in C:\inetpub\logs\LogFiles\W3SVC1\ of Exchange 2010, those might give some more details on connectivity problems.
5. If you still experience such problems - post the ExRCA error report here.
▲ Vote if Helpful / Mark if Answer
MCSE: Messaging 2013 Charter / Private Cloud / Server Infrastructure
MaximumExchange.ru

Exchange 2010 - Exchange 2013 permanent coexsistence to avoid migration of Public Folders

Hi Guys,
I was hoping to get some opinions/ advices regarding the case explained below.
The company I work for has a medium-sized Exchange 2010 infrastructure that consists of several geographically dispersed 2-node DAGs and corresponding CASArrays. It hosts about 1000 mailboxes in total and large public folder database that is replicated on
every mailbox server in the environment. All users are using Outlook 2010/2013.
There is a business drive to perform migration to Exchange 2013. However, migration of the Public Folders is not feasible because of the lack of multimaster replication, the complicated migration process and several other limitations in Ex2013 PFs.
To work around this issue while still performing the migration I am considering the following scenario:
Deploy Exchange 2013 servers in the organization
Migrate all mailboxes to Exchange 2013 servers
Don't ever start migration of Public Folders (leave one Exchange 2010 mailbox server in every location for hosting the Public Folder database)
Keep the coexistence permanently (with mailboxes on 2013 and public folders on 2010)
What do you think of this setup? Do you see any issues with such long-term coexistence?
Thanks.

Hi,
You can leave the public folders on Exchange 2010 if you can’t migrate them to Exchange 2013. Exchange 2013 users can access public folders on Exchange 2010, but Exchange 2010 users can’t access public folders on Exchange 2013.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support

Exchange 2007 to Exchange 2010 Migration

Hi all,
I am migrating to exchange 2007 to exchange 2010 .This is not a migration data only migration like i am exporting mailboxes and importing it to new mailboxes .But email address and SAM account name will be same as per the source.Post migration i will point
the auto discover to new organisation.May i know what will be the impact to users??need to reconfigure outlook profile or does it will look for auto discover and prompt for new email id?
Jayakumar K

Is it in the same forest of or both the servers are different forest?
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Exchange 2003 to Exchange 2010 Migration

Is there anything I have to do to migrate Exchange 2003 to Exchange 2010 aside from migrating the database(s)? I believe autodiscover picks up the new server when people open Outlook?

It will definitely HELP
you with the migration process, its not a guaranty for a successful one.
You should be familiar with both systems (Exchange 2003 & 2010) and know the migration process and be familiar with each step .
Best practice is to make the migration in lab environment that is a copy of you production environment first. that way you will get an experience with the process and know in advance if there are any issues before go to production. I
know that in real world this is not always possible.
Here is another grate guide from Pete Long:
http://www.petenetlive.com/KB/Article/0000234.htm
As a side note, Exchange SP1 or SP2 no longer supported, so make sure your Exchange 2010 is installed with minimum SP3 (RU5 is better).
Please take a moment to Vote as Helpful and/or Mark as Answer where applicable. Thanks.

Public Folder Exchange 2010 to Exchange 2013 Migration

hi guys
i have Exchagne 2010 SP3 and Exchange 2013 CU2 , i have moved all my mailboxes to Exchange2013 , before that i created Exchnage2013 Address Book ( web base ) for OAB . i have Public folder Database( used for Default Address book ) -Free/Busy on exchnage
2010 . now i don't need PF at all on Exchange 2013, So can i just Delete Public Folders from Exchange 2010 without Moving Public Folder ( free/Busyy , etcc... ) to Exchange 2013. from exchange 2007 to exchange , we did create Public folder
on Exchnage 2010 , Add replica , waited for sync, moved OAB generated Server as Exchnage 2010.
as i see from deploymetn guild, there are few steps need to be done to move PF to excahnge 2013, but since i don't need PF, can i just delete it.
Indunil

Hi
I m migrating public folder 2010 to 2013
When i do :
Get-PublicFolderMigrationRequest | Get-PublicFolderMigrationRequestStatistics -IncludeReport | Format-List
I have a lot of line like this
00-00-00-00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-36-B9-C6-5D-38-99-D6-11-9B-D6-00-08-02-55-A6-70-00-00-00-18-33-94-00-00 ». Ce dossier peut être
lié manuellement en exécutant la cmdlet Enable-MailPublicFolder une fois la migration terminée.
23/05/2014 19:18:02 [serveur] Avertissement : échec de recherche ou de liaison de l'objet destinataire « 96-7D-85-6C-DC-A6-83-42-AC-77-A4-5E-BD-CD-52-9B » dans
Active Directory pour le dossier public à extension messagerie « Public Root/IPM_SUBTREE/Secrétariat RC/PAYS/VENEZUELA/2006/SINCOR » avec l'ID d'entrée «
00-00-00-00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-36-B9-C6-5D-38-99-D6-11-9B-D6-00-08-02-55-A6-70-00-00-00-13-4D-8A-00-00 ». Ce dossier peut être
lié manuellement en exécutant la cmdlet Enable-MailPublicFolder une fois la migration terminée.
it scared me, what does it means ? Do i do something wrong?
I have let it work
And when i check status i have this :
Statut: Failed
Détails status : Failed other
Syncstages : Copying message
Estimed transfert size : 0
Pourcentcomplete : 95
What do i do? Can You help me? I m a little scared right now
Thanks

Planning a migration from Exchange 2010 to Exchange 2013

Hello,
I am planning a migration from Exchange 2010 to Exchange 2013 and I was wondering if there was a good guide on the UM migration. I haven't found one that isn't confusing as heck.

Hello,
Is there any update?
If
you have any feedback on our support, please click here
Cara Chen
TechNet Community Support

Migrate UM from Exchange 2010 to Exchange 2013

I have been running Exchange UM since Exchange 2007, using the ps1 script to move all my Auto Attendants into the 2010 environment. I'm at a loss on how to efficiently do this in moving from Ex2010 to Ex2013, though. I've read
http://technet.microsoft.com/en-us/library/dn169226 and it's Step 3 that's got me bewildered. I have 44 Auto Attendants, most of which with up to five custom greetings, numerous key mappings,
etc. That Step 3 indicates having to move each custom greeting individually.
I'm just getting into PowerShell and struggling as-is. Compounding that floundering with the lack of clear documentation on moving custom greetings en mass has me frustrated. Any assistance would be greatly appreciated. Thank you.

Hi David,
Before we migrate all the users to
2013, we would recommend you to test voice mail on
2013 server.
Here are the steps we need to follow
to test VM on 2013 server:
1. Create a certificate for both Unified Messaging service and the Call Router services. Here is an article on how
to create certificates , http://technet.microsoft.com/en-us/library/dn205141(v=exchg.150).aspx
2. Create new dial plan in Exchange
2013. Here is an article on how to create a dial plan, http://technet.microsoft.com/en-us/library/bb123819(v=exchg.150).aspx
3. Run scripts on both Exchange and Lync servers.
4. Create test user and enable the user for both Lync and Exchange.
5. Enable newly created user for UM and test voicemail for that user.
Additionally here is a link which has checklist to upgrade
from Exchange 2010UM
to 2013UM http://technet.microsoft.com/en-us/library/dn169228(v=exchg.150).aspx
Thanks,
James

Migrating Exchange 2007 to Exchange 2010 at a different physical location - Suggestions??

Hello! I have a domain in Canada that is running Exchange 2007. My company wants to consolidate this Exchange and migrate the mail to the USA based Exchange 2010 in NYC. Not only is it migrating from 2007 to 2010, it's also moving locations physically.
Does anyone have any thoughts on how to best approach such a situation?

ok... in addition to sarvesh comments i would also add a checklist based approach .. please follow below link
http://blogs.technet.com/b/mspfe/archive/2014/03/20/checklist-upgrading-to-exchange-2010-from-exchange-2007.aspx this would help you not to miss anything in terms to critical or non-critical aspects.
after checklist i would suggest you give a shot at exchange server deployment assistant which will help you putting your scenario and suggesting the best practices. http://technet.microsoft.com/en-us/office/dn756393.aspx
this guide for planning of migrations also shows the full scenario step by step : http://exchangeserverpro.com/wp-content/uploads/Exchange%20Server%202007%20to%202010%20Migration%20Guide%20V1.0%20-%20Planning%20Chapter.pdf
this is also a step by step graphical representation for the process. THIRD PARTY LINK though.. http://www.petenetlive.com/KB/Article/0000236.htm
Let me know if this helps.
MARK AS USEFUL/ANSWER IF IT DID
Thanks
Happiness Always
Jatin

Keep exchange 2007 Hub transport & CAS during migration to Exchange 2010

Hello,
during a migration from exchange 2007 to exchange 2010 is it supported to keep the old exchange 2007HUB and CAS in charge of the outside mail flow (send/receive) and OWA service.
Here is the scenario :
Actual OWA url : https : // webmail . compagnie . com (2007)
Future OWA url : https : // owa . compagnie . com 2010)
Keep the old url accessible for the users which have not be migrated to the new exchange 2010 MBX server.
Indicate to the migrated users to use the new url instead of the old one.
Keep the old hub transport server (2007) handle the mail flow (send/receive) to the outside.
At the end, when all the users will be migrated, configure the new 2010 Hub/cas to handle the mail flow (send/receive) to the outside.
Thanks a lot for your answers.
David

Thanks for your answers.
So if I have understood right, the only thing I have to take care about (in order to let the 2007 cas/hub server handle the external mail flow (on which the MX is bind) until all mailboxes are migrated) is to add the 2010 cas/hub server in :
Organization Configuration ---> send connector ---> Actual 2007 send connector --> Source server
Thanks a lot.
David
That will take care of the outbound message flow, yes.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

How to migrate public folders from legacy (exchange 2003 ) to exchange 2010

How to migrate public folders from legacy (exchange 2003 ) to exchange 2010 . Please suggest ?
Aditya Mediratta

Hi Aditya,
please find the answer in
http://blogs.technet.com/b/agobbi/archive/2010/08/04/how-to-move-public-folder-from-exchange-2003-to-exchagne-2010.aspx
Please ensure you have a working mailflow from Exchange 2003 to 2010, vice versa, before you begin.
Basically it's the same procedure as adding some PF Database in E2K3; just
run .\AddReplicaToPFRecursive.ps1 -server "Exchange 2010 Server" -TopPublicFolder "\" -ServerToAdd "Exchange 2010 Server"
Wait until some initial data started to replicate; after that run
Update-PublicFolderHierarchy -Server "Exchange 2010 Server"
After replication has finished you can do a
.\MoveAllReplicas.ps1 -Server "Exchange 2003 Server" -NewServer "Exchange 2010 Server"
Please let me know if it worked.
Kind regards,
Martin

Exchange 2010: Virtualized Exchange 2010 Datacenter Migration

Similar Messages

Maybe you are looking for