I am having issues with that method. I keep getting an error . ID no:80040e19 This object is no longer available, when I right click a public folder.
I have gone through all the proposed resolutions to this error, but none seem to apply to me.
I was thinking that since I'm going to take the old server offline anyway, could I justwait till everyone is off, then "move" the public folders like I do the mailboxes using AD?
Oh I see. I was selecting the public folders within the original server container and getting that error. Once I selected them from the root Folders/Public folders I was able to turn on replication. So when I am ready to remove the original server I just go to the same spot and remove it from the list?
Thanks again for your help, it is much appreciated.
Posts: 3004
Joined: 9.May2007
From: India
Status: offline
hi Open ESM Right click public folder tree and click on connect to and select the right server, because i feel that you might be connecting to some other server where just hierarchy replicating or replicated
Ok, so far so good. I have moved almost all my mailboxes, and my public folders are being replicated. I am going to start turning off replication on the original server. One thing I notice is that if I look in ESM at server/storage group/public folder store/replication status they all say "local modified", but if I look in the folders/public folders/replication tab and click details, they all say "In Sync". Is this normal. Which one do I trust? I did do a couple of test and I THINK replication is working.
Also any advice on the actual removal of the old exchage server from AD and the network?
Posts: 3004
Joined: 9.May2007
From: India
Status: offline
Generally, when the replicas'' status is "In sync", the synchronization is completed. The following are the four statuses:
-- In sync. This state indicates that replicas are the same between this server and the remote server. -- Local modified. This state indicates that the replica has changed on this server. -- Remote modified. This state indicates that the replica has changed on the remote server. -- Both modified. This state indicates that the replica has changed on both this server and the remote server.
Check out the number of items and size replicated. Try to create a new PF on both the end test out replication is working successful. if so just for monitoring purpose you can remove the replica and confirm it.
How about the ESM system folders? Do I need to replicate ALL of them. I looks like there are some that I shouldn't...I wanted to post a shot of the folders that are there, but it seems I cannot post pics. It says " Either the feature is disabled, or you do not have sufficient permission." on the bottom....