Exchangepedia Blog is read by visitors from all 50 US States and 150 countries world-wide
In Exchange Server 2007, recipients are managed from the Exchange console or shell. The Exchange console does not show security tab for a recipient.
You can still use AD Users & Computers console to modify permissions on a recipient, as the documentation suggests ["How to Grant Send As Permissions for a Mailbox"] - and in this case, assign the Send As permission. In ADUC | select recipient | Properties | Security tab.
You can use the Exchange shell to assign SendAs right (e.g. on a Distribution Group) to a user:
11/29/2007:
Exchange Server 2007 SP1 includes a Manage Send As Permissions wizard, similar to the Full Mailbox Access wizard found in the RTM version.
1. In EMC, right-click a recipient | select Manage Send As Permission
2. In the Managed Send As Permission wizard, click the Add button to add the recipient which needs to be assigned Send As permission on the selected recipient
You can still use AD Users & Computers console to modify permissions on a recipient, as the documentation suggests ["How to Grant Send As Permissions for a Mailbox"] - and in this case, assign the Send As permission. In ADUC | select recipient | Properties | Security tab.
You can use the Exchange shell to assign SendAs right (e.g. on a Distribution Group) to a user:
Add-AdPermission "Group Name" -user "User Name" -AccessRights
extendedright -ExtendedRights "send as"
11/29/2007:
Exchange Server 2007 SP1 includes a Manage Send As Permissions wizard, similar to the Full Mailbox Access wizard found in the RTM version.
1. In EMC, right-click a recipient | select Manage Send As Permission
2. In the Managed Send As Permission wizard, click the Add button to add the recipient which needs to be assigned Send As permission on the selected recipient
Labels: Administration, Exchange Server 2007, Exchange Shell, Mailbox, Security
5 Comments:
THis command worked great for me, thanks! I am, however, having difficulty piping users with this command... I.E... Get-user -organizationalunit NAMEOFOU | add-adpermission ....etc. It returns an error saying the command is not able to be pipelined. Do you know the correct usage of this command?
I had the same problem, I don't want to do one at a time, I want to add the sendas permission on a large group of users, I tried the get-user and then pipe add-adpermission but got an error
You need to do a Get-Mailbox instead of Get-User. You can constrain that based on -OrganizationalUnit or -Server parameters.
Alternatively, you can do this for members of a Distribution Group - Get-DistributionGroupMember "Dist Group Name"
You can further constrain Dist Group members to a particular recipient type:
Get-DistributionGroupMember "DG Name" | where {$_.RecipientType -eq "UserMailbox"}
Pipe the above command to Add-ADPermission.
how to take back "send as" permisson on org. unit?
Once this is all added in, it takes up to two hours for it to update on the server cache. Is there a way to force this?
Post a Comment
Links to this post:
Create a Link
<< Home