Skip to main content

Manage full access permissions and commands on mailboxes in Exchange 2010

 Manage full access permissions on mailboxes in Exchange 2010





Just a couple of quick tips on how to manage full access permissions on mailboxes in Exchange 2010.



Grant permissions on a single mailbox
Use the following command to grant access to just one mailbox for a single user:
Add-MailboxPermission -Identity "" -User -AccessRights Fullaccess -InheritanceType all
Example:
Add-MailboxPermission -Identity "Test" -User Administrator -AccessRights Fullaccess -InheritanceType all


Grant permissions on all mailboxes
Use the following command to grant access to all mailboxes for a single user:
Get-Mailbox | Add-MailboxPermission -User -AccessRights Fullaccess -InheritanceType all
Example:
Get-Mailbox | Add-MailboxPermission -User Administrator -AccessRights Fullaccess -InheritanceType all
Note: In the screenshot below I received a message saying that Administrator already have access to the mailbox Test (Yellow text message).


Grant permissions on mailboxes using Where
We might as well add a where to the command while we are at it. With this command we grant access to all mailboxes in a specific OU for a single user:
Get-Mailbox | Where { $_.OrganizationalUnit –eq “” } | Add-MailboxPermission -User -AccessRights Fullaccess -InheritanceType all
Example:
Get-Mailbox | Where { $_.OrganizationalUnit –eq “sundis.local/Test/Users” } | Add-MailboxPermission -User Administrator -AccessRights Fullaccess -InheritanceType all


Remove permissions on a single mailbox
Quite simple, just change Add to Remove:
Remove-MailboxPermission -Identity "" -User -AccessRights Fullaccess -InheritanceType all
Example:
Remove-MailboxPermission -Identity "Test" -User Administrator -AccessRights Fullaccess -InheritanceType all


Remove permissions on all mailboxes
Well you have probably figured this one out already, but I will show it to you anyway:
Get-Mailbox | Remove-MailboxPermission -User -AccessRights Fullaccess -InheritanceType all
Example:
Get-Mailbox | Remove-MailboxPermission -User Administrator -AccessRights Fullaccess -InheritanceType all
Note: As you can se below, using this command will remove the users full access to its own mailbox. That is not good, this command should be used with care…




Thanks for reading, I hope that you found it useful.

Comments

Post a Comment

Popular posts from this blog

Calculate how much data can be transferred in 24 hours based on link speed in data center

  In case you are planning for migration via DIA or IPVPN link and as example you have 200Mb stable speed so you could calculate using the below formula. (( 200Mb /8)x60x60x24) /1024/1024 = 2TB /per day In case you have different speed you could replace the 200Mb by any rate to calculate as example below. (( 5 00Mb /8)x60x60x24) /1024/1024 =  5.15TB  /per day So approximate each 100Mb would allow around 1TB per day.
Post a Comment
Read more

Integration with vCloud Director failing after NSXT upgrade to 4.1.2.0 certificate expired

  Issue Clarification: after upgrade from 3.1.3 to 4.1.2.0 observed certificate to be expired related to various internal services.   Issue Verification: after Upgrade from 3.1.3 to 4.1.2.0 observed certificate to be expired related to various internal services.   Root Cause Identification: >>we confirmed the issue to be related to the below KB NSX alarms indicating certificates have expired or are expiring (94898)   Root Cause Justification:   There are two main factors that can contribute to this behaviour: NSX Managers have many certificates for internal services. In version NSX 3.2.1, Cluster Boot Manager (CBM) service certificates were incorrectly given a validity period of 825 days instead of 100 years. This was corrected to 100 years in NSX 3.2.3. However any environment originally installed on NSX 3.2.1 will have the internal CBM Corfu certs expire after 825 regardless of upgrade to the fixed version or not. On NSX-T 3.2.x interna...
Post a Comment
Read more

Recreating a missing VMFS datastore partition in VMware vSphere 5.x and 6.x

    Symptoms A datastore has become inaccessible. A VMFS partition table is missing.   Purpose The partition table is required only during a rescan. This means that the datastore may become inaccessible on a host during a rescan if the VMFS partition was deleted after the last rescan. The partition table is physically located on the LUN, so all vSphere hosts that have access to this LUN can see the change has taken place. However, only the hosts that do a rescan will be affected.   This article provides information on: Determining whether this is the same problem Resolving the problem   Cause This issue occurs because the VMFS partition can be deleted by deleting the datastore from the vSphere Client. This is prevented by the software, if the datastore is in use. It can also happen if a physical server has access to the LUN on the SAN and does an install, for example.   Resolution To resolve this issue: Run the  partedUtil  command on the host wit...
1 comment
Read more