Missing Manage Send as Permissions option in Exchange Management Console

In Exchange 2010 RBAC allows you to grant permissions to Helpdesk or Administrators in a very granular manner.  There are built in groups that one can use for Helpdesk and Recipient Management that one can add User Support team to be able to manage permissions on a mailbox, create and delete mailbox, mail enable public folders, manage permissions on mailbox etc.

Issue

I used the built in groups to grant our user support team permissions that they required. All works fine but User Support was unable to see or grant send as permissions. When any of them right click a mailbox they don’t even see an option to view or change send as permissions. They do see an option for managing full mailbox permissions.

Resolution

In Toolbox of EMC go to “Role Based Access Control (RBAC) User Editor”

Double click Recipient Management Role and in the Roles add “Active Directory Permissions” click on Save.

How to manage Distribution Lists with groups in Exchange 2010

Issue

When User1 tries to add a new member to the DistributionGroup1 distribution group, she gets this error:

Changes to the distribution group list membership could not be saved. You do not have sufficient permissions to perform this operation on this object.

Figure 1: User gets a permissions error when trying ot modifying a distribution group membership in Microsoft Outlook

In the past, User1 was able to add/remove members to the distribution group by using Outlook and didn’t need to call the help desk for assistance. What has changed?

You know that you had previously configured SecurityGroup1 to be able to manage this distribution group. Did someone make a change to User1’s security group membership? You look at ADUC first. No change – the user’s still a member of SecurityGroup1.

Figure 2: The user’s still a member of the security group that’s configured to manage the distribution group

Next, you check the distribution group configuration in ADUC to verify that DistributionGroup1 is still being managed by SecurityGroup1.

Figure 3: The user’s still a member of the security group that’s configured to manage the distribution group

Okay, so what’s the deal here? You know you recently migrated to Exchange 2010. So you take a look at DistributionGroup1 in EMC (which reveals that it’s managed by SecurityGroup1, but also displays an ‘Object Not Found’ error).

Figure 4: EMC displays the security group with an ‘Object not found’ error

Why is Exchange 2010 doing this?

This behavior is by design. In Exchange 2010, distribution groups can’t be managed by groups – only individual users can manage groups. So it’s possible that using Exchange 2003, you used groups to manage a distribution group. Group ownership was handled at a different level. Now that these mailboxes have been moved to Exchange 2010, members of these groups can’t modify the group.

So are there any workarounds?

We’ve created a script to work around this limitation. Download Set-DistributionGroupOwners.ps1 from the Script Center.

The script will allow you to simulate a group having ownership of a distribution group in Exchange 2010. The script can be run in three different modes depending on the switches you pass.

1. Mode 1 – Set Ownership for a particular distribution group. Modifications to the ManagedBy attribute are not set at this time. It will simply modify a Custom Attribute to have the information needed later when the script sets the ManagedBy attribute.
2. Mode 2 – Modify the ManagedBy attribute of a specific distribution group so the members of either a security group or distribution group can manage it.
3. Mode 3 – Is designed to be run as a scheduled task and ensure individual members of a group have ownership of the Distribution Group which they are set to own. This mode is used if you prefer to automate the process and perhaps run it nightly to look for any changes to security group and distribution group membership.

Read More from the Source: http://msibrahim.wordpress.com/2011/05/08/how-to-manage-groups-with-groups-in-exchange-2010/

Couldn't find public folder–When Get-PublicFolderStatistics is run in Exchange 2010 SP1

 

When I tried the following cmdlet in EMS

Get-PublicFolder '\PublicfolderName' -Recurse | Get-PublicFolderStatistics

I got the following error

Couldn't find public folder "\PublicfolderName" on server "server.domain.org".
    + CategoryInfo          : InvalidData: (\PublicfolderName:PublicFolderIdParameter) [Get-PublicFolderStatistics], InvalidOperationException
    + FullyQualifiedErrorId : 773CD1AB,Microsoft.Exchange.Management.MapiTasks.GetPublicFolderStatistics

Couldn't find public folder "\PublicFolderName\subfolder" on server "server.domain.org".
    + CategoryInfo          : InvalidData: (\PublicFolderName\subfolder:PublicFolderIdParameter) [Get-PublicFolderStatistics], InvalidOperationException
    + FullyQualifiedErrorId : 773CD1AB,Microsoft.Exchange.Management.MapiTasks.GetPublicFolderStatistics

Solution

This seems to be bug (may be a feature :)

If you add the resultsize parameter to the cmdlet it works fine

Get-PublicFolder '\PublicfolderName' -Recurse | Get-PublicFolderStatistics –ResultSize unlimited

Installing Exchange 2007 SP2 Management Tools on Windows 7 SP1

We recently deployed Windows 7 SP1 64bit to all the IT staff and the user support team required Exchange Management Tools installed on their workstations.  I just asked them to go ahead and copy the installer on the local disk and fire up the installation as administrator and choose management tools in a custom installation. I was told that there was a compatibility  issue error while doing the installation.

Resolution

I installed the following features just to make sure that the perquisites are met.

• IIS 6 Management Console
• IIS 6 WMI Compatibility
• IIS Metabase and IIS 6 configuration Compatibility
• IIS Management Console

I tried the installation again as administrator and checked the compatibility mode to Vista SP2, got the following error.

So trusting in the good old restart trick I restarted and ran the same setup as administrator and compatibility mode (right click > Properties > Compatibility) Vista SP2. It worked like a charm!