Solved

Pfmigrate limitaton on number of PFs to migrate.

Posted on 2006-11-12
5
377 Views
Last Modified: 2012-05-05
Hello,

Does pfmigrate needs to contact or do LDAP calls to a domain controler
while migrating public folders between exchange 5.5 and exchange 2003 ?

The exchange guys with whoom i work tried to migrate large number of PF
(>3000) from 5.5 to e2k3, and the scripts stops at ~1000 PF.When this error
occurs, no PFs has been migrated.
So they told me perhaps it corresponds to the ldap MaxPageSize set on my DC
(1000 by default)and asked me to raise this value higher.
While i don't think they are right, i'd like to clarify their statement with
exchange gurus before altering the values on my DC.

Thanks.
0
Comment
Question by:boubbha
  • 2
5 Comments
 
LVL 104

Accepted Solution

by:
Sembee earned 500 total points
Comment Utility
You do realise what pfmigrate is?
It is simply a script that adds a server to the replication list. It doesn't actually replicate the data for you, nor does it make replication move any faster.

As you have Exchange 2003, you can use ESM on that version to achieve almost the same effect, particularly if you have nested folders. Simply use the All Tasks wizard to add the replica to all the folders.

Simon.
0
 

Author Comment

by:boubbha
Comment Utility
Thanks for your answer.

So if i understood you, there is no need to connect to any DC whilie using pfmigrate, and so no need to alter the ldap MaxPageSize set on my DC on my DC: good news ! :)

So what could be the reasons why the script fails at ~1000 PFs ? This value makes me think about quota or limitation set on exchange confiuration........
Any suggestions would be greatly appreciated.

Thanks.
0
 
LVL 104

Expert Comment

by:Sembee
Comment Utility
I have no idea on the script as I don't use it.
It wouldn't surprise me if there was a limit in the script, whether that limit is script or domain I wouldn't know.

Many people seem to think that pfmigrate.wsf is the "magic" tool for doing the migration, but it isn't. It makes things a little easier, but its usefulness was reduced with the release of Exchange 2003 SP2.

Simon.
0

Featured Post

Why spend so long doing email signature updates?

Do you spend loads of your time carrying out email signature updates? Not very interesting are they? Don’t let signature updates get you down. Let Exclaimer Cloud - Signatures for Office 365 make managing email signatures a breeze.

Join & Write a Comment

Resolve Outlook connectivity issues after moving mailbox to new Exchange 2016 server
Follow this checklist to learn more about the 15 things you should never include in an email signature from personal quotes, animated gifs and out-of-date marketing content.
In this video we show how to create an email address policy in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Mail Flow…
To show how to generate a certificate request in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Servers >> Certificates…

744 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

15 Experts available now in Live!

Get 1:1 Help Now