I'll look at the example of changing the default calendar permissions of the default ACL on the calendar as this is one of the harder things to do and there are a few points that can catch you out.
First point is that when you modify permissions with EWS you basically grab the DACL from the server make your changes locally to the DACL and the post it back in a Update Folder operation. This means the logic you use on the client side needs to be up to dealing with this. The permissions object in the Managed API has a Add and Remove methods and you have the ability to modify am ACE within the permissions collection. The one problem you can have is if the Folder permissions is currently set to custom and you try to use one the default FolderPermissionLevel. You will also have problem if you don't check the current collection and try to add a duplicate ACE into the collection.
A simple way to solve this is to first search the current collection for any existing ACE entries and remove the existing ACE then add the new rights you want set using the Add method. The other issue you need to deal with when setting the calendar folder permission is to also make sure you set the corresponding rights on the FreeBusy Data folder or you may have problems such as explained in http://support.microsoft.com/kb/184151
I've put together two examples both of these use EWS Impersonation which you can configure in 2010 via RBAC http://msdn.microsoft.com/en-us/library/bb204095%28v=EXCHG.140%29.aspx
There are 3 varibles in the script you need to modify
$MailboxName = "user@domain.com"
This is the mailbox you want to make the changes and what will be impersonated
$Permission = [Microsoft.Exchange.WebServices.Data.FolderPermissionLevel]::Editor
This is the rights you want to set
$credentials = New-Object System.Net.NetworkCredential("user@domain.com,"password")
These are the user credentials to use this user must have impersonation rights
I've posted both examples up here
In the first example this shows how to set the Default permissions for the default user on the Calendar to Editor
The second Example shows how to set calendar permission for a particular user to Editor this example looks like
- $MailboxName = "mailbox@domain.com"
- $credentials = New-Object System.Net.NetworkCredential("user@domain.com","Password#")
- $NewACLUser = "newacl@domain.com"
- $dllpath = "C:\Program Files\Microsoft\Exchange\Web Services\1.1\Microsoft.Exchange.WebServices.dll"
- [void][Reflection.Assembly]::LoadFile($dllpath)
- $Permission = [Microsoft.Exchange.WebServices.Data.FolderPermissionLevel]::Editor
- $service = New-Object Microsoft.Exchange.WebServices.Data.ExchangeService([Microsoft.Exchange.WebServices.Data.ExchangeVersion]::Exchange2010)
- $service.Credentials = $credentials
- $service.AutodiscoverUrl($MailboxName,{$true})
- $service.ImpersonatedUserId = new-object Microsoft.Exchange.WebServices.Data.ImpersonatedUserId([Microsoft.Exchange.WebServices.Data.ConnectingIdType]::SmtpAddress, $MailboxName);
- function addFolderPerm($folder){
- $existingperm = $null
- foreach($fperm in $folder.Permissions){
- if($fperm.UserId.StandardUser -eq $null){
- if ($fperm.UserId.PrimarySmtpAddress.ToLower() -eq $NewACLUser.ToLower()){
- $existingperm = $fperm
- }
- }
- }
- if($existingperm -ne $null){
- $folder.Permissions.Remove($existingperm)
- }
- $newfp = new-object Microsoft.Exchange.WebServices.Data.FolderPermission($NewACLUser,$Permission)
- $folder.Permissions.Add($newfp)
- $folder.Update()
- }
- "Checking : " + $MailboxName
- $folderidcnt = new-object Microsoft.Exchange.WebServices.Data.FolderId([Microsoft.Exchange.WebServices.Data.WellKnownFolderName]::Calendar,$MailboxName)
- $Calendar = [Microsoft.Exchange.WebServices.Data.Folder]::Bind($service,$folderidcnt)
- "Set Calendar Rights"
- addFolderPerm($Calendar)
- $sf1 = new-object Microsoft.Exchange.WebServices.Data.SearchFilter+IsEqualTo([Microsoft.Exchange.WebServices.Data.FolderSchema]::DisplayName,"Freebusy Data")
- $fvFolderView = New-Object Microsoft.Exchange.WebServices.Data.FolderView(1000)
- $fvFolderView.Traversal = [Microsoft.Exchange.WebServices.Data.FolderTraversal]::Shallow;
- $folderidRoot = new-object Microsoft.Exchange.WebServices.Data.FolderId([Microsoft.Exchange.WebServices.Data.WellKnownFolderName]::Root,$MailboxName)
- $fiResult = $Service.FindFolders($folderidRoot,$sf1,$fvFolderView)
- if($fiResult.Folders.Count -eq 1){
- "Set FreeBusy Rights"
- $Freebusyfld = $fiResult.Folders[0]
- $Freebusyfld.Load()
- addFolderPerm($Freebusyfld)
- }
4 comments:
I am using a similar method written in C# to set the permission on a calendar and freebusy data folders of a mailbox on an Exchange 2007 system. I am trying to set the permission for the default standard user to reviewer. However, when I look at the permissions set in Outlook 2007, it is not set to reviewer, it is shown as custom. If I set the permission to reviewer using Outlook, and and examine the permissions in code, they show up as reviewer for the calendar and editor for the freebusy data folder. If I replace with identical permissions and update in code, Outlook shows a custom permission. What am I doing wrong?
Thanks
Ade
With EWS the permission don't align for versions Outlook other the 2010 and greater. Its not a big deal really but if you want the permissions to align you need to use a custom permission type.
Cheers
Glen
Thanks for responding. I saw a previous post where you mentioned this and have used the custom permission type and set the relevant properties but it makes no difference. It appears the FolderPermission.ReadItems property is being read as None or ignored by Outlook 2007 even though I have set it to FullDetails. The value is still set to FullDetails when I read it back.
My eyes aren't what the used to be, but the code samples for the IPM_Subtree and Non_IPM_Subtree seem to be missing some trailing punctuation.
Post a Comment