Article ID: 111667, created on Jul 19, 2011, last review on May 10, 2014

  • Applies to:
  • Operations Automation 5.x


After importing Exchange Public Folders into POA Customer Control Panel shows different permission than the cmdlet Get-PublicFolderClientPermission on backend for Public Folders which name contains '#' symbol.


WebDAV protocol used to apply Public Folder's permissions processes folders with name containing '#' symbol incorrectly.


To repair Public Folders with broken permissions:

Login to POA database and perform the following query:
SELECT ds.subscription_id,
COUNT(DISTINCT pf.folder_id) AS folders_in_subscription,
COUNT(pfp.folder_id) AS items_in_all_folders
FROM exch_domain_services ds
INNER JOIN exch_public_folders pf ON pf.ds_id = ds.ds_id
INNER JOIN exch_public_folders_permissions pfp ON pfp.folder_id = pf.folder_id
GROUP BY ds.subscription_id;

The query helps to estimate the total number of items which should be modified.

For each subscription:
  • Log into Customer CP and go to Hosting > Configuration & Administration > Exchange > Public Folders
  • Type a string '*#*' in the field 'Name' of the search filter to select all public folders with name containing '#' symbol
  • For each found public folder:
    • Select public folder and go to the Permissions tab
    • For each item in the list:
      • Select an item;
      • Remember the current role setting, select some other role from the combobox and press 'Submit'
      • Select the same item second time and restore original role setting
    • If you want to control the changes: for current public folder execute the cmdlet Get-PublicFolderClientPermission in the Exchange Management Shell and make sure that all permissions are in sync. Cmdlet example: Get-PublicFolderClientPermission -Identity \P0001000005\PF\#test1 | fl

5356b422f65bdad1c3e9edca5d74a1ae 2554725ed606193dd9bbce21365bed4e caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF