Problem after deleting legacy exchange administrative group


Start ADSI Edit. In the CN=Configuration container, locate the following container:

CN=Services,CN=Microsoft Exchange,CN=ORGANIZATION,CN=Administrative Groups,CN=administrative_group,

Now we were missing the ‘Folder Hierarchies’ folder – All we have to do is recreate it as follows: 
Create the “Folder Hierarchies” under the Exchange Administrative Group 

1. Right click on Exchange Administrative Group 
2. Select New Object 
3. Select msExchPublicFolderTreeContainer for the class and click Next 
4. Enter the following for the value: Folder Hierarchies, click Next 
5. Click Finish 

Create Public Folder Tree Object 

1. Right click CN=Folder Hierarchies -> New Object 
2. Selected msExchPFTree for the class 
3. For the value we entered, “Public Folders” and clicked next 
4. Clicked on the “More Attributes” button, selected msExchPFTreeType and set the 
value to 1. Note: This is very important that this value is set to a value of 1 as 
this tells Exchange that this is a MAPI Tree 
5. Click Ok and then finish 

Populate msExchOwningPFTreeBL attribute object of the PF Stores in the organization 
(Since this attribute is not directly editable, you have to follow the below steps 
to do this for each PF store) 

1. Get properties of the newly created “Public Folders” Tree object in ADSIEdit. 
2. Copy the distinguishedname value to the clipboard and then click cancel. 
3. Navigate to the Storage group that contains the Public Folder Store for this 
server and get properties of the server database. 
4. Locate the msExchOwningPFTree attribute and paste in the value that was copied 
to the clipboard in step 2. Click OK. 
5. Restart the Information Store Service 

Set permissions on the Public Folders

  1. Start ADSI Edit. In the CN=Configuration container, locate the following container:

CN=Services,CN=Microsoft Exchange,CN=ORGANIZATION,CN=Administrative Groups,CN=administrative_group,CN=Folder Hierarchies,CN=Public Folders

Note In this container, ORGANIZATION is the name of the Exchange Server organization and administrative_group is the name of your administrative group.

  1. Right-click CN=Public Folders, and then click Properties.
  2. Click the Security tab.
  3. Make sure that the Allow inheritable permissions from parent to propagate to this object check box is selected.
  4. Make sure that the Everyone group has the following Allow permissions:
  • Create named properties in the information store
  • Create public folder
  • Create top level public folder

If the Allow inheritable permissions from parent to propagate to this object check box is selected, the Everyone group should already have these permissions. Make sure that the Deny check boxes are not selected.

6. Now try to mount the PF store and see if we can access it fine now. 

http://support.microsoft.com/?id=313866 
http://technet.microsoft.com/en-us/library/cc817865.aspx 
http://social.technet.microsoft.com/Forums/en-US/exchangesvravailabilityandisasterrecovery/thread/35769dc6-1b32-4409-a2c2-38d1de37db01/

11 thoughts on “Problem after deleting legacy exchange administrative group

  1. A million thanks for this post.
    I have been struggling with this issue for the past 3 days, after recklessly deleting my old Exchange 2003 legacy First administration group.

  2. Saved my bacon!

    Sincere thanks for your efforts in posting this information. Your time and expertise is greatly appreciated!

  3. This really saved my bacon, I deleted the old Exchange 2003 administrative group via ADSI and the next thing I know the PFs are gone! Gulp! Then I found this article and now they are all back!

    Cheers

  4. Seriously – this is brilliant. I was preparing myself for a miserable ordeal after cleaning up the old Administration Group and finding that the PF’s were all gone. I expected a support call to MS and 4-5 hours of waiting, etc. Instead, it was fixed in about 4 minutes. I can’t thank you enough.

  5. Thanks very much! Had to use your howto for second time today!!!
    We have some customers still with SBS 2003 and migrating 2k3 to Exchange 2010 is everytime something special (I get only old buggy machines ….)

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s