E2K7: How to Change the Recipient Scope
When managing Exchange 2007, the recipient scope for Exchange Management Shell (EMS) and Exchange Management Console (EMC) defaults to the domain...
1 min read
cloudservuscom Sep 18, 2012 8:57:56 AM
There is a bug in the creation process for Dynamic Distribution Groups (DDG) in Exchange 2010. When you use the Exchange Management Shell to create a DDG and specify the Organizational Unit (OU) where the DDG should reside in Active Directory, you must also specify the –RecipientContainer to search for that DDG. Otherwise the DDG Recipient Container defaults to the OU where the DDG was created.
One of my customers came to me with this question. Here is a sample DDG that I created in my lab using the same PowerShell cmdlet that they were using. Apparently, this had worked for them in the past.
New-DynamicDistributionGroup -Name “Abbeville Office” -OrganizationalUnit “servusinc.com/servusinc/groups/DL/hidden” -RecipientFilter {((recipienttype -eq “usermailbox”) -and (office -eq “Abbeville Office”))}
Notice that the Recipient Container matches the OrganizationalUnit where it was created. You can also see this in the EMC. This can be changed here or through the Set-DynamicDistributionGroup cmdlet in PowerShell. You will also notice that Exchange 2010 adds some additional information to your query, for example, to exclude Arbitration Mailboxes, Discovery Mailboxes, etc.
You can audit all of the DDGs using the following cmdlet.
Get-DynamicDistributionGroup | select name,RecipientContainer,OrganizationalUnit
Here is the new cmdlet you should be using when creating DDGs:
New-DynamicDistributionGroup -Name “Abbeville Office” -OrganizationalUnit “servusinc.com/servusinc/groups/DL/hidden” –RecipientContainer “servusinc.com” -RecipientFilter {((recipienttype -eq “usermailbox”) -and (office -eq “Abbeville Office”))}
This will allow the DDG to search the entire directory for recipients that match your search criteria.
When managing Exchange 2007, the recipient scope for Exchange Management Shell (EMS) and Exchange Management Console (EMC) defaults to the domain...
1 min read
Microsoft announced the release of Exchange 2013 last fall, but this was not very useful to most of us, because there was no support for previous...
In Exchange 2010, the Client Access Servers now handle all client traffic now (MAPI, Outlook Anywhere, IMAP, POP, OWA, etc.). In Exchange 2007, you...