Solved

Exchange: Orphaned public folder replication

Posted on 1998-10-21
2
361 Views
Last Modified: 2013-12-23
Origional situation:
2 exchange 4.0 servers and 2 different sites. SiteA connected to SiteB via a RAS connector and Directory replication connector. Public folders replicated via RAS connector between the 2 sites.

Current situation:
SiteA server Crashed and died-completely-no backups available.(I'd like to point out that I didn't set this server up!!) The server at SiteA had to be rebuilt from scratch. The Directory replication connector(and also the RAS connection) also had to be deleted on SiteB and recreated on siteA & siteB.

Problem:
The recreation of the Directory Replication has caused problems with the public folders-a good description of this can be found in Kbase article:Q152433.
The problem is that SiteA has no public folders homed as they were all lost.The public folders can be viewed at siteA but cannot be accessed as this error pops up "The object cannot be found in the directory.This may be because the directory replication has not been completed"
On SiteB the Public folders can be viewed as they are now homed on siteB.
When looking at the properties of the folders at SiteB  using the exchange admin program-an looking at the INSTANCES tab-the public folders are shown to be "siteA/foldername".
Can anyone tell me that now directory replication has started if the Public folders will be replicated back to SiteA without any problems. If not are then any measures that can be taken to ensure that the replication restores the folders to SiteA.
As this is quite a detailed question, if any more info is needed then please post a comment.
0
Comment
Question by:rcoldwell
2 Comments
 
LVL 1

Accepted Solution

by:
achmed earned 150 total points
ID: 1564611
Now that you have rebuilt the server A and since there were no back-ups, you have orphaned folders. While Server A will get the replication from Server B, it does no know that it is the owner either. So it will display the same message "The object cannot be found in the directory..."

What you need to do is delete the orphaned folders and recreate them on Server A. Because there was no replication to Server B, ALL OF THE INFORMATION IN THOSE FOLDERS IS GONE!

Here is what Microsoft has to say about deleting orphaned folders:
1. Start the Microsoft Exchange Administrator program and go to the Server container.
2. Double-click on the Public Information Store.
3. Look for the Public Folders on the left hand side of the Instances Property page and add them to Folders on This Information Store on the right hand side of the Instances Property page. This has to be done for every orphaned folder.
   NOTE: If the folders do not appear on the right hand side, you must follow these steps:
   WARNING: If you ever plan to re-join the sites, do NOT go through this procedure.
      A. Go back to the server object and display the properties.
      B. From the Advanced tab, go to the DS/IS consistency adjustment.
      C. Choose to adjust all inconsistencies and click on Adjust.
4. Go to the Organization's Public Folder tree on left hand side of the window.
5. Double-click on the folder in question.
6. Click the Client Permissions button on the General tab and give Owner rights to an administrator account.
7. Start a Microsoft Exchange client, log on as the administrator above, and remove the orphaned folders.
 
The Offline Address Book and Schedule+ Free Busy folders from other replicated sites cannot be removed from the hierarchy using this procedure. These folders should disappear from the System Folder hierarchy a week after replication has been broken. The Information Store will mark the folders for deletion the first time it is restarted after replication has been broken between the sites. The next time that the Information Store is restarted, after the 7 day waiting period, the orphan folders will be removed from the hierarchy. This is done to avoid recreating the system folder hierarchy if the sites are re-connected within a week. These folders are completely harmless because they are not visible from the clients and have no effect on any other store task.

----------------------------------
This was from Q152433

0
 
LVL 1

Author Comment

by:rcoldwell
ID: 1564612
This did not really answer my question and I have now managed to get round the problem-what needed to be done was to home the public folders on site B, run the DS/IS consistency adjutment and then replicated the folders back to site A.
I have ended with a situation where none of the folders were lost.
0

Featured Post

IT, Stop Being Called Into Every Meeting

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

Join & Write a Comment

Nslookup is a command line driven utility supplied as part of most Windows operating systems that can reveal information related to domain names and the Internet Protocol (IP) addresses associated with them. In simple terms, it is a tool that can …
Many of us in IT utilize a combination of roaming profiles and folder redirection to ensure user information carries over from one workstation to another; in my environment, it was to enable virtualization without needing a separate desktop for each…
This video discusses moving either the default database or any database to a new volume.
This demo shows you how to set up the containerized NetScaler CPX with NetScaler Management and Analytics System in a non-routable Mesos/Marathon environment for use with Micro-Services applications.

758 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

16 Experts available now in Live!

Get 1:1 Help Now