Can't delete orphaned public folders on Exchange 5.5

I've broken a site connector with a larger Exchange 5.5 org and am just using SMTP now with a single server.  There are public folders still visable that were replicated from the larger organization that I didn't have rights to before and can't do anything with now.   When I try to delete them in Outlook, I get the message: "Unable to delete this folder. See the folder owner or your administrator to change your permissions.  This folder cannot be opened because there is a configuration problem on the server.  Contact your Exchange admin...."  I have assigned myself full permissions from Exchange admin but it still won't let me do anything.  I'd love to get rid of this junk before I upgrade to 2K3.  Anyone ever had a similar problem? Am I overlooking a place where I can take ownership of these folders?

Who is Participating?
Run the Exchange Administrator program, and run the Directory Store/Information Store (DS/IS) consistency adjuster. To run the adjuster, select the server, view its Properties sheet, select the Advanced tab, click Consistency Adjuster, and select all the options for public ISs, enabling All inconsistencies. Depending on the size and number of items in the IS, the process can take a long time. Check that this operation has successfully completed by inspecting the NT Event Viewer application log.

Pasted from
This can cause problems if you ever reconnect to the other site.

Do the above will rehome the public folders and then allow you to delete them. But if you never plan to reconnect to the other site it will be OK.

Hey, can you use the Exchange Public Folder Utility PFDAVADMIN?

I've used this for all sorts of public folder tasks that I couldn't do otherwise.
DavidColesAuthor Commented:
Essentially SunKing's anser above took care of it.  From there I was able to go into Exchange Admin--Servers--Public Information Store-- "Public Folder Resources", and get "Properties" of the folder I wanted to delete, give myself "Owner" rights under "Client Permissions" and then I could manage them.

The "PFDAVADMIN" tools look cool but the doc's say they are for AD/Exchange 2K and I couldn't get them to work in my environment.

Thanks to all who responded!
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.