Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1864
  • Last Modified:

Public Folder Migration

Need to move public folders from an Exchange 2000 server to a 2003 server
Individual folders have been added as replicas etc but mothing appears to be moving

All the posts Ive read say - replicate the heirachy - or simply use pfmigrate and it will move the folders accross

I cant find any simple to understand info on how to do this
The 2000 Server is going to be killed off afterwards so EVERYthing needs to go to the new box (I appreciate this might take a while but these guys pay me by the hour so pfmigrate would seem to be the fastest option.)

What commands will move EVERYthing from the Exchange 2000 Server to the 2003 server???????

Mailbox's are allready moved.

0
Pete Long
Asked:
Pete Long
  • 11
  • 4
  • 4
  • +2
4 Solutions
 
ksharma4Commented:
0
 
amaheshwariCommented:
You can use  this option:
PFMIGRATE.WSF /S:source_server /T:destination_server /A /N:100 /F:C: \logfile.txt

In the command above the /S:source_server switch is where you would enter the name of the server that currently contains the public folders. Likewise, the /T:destination_server switch allows you to enter the name of the server to which you want to move the public folders. The /A switch adds the target server to the folder replica list. The /N:100 switch allows you to enter the number of public folders to modify. For some reason, this switch is an absolute requirement in add mode, but not in delete mode. If you were using this command in real life, you would replace the number 100 with the number of folders that you need to migrate.

Fortunately, you don't have to count public folders to figure out what number to use. The PFMIGRATE tool has a reporting option. You can run a report and it will tell you how many folders exist on the source server. The switch used to generate a report is /R.

The final portion of the command above is the /F:C: \LOGFILE.TXT switch. This allows you to log the operation to a text file.

Once you have added the target server to the list of replicas, you must wait for the replication process to complete before doing anything else. Once replication is finished, you can use PFMIGRATE to remove the public folders from the source server. The command syntax for this operation is:

PFMIGRATE /S:source_server /D:destination_server /D

In this command, the source server is the server that you want to remove the replicas from and the destination server is the server that should now contain the replicas. The /D switch tells PFMIGRATE to delete folders from the source server, but only if they exist on the destination server.
0
 
rakeshmiglaniCommented:
pfmigrate is just a tool that automatically adds public folder replicas from the source server to the target server.once the replicas have been added the public folder replication takes place via smtp messages between the public folder stores on both the servers.
by default public folder replication messages have the lowest priority..

has the PF heirachy replicated to the new server?  you can check it by opening ESM and then expanding Public folders and then the Pf tree and connecting to the new server.
0
Get free NFR key for Veeam Availability Suite 9.5

Veeam is happy to provide a free NFR license (1 year, 2 sockets) to all certified IT Pros. The license allows for the non-production use of Veeam Availability Suite v9.5 in your home lab, without any feature limitations. It works for both VMware and Hyper-V environments

 
amaheshwariCommented:
The easiest way to complete a migration of public folders from Exchange Server 2000 to Exchange Server 2003 is to set the Exchange 2003 server up as a replication partner for the public folders that you want to migrate. After doing so, you can just wait for Exchange to replicate the public folders to the new server. Once replication is complete, you can remove the old server from the list of replication partners.


To accomplish this, open the Exchange System Manager and navigate to Administrative Groups -> your administrative group -> Servers -> your public folder server > First Storage Group -> Public Folder Store -> Public Folder Instances.

Right click on the folder that you want to migrate and select Properties.

When you see the folder's properties sheet appear, select the Replication tab and click the Add button.

Specify the public folder store to which you want to migrate the folder and click OK.
Exchange will now begin to create a replica of the folder on the designated public folder store. After the replication cycle completes (which can take a while), you will need to remove the original server from the list of replication partners.


Navigate through Exchange System Manager to Administrative Groups -> your administrative group -> Servers -> the new server -> First Storage Group -> Public Folder Store -> Public Folder Instances.

Now, right click on the folder that you just migrated and select Properties.

Go to the Replication tab, select the old server from the list, click Remove and then OK. Exchange will eventually remove the folder replica from the old server, leaving only the copy on the new server.
As you can see, this technique is pretty easy to use, but it does have its limits. This seemingly easy task would become overwhelming if you had a public folder store with thousands of folders
0
 
Pete LongConsultantAuthor Commented:
>>The PFMIGRATE tool has a reporting option. You can run a report and it will tell you how many folders exist on the source server. The switch used to generate a report is /R.


pfmigrate /r


just returns the syntax guide?????????????
0
 
rakeshmiglaniCommented:
Overview of the Public Folder Migration tool
http://support.microsoft.com/kb/822895/en-us

Please check the above link for the pfmigrate command line options
0
 
Pete LongConsultantAuthor Commented:
amaheshwari

I tried doing it that way first and it didnt work - nothing is appearing on the new 2003 server - I WANT to  migrate EVERYTHING so I can kill the original Echange server - If I can use pfmigrate to move the mail stores in two or three commands then I want to be able to do it that way - hence the intrest in pfmigrate

to kill the original server I need to move  offline address books  - Schedule+ folders  etrc etc plus all the users own public folderrs

0
 
amaheshwariCommented:
pfmigrate.wsf /s:2000 server/t:2003server /r /f:c:\temp\ pfmigrate.log
0
 
Pete LongConsultantAuthor Commented:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Im guessing that that produces the report yes?

0
 
amaheshwariCommented:
yes it is for producing report.
0
 
SembeeCommented:
How long have you waited for the replication to take place?
Coming off an Exchange 2000 server is slow, very slow. If you have only waited a few hours, then you haven't waited long enough. Leave it a week and see what happens (I am not joking).

Simon.
0
 
Pete LongConsultantAuthor Commented:
Right Im getting the client to run that command -

I dont know what the output of that command looks like
I will need to know which are system folders and which are public folders - does it tell you??????
i.e. if there are 77 public folders and 23 system folders the commands would be

the commands would be

PFMIGRATE.WSF /S:source_server /T:destination_server /A /N:77 /F:C: \logfile.txt
PFMIGRATE.WSF /S:source_server /T:destination_server /SF /A /N:23 /F:C: \logfile2.txt

then after replication is complete

PFMIGRATE /S:source_server /D:destination_server /D

to remove the orginals

0
 
Pete LongConsultantAuthor Commented:
>>Leave it a week and see what happens (I am not joking).

Hi Simon :)

Doesnt pfmigrate force it quicker than a week!?!?!?!?!
0
 
SembeeCommented:
Nope.

pfmigrate is just a script file. All it does is set the replica settings in one hit, rather than having to set the folders individually. It is not the "magic option" that everyone thinks it is. It doesn't help with the inherent problems on Exchange 2000 that replication is very conservative to save bandwidth - remember Exchange 2000 was designed when 10-baseT networks were common.

Its value is limited now, as Exchange 2003 SP2 can do the same thing with the GUI.

Simon.
0
 
Pete LongConsultantAuthor Commented:
:) this dont look good from the client

pfMigrate.wsf /s:swnmail1 /t:pluto /r /f:c:\pfmigrate.log

Microsoft Exchange Public Folder Migration Tool

Tue May 2 15:41:15 UTC+0100 2006

Source Server:      SWNMAIL1      Version 6.0 (Build 6249.4: Service Pack 3)
Target Server:      PLUTO      Version 6.5 (Build 7638.2: Service Pack 2)
WMI Server:      PLUTO

Report Mode in progress.

Analysis of 0 folders with replica on 'SWNMAIL1' completed.

0      folders without replica on 'PLUTO'.
0      folders with replicas on both servers.


Tue May 2 15:41:26 UTC+0100 2006

--------------------------------------------------------------------------------

On his server NOTHING appears under administrative tools > Folders > public folders
you have to drill down to servers > servername > first storage gp > public folders

Is this normal?

given the output of the report above things dont look to promising - any thoughts
0
 
Pete LongConsultantAuthor Commented:
You would think microsoft would make it EASIER to SPEND MONEY upgrading their products sigh - all I want to do is get rid of the 2000 exchange box
0
 
ksharma4Commented:
Pete, You should wait for sometime as correctly said by Sembee, it takes hell lot of time.

0
 
Pete LongConsultantAuthor Commented:
:) I can wait the time - I just dont want to wait the time and find out Me/Client has done something wrong essentially this  is what the client has ran through
http://support.microsoft.com/default.aspx?scid=kb;en-us;307917&Product=exch2k

0
 
SembeeCommented:
There is nothing that can be done because the problem is with Exchange 2000. You can see that Microsoft have addressed the problem with Exchange 2003 with the send hierarchy and send contents options for the new versions. I can do Exchange 2003 to Exchange 2003 migrations in a weekend now.

With Exchange 2000 deployments, I start the migration on a Monday, and leave it for the entire week. The more time that you can give it the better.
Otherwise it comes down to doing a manual migration of the public folder content using PST files.

Simon.
0
 
Pete LongConsultantAuthor Commented:
>>Otherwise it comes down to doing a manual migration of the public folder content using PST files.

Ah Ive done that with an SBS2K to 2K3 Migration :( then had to manually put all the permissions back in :(

OK- Ill put my waiting hat on :)
0
 
Pete LongConsultantAuthor Commented:
Man I knew they wouldnt be happy with that sigh :(

now they are asking about doing a pst migration

can system files be migrated in this way? - offline address book etc?

Ive migrated from one domain to another using pst files from public folders (using outlook) but how do you move folders within a domain in this way?

0
 
SembeeCommented:
You can't do the system folders.
You have to let those rebuild using the natural processes.

The OAB is easy enough - simply switch the server used for OAB generation.

The Free Busy information requires every user to make an entry in their calendar, wait 30 minutes for the information to be posted, then delete it again.

All the other public folders - remove the replicas, so that the only server listed is the server that they are homed on. Make sure that you have exported all the content first, get it wrong and you will loose data.

Simon.
0
 
Pete LongConsultantAuthor Commented:
Cheers Simon If this is going to take a week Ill close this Q I'll split up thew points

Thanks all
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 11
  • 4
  • 4
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now