It is, obviously, crucial to validate what damage any script you run will perform in case you review the changes and find that it will cause you problems.I am trying to add a universal, mail enabled security group to a public folder calendar for permission purposes. The structure looks like this screenshot below, with each folder having a mix of different permissions added:īefore I replace the permissions, I will want to test the script to see which permissions will be removed. I’ll give this group Owner permissions down the tree, starting from a folder called TopLevel. In the example below, I’m going to replace the existing permissions with a Mail-Enabled Security Group, called PFPGroup. To use the script, download it from my GitHub. I’ll cover a quicker way of performing a search and destroy for these type of issues in my next article on the subject, but if you want to perform a clean of a Public Folder tree and remove spurious permissions that should not be there, then using the ReplacePFPermissions script may help. For example, you might find some recently deleted users, or users who are not mailbox-enabled still have Public Folder permissions, as shown below: One common problem you may be trying to solve (and failing) is removing permissions that aren’t identified as problematic by the Source Side Validation scripts provided by Microsoft. The ReplacePFPermissions script is a simple script that enables you to remove non-default permissions from a Public Folder and it’s sub-folders and add a new Public Folder permission – such as a group, or perhaps an admin account if you are removing general user access. To help with this requirement for one of my customers, I’ve written a simple script that can be used to achieve this. There are scripts from Microsoft to do this on Exchange 2013 and above, but not a quick and simple one for Exchange 2010. One common ask is to be able to quickly replace a set of Public Folder permissions on Exchange 2010. Unfortunately, they’re still around and as Exchange 2010 lives beyond the grave, with its life-support extended until October 2020 you, like many others, are trying to get rid of Public Folders or move them to modern Exchange or Office 365. You wouldn’t expect that in 2020 we would still be trying to manage Public Folders in Exchange, especially given that people originally expected them to die a death nearly fourteen years ago, with Exchange 2007.
0 kommentar(er)
