Distribution Group to Mailbox conversion

Hi
Our Marketing departments has a couple of DL's (static, not Dynamic) that they use for people to communicate with them. Examples are:
[email protected]
[email protected]
etc
They would like these DL's converted into mailboxes now rather than DL's. But - they want to minimise any downtime where people sending to these DL's would get a rejected/ non-deliverable message.
We have AD sites and Exchange servers in USA, Europe and Asia, and these DL's receive emails from all over.
Is there a recommendation for the quickest and most efficient way to do this?
We are running Exchange 2007 SP2 and AD 2003.

Hi All, <o:p></o:p>
Just wondering if there was any progress with this?<o:p></o:p>
@Rich , while your solution is more than acceptable, in our case, we're required to lose the distribution list completely and provide a user mailbox
that they can send / receive from. While we can delete the existing distribution group and once the changes have propagated, simply create a mailbox using the same SMTP address, it means that when users send emails to the existing cached address they have
stored in outlook they will receive a NDR. It will require them to delete the cached address before they can send to this address again.<o:p></o:p>
Are there any specific attributes that can be copied/migrated over to avoid causing the mass disruption? <o:p></o:p>
We're running Exchange 2010. <o:p></o:p>
Regards,<o:p></o:p>

Similar Messages

One shared mailbox with multiple distribution groups connected and the sent items folder - how to configure?

Hi!
I have been struggling for a while now with the following issue.
For starters:
We are using exchange 2010 in combination with outlook 2013 on client computers.
Cause of the limitations concerning the number of mailboxes in outlook im looking for a solution to receive and reply
to multiple aliasses. So i did the following:
1. Configured one shared mailbox.
2. Configured multiple distribution groups
3. made the shared mailbox a member of the distribution groups
4. Configured full access and send as permissions for myself on the shared mailbox ( testing )
5. Gave send as permissions to the shared mailbox in Active directory.
6. Logged in to OWA to setup rules for the shared mailbox.
I now receive emails from all connected distribution groups in the shared mailbox and also in the right folder.
I do however have to select the proper from address when i reply to an email.
the email sent by the main SMTP of the shared mailbox is placed into the sent folder of the shared mailbox.
I setup the senddelagate blabla in register.....
When i sent an email as one of the connected distribution groups it fails to put the sent item in the sent items folder of the shared mailbox. The email is sent using the proper address but placed in the sent folder of my main account.
I want this emails to end up in the sent items folder of the shared mailbox. Or even better, in a sent items folder for each of the addresses.
Any suggestions ?
Thanks in advance!

Hi,
As what
Rajkumar says, sending as a shared mailbox(full access permission) will put the email in the sent item of shared mailbox. But it cannot be located in the “sent item” of a distribution group. Because
it is a distribution group instead of a enabled user mailbox.
According to your further description, I understand that the reason why you configure that is some users reached the
limitation about the number of Exchange accounts you can include in the same Outlook profile. Is it rights? If I misunderstand, please point it out.
By default, user can only add 10 Exchange accounts to the same profile. You can customize the limit to the number Exchange accounts in the same profile using the following registry data:
Key: HKEY_CURRENT_USER\software\policies\Microsoft\exchange
DWORD: MaxNumExchange
Value: integer value starting at 1 (default = 10 if DWORD is missing)
http://blogs.technet.com/b/outlooking/archive/2012/12/24/clarification-on-outlook-2010-and-additional-exchange-account-supportability.aspx
Hope it helps.
Thanks,
Winnie Liang
TechNet Community Support

Looking for Script Exchange-2007: Import-Mailbox Calendar Folder on multiple mailboxes {Distribution Group}

Hi,
I'm looking for a PowerShell script which will import a Calendar events into student's mailbox (Calendar). Those students are located in a distribution group and I would like to target the distribution group; I'm trying to simulate what I want to achieve
in the below code example, I would appreciate if anyone jump in and advise.
$Users = Import-Csv C:\users.csv | ForEach-Object{Get-DistributionGroup -Identity SC-1213} | Import-Mailbox -Identity $Users -PSTFolderPath c:\Calendar.pst -IncludeFolders '\Calendar' -StartDate -EndDate
Much appreciated..
Hussain

The logic doesn't work unless you are using StartDate and EndDate for the period when you change the item. As I said above, StartDate and EndDate are not the times when the meeting starts and ends - they are the times that the item was either added
or modified in the mailbox. Your filter was trying to pull items that were in the future.
And as I also said above, if you import a modified item, the original is
not going to be updated. You will have a duplicate meeting
on the calendar. You would have to remove the original
and import the updated item if this was how you wished to manage the updates. This is not nearly as effective as
sending meeting requests and updating those meetings.
For example, if we do things the way you are doing them, and we add a "Student Appreciation Bonfire" meeting to the calendar for April 12 at "The Quad", we would do the following:
On February 1, you get information for the meeting that needs to be imported
You create this new meeting in the PST calendar - "Student Appreciation Bonfire"; Date April 12, start 8:00 AM, end 12:00 noon; Location The Quad
You import the PST into everyone's calendar
You receive a note on March 12 saying the venue has changed to The River Beach, so you update this meeting in your PST
Since there are other calendar items in the PST, you import the update using StartDate of March 12 and EndDate of March 13 - the date that you changed the item, not the date the item occurs
At this point, all users have two meetings on their calendar - the original and the update
If, instead of doing it this way, you create a Student Actvities Calendar mailbox, you would handle it this way:
On February 1, you get information for the meeting that needs to be imported
You create this new meeting in the Corporate calendar - "Student Appreciation Bonfire"; Date April 12, start 8:00 AM, end 12:00 noon; Location The Quad
You invite everyone to the meeting
You receive a note on March 12 saying the venue has changed to The River Beach, so you update this meeting in that calendar and send out the update
At this point, all users have only the one meeting on their calendar - the update
Using the PST as the source for the meetings would work only for items that
will not be changed - holidays are a good example.

Single Mailbox receiving 432-4.3.2 STOREDRV; mailbox server is too busy error emailing distribution group

I have a user who is trying to email a distribution group with approximately 185 recipients, 183 internal, and 2 external.
The user is recieving message delayed/pending for some (but not all) of the recipients. Approximately 15 recipients have recieved the mail including the external recipients and did so shortly after the mail was sent, however, 168 recipients have not recieved
the email and when I search for the mail in Message Tracking on the server, the pending recipients have the following error:
Submitted
04/12/2013 11:56 BTSDCAEXCMDB02.one.local
The message was submitted to btsdcaexccas02.one.local.
Group Expanded
04/12/2013 11:56 btsdcaexccas02.one.local
The list of members of the group "All TCP Users" was expanded so that the message can be delivered to each recipient.
Pending
04/12/2013 11:56 btsdcaexccas02.one.local
The message has been queued on server 'btsdcaexccas02.one.local' since 04/12/2013 11:56:48 (UTC) Dublin, Edinburgh, Lisbon, London. The last attempt to send the message was at 05/12/2013 12:08:22 (UTC) Dublin, Edinburgh, Lisbon, London and generated the error
'432-4.3.2 STOREDRV; mailbox server is too busy 432 4.3.2 STOREDRV.Deliver.Exception:StorageTransientException.MapiExceptionNotEnoughMemory; Failed to process message due to a transient exception with message Cannot set search criteria in SearchFolder. Try
using fewer keywords at the same time, reducing the number of users in the From, To, Cc, and Bcc fields, and reducing the number of mailboxes that are searched at the same time. 16.55847:42000000, 17.43559:0000000090020000000000000000000000000000, 255.23226:2B0A0000,
255.27962:30000000, 255.17082:F0030000, 0.27745:80030400, 4.21921:F0030000, 255.27962:FA000000, 255.1494:00000000, 255.1238:31000000, 4.7155:F0030000, 4.7155:F0030000, 4.7155:F0030000, 4.7155:F0030000, 4.7155:F0030000, 4.7155:F0030000, 4.7155:F0030000, 4.7155:F0030000,
4.7155:F0030000, 4.7155:F0030000, 4.7155:F0030000, 4.7155:F0030000, 4.7155:F0030000, 4.7155:F0030000, 4.7155:F0030000, 4.7155:F0030000, 4.7155:F0030000, 4.7155:F0030000, 4.7155:F0030000, 4.7155:F0030000, 4.7155:F0030000, 4.7155:F0030000, 4.7155:F0030000, 4.7155:F0030000,
4.7155:F0030000, 4.7155:F0030000, 4.7155:F0030000, 4.6131:F0030000, 4.7728:F0030000, 0.59311:F0030000, 4.8112:F0030000, 255.1750:00000000, 0.26849:00000000, 255.21817:F0030000, 0.30353:00000000, 4.19089:F0030000, 0.18065:0E000000, 4.26257:F0030000'.
05/12/2013 12:08 btsdcaexccas02.one.local
Message delivery is taking longer than expected. There may be system delays. For more information, contact your helpdesk.
Can anyone help as to what is going on here? This only seems to be affecting a single user, and it is intermittent as some recipients received the email, whilst others have not.

Hi Leo,
From your description, I recommend you refer to the following blog to set the values of MaxMailboxDeliveryPerMdbConnections and RecipientThreadLimit.
Store Driver Fault Isolation Improvements in Exchange 2010 SP1
http://blogs.technet.com/b/exchange/archive/2011/04/11/store-driver-fault-isolation-improvements-in-exchange-2010-sp1.aspx
What's more, here is a thread for your reference.
4.3.2 432 STOREDRV.Deliver; recipient thread limit exceeded
http://social.technet.microsoft.com/Forums/exchange/en-US/3b097117-6eb7-4368-b45a-62a4cddf871b/432-432-storedrvdeliver-recipient-thread-limit-exceeded?forum=exchange2010
Hope it helps.
If there are any problems, please feel free to let me know.
Best regards,
Amy
Amy Wang
TechNet Community Support

Looking for good tool to report on unused Mailboxes, unused Distribution Groups, and unused Public Folders

I have evaluated the following products.
Quest (Dell) MessageStats
Enow
StealthAudit
StealthAudit looked to be the best as they also group like mailboxes with like permissions for Office 365 migrations, but this was by far the most expensive.
We are looking to clean up our environment to eventually migrate to Office 365. Any advice on a product that would report on unused Mailboxes, unused Distribution Groups, and unused Public Folders that would be great.
d

Hi,
In your case, you can use the following cmdlet to determine unused mailboxes. If a mailbox has never logged on, the Lastlogontime is empty.
Get-Mailbox|Get-MailboxStatistics |fl DisplayName,Lastlogontime
Use the cmdlet below to get publicfolder's last access time.
Get-PublicFolderStatistics |fl name,LastAccessTime
Get all distribution lists used over last 30 days.
Get-MessageTrackingLog -EventId Expand -ResultSize Unlimited |Sort-Object RelatedRecipientAddress | Group-Object RelatedRecipientAddress |Sort-Object Name | Select-Object @{label=”PrimarySmtpAddress”;expression={$_.Name}}, Count
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

Shared mailbox in distribution group

Hi,
I am trying to set up a set of shared mail boxes to be distributed to several mailboxes
eg [email protected] forwards to [email protected] + [email protected]
Struggling beginner using hosted exchange
Thanks in advance

Hi,
From your description, I would like to verify if you want to create a distribution group that have some shared mailboxes members. If I have misunderstood your concern, please let me know. What's more, I would like to verify if you use Exchange 2007.
In your case, you can use the following cmdlet to create these shared mailboxes one by one firstly.
New-Mailbox -Shared -Name "blabla"
Secondly, use the following cmdlet to create the distribution group.
New-DistributionGroup -Name "sales" -OrganizationalUnit "xxx/xxx"
Lastly, use EMC to add these shared mailboxes to the distribution group.
Hope my clarification can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

Can't manage distribution group from Outlook with Exchange 2010 or Exchange 2013 mailbox

Hi All,
In my environment we are using exchange 2010 that contains the distribution groups which has been migrated from exchange 2003 environment .On that one of the distribution group is having an problem for the user who had an access to manage DL'S via outlook
but he can't able to manage it.When we add the new user to manage same DL and the new user tries to manage the DL via outlook it happens without any issues.
issue occurs only for the user who has already have the manage access permission on the DL where the group was on exchange 2003 before migrated to exchange 2010.
Reffered blog : http://support2.microsoft.com/kb/2586832?wa=wsignin1.0
We have done all the settings defined on the above mentioned link but still we are facing the issue.
In addition to that , we have forcefully upgraded the DL too by using the below mentioned command.
set-distributiongroup -identity "name of the problematic DL" -forceupgrade
Please all of you provide your valuable suggestions to overcome this issue .
Error message :
Regards
S.Nithyanandham
Thanks S.Nithyanandham

Hi S.Nithyanandham,
From your description, I would like to verify if the problematic manager user is a member of security group. If yes, this issue will occur. In Exchange 2010, distribution groups can't be managed by groups, only individual users can manage groups. But in
Exchange 2003, it is possible to use groups to manage a distribution group.
For more information, here is a blog for your reference.
How to manage groups with groups in Exchange 2010
http://blogs.technet.com/b/exchange/archive/2011/05/04/how-to-manage-groups-with-groups-in-exchange-2010.aspx
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

Effective Permissions to send email to distribution group having "only senders in the following list"

Our environment is a mixed Exchange 2007 and Exchange 2010 server environment, still in transition (after 4 years). Users have Exchange 2007 mailboxes. A recent problem has been reported in a distribution group access model that has been working without
complaint for several years.
[email protected] has member John Doe ([email protected]), Jane Doe ([email protected]), "only senders in the following list" is set to GroupA
[email protected] has member Rob Smith ([email protected]), Diane Smith ([email protected]), "only senders in the following list" is set to GroupB
[email protected] has members GroupA, GroupB, "only senders in the following list" is set to GroupC
When designed, we thought that when [email protected] sends an email to [email protected] it would be resolved to the user members of GroupC and delivered to everyone ([email protected], [email protected], [email protected], [email protected]). (While
it seems unlikely, that this model has functioned for several years without experiencing this problem, it is conceivable that until recently [email protected] and [email protected] have with few exceptions always had the same membership. Recent changes in
our organizational model have caused this to have some exceptions, and may be the root cause of this problem.)
What we are experiencing is that users [email protected] and [email protected] receive the original email. Users [email protected], [email protected] do not receive the email. [email protected] receives an email "Undeliverable: test
Delivery has failed to these recipients or distribution lists:
[email protected]
Your message wasn't delivered because of security policies. Microsoft will not try to redeliver this message for you. Please provide the following diagnostic text to your system administrator. Sent by Microsoft Exchange Server 2007.
Diagnostic information for administrators
Generating server: mail3.domain.com
[email protected]
#550 5.7.1 RESOLVER.RST.NotAuthorized; not authorized ##
Original message headers:
Received: from MAIL7.domain.com ([::1]) by mail3.domain.com ([::1]) with
mapi; Mon 9 Mar 2015 07:00:30 -500
Content-Type: application/ms-tnef;name="winmail.dat"
Content-Transfer-Encoding: binary
From: Jane Doe <[email protected]>
To: GroupC <[email protected]>
Date: Mon 9 Mar 2015 07:00:29 -500
Subject: test
What is the expected behavior?
Does Exchange resolve the "To" distribution group to member mailboxes for delivery purposes, or does it walk the subordinate child groups and check security at each level?
Is this a configurable behavior that may have recently changed as we have a "new" Exchange Admin poking around?
Might this be related to the mixed Exchange 2007 / 2010 environment?
Is there a way to obtain "effective permissions" for delivery restrictions?
emc2

Hi,
From your description, I would like to verify if you have done some changes for GroupB distribution group. Ensure that "[email protected]" is added to the "accept list" in GroupB's message delivery
restrictions.
What's more, are GroupA GroupB and GroupC Exchange 2010 distribution groups?
Best regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Amy Wang
TechNet Community Support

Internal email delivery taking very long time (EMAIL WITH attachment sent to large distribution group)

Hi Fellows
I am facing an issue with Exchange 2010 SP3 (14.03.0123.003) environment. Internal email sent with attachment to an all employee or large-member distribution group chokes the queue on Hub Transport and takes from 7 to 15 minutes to deliver. during this
time period users's emails are also delayed because of transport queue. I am trying to diagnose the root cause for this. Your suggessions and insight might be helpful for me to get it over quickly.
2 x HT + CAS (WNLB)
2 x MBX (DAG)
UserBase: 5000+
Regards.
J.A

Hi,
Generally, a message that has a large attachment or many recipients takes longer for a Hub Transport server to process than a small message that's addressed to only one recipient.
In Exchange 2010, after a message is received by the Hub Transport server, the message is added to the Submission queue. Messages move from the Submission queue through the categorizer. When the message is categorized, a recipient's e-mail
address is resolved to an object in Active Directory. This query determines the mailbox associated with that e-mail address and which Mailbox server is hosting that mailbox.
For more information about Internal message Routing, please refer to the following link.
http://technet.microsoft.com/en-us/library/bb232193(v=exchg.141).aspx
In addition, Slow network bandwidth will effect email delivery. We can increase the network bandwidth to take a test. Low computer performance will also affect the delivery. If sending internal email without attachment to all employee or
large-member distribution group, will they take the same long time to deliver?
Best Regards.

How to get Exchange Distribution Groups in Mail on iPad / iPad 2

Hello...
Maybe I'm missing something, but for some reason, the distribution groups I create for myself in Exchange 2010 ( personal mailbox ) are NOT showing in Mail on my iPad. Is there something that I need to do in order for them to sync?
I appreciate any help someone can give!

just start started using Exchange Online and also discovered this. Shared mailboxes and distribution group doesn't work on iOS devices and also OSX Mail.App, unfortunatly.

Distribution group not showing up in Exchange 2007 GAL

Hello,
We have AD running on a 2003 R2 SP2 server
We have Exchange 2007 running on a 2003 R2 SP2 server on the same domain.
I put a distribution group (all staff) on the active directory server.    I can e-mail to [email protected] and it goes to everyone I put in that group no problem.   However if I do check name, allstaff isn't listed, I have to go to contacts and drop down to find that distribution group (under groups).   How do I get it into the global address list so it shows for anyone pressing alt K or checkname along with other members of our domain - I don't want them to have to drop down under the contacts item in outlook to go to groups to find it.
Thanks

Thanks - I don't think the regen of the address book is really the key but modifying the distribution group in AD after you create it in EMC.   I had regened the OAB a few times since last friday but the allstaff was only available under groups in outlook.   Maintenance runs every morning at 5AM and that didn't update the group into lookup in outlook.   It seems to be the broken AD interface between exchange 2007 and windows 2003.   You used to be able to see all exchange data for a user or group in AD however now part of it is in Exchange 2007 Management console and some is in AD users and computers.
THis is just one more item in my opinion along with the lack of gui control in exchange 2007 that displays the half baked creation that is Exchange 2007.   Is the next version of WIndows Server going to require all DOS commands like Exchange 2007 does to do any AD work?   Gussy it up with a fancy name like "POWERSHELL" but it is just another way of saying DOS to me.   Pretty sure PCs became more popular with GUI interfaces.    I used to be an MS FAN (not the same as fanboy who thinks they can do no wrong) but things at MS have taken a SERIOUS turn down hill as of late
Vista - incredibly bad performance - no such issue with WIndows 95, 98, 2000, XP - and then they claimed it was drivers, then it was third party apps such as AV or firewalls - 5 months later they finally admit as people set up boxes with all the extras turned off with identical hardware and the latest drivers - hmm XP blows the doors off vista for file copy performance - can't imagine why sales suck for business clients and Dell had to start selling XP again.
BTW - I tried their patch for performance - it actually decreased disk to disk performance on the same box while increasing performance by 20% in network copys however since network performance is up to 500% slower than XP that 20% increase doesn't really help enough to offset internal performance slow downs - here is a tip MS - strip out the DRM scanning and you'll get your performance back.
Exchange 2007 - ESM worked great in 2003, 2000.   2007 we bring you POWERSHELL known 20 years ago as DOS.   Much easier to write scripts like - ## AutoDisco for EWS
[array]$SCPCurrent = Get-ClientAccessServer
$autodiscoResponse = "<Autodiscover xmlns=`"http://schemas.microsoft.com/exchange/autodiscover/outlook/requestschema/2006`">"
`
+ " <Request>"`
+ " <EMailAddress>" + $siSIDToSearch.WindowsEmailAddress + "</EMailAddress>"`
+ " <AcceptableResponseSchema>http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a</AcceptableResponseSchema>"`
+ " </Request>"`
+ "</Autodiscover>"
$strRootURI = $SCPCurrent[0].AutoDiscoverServiceInternalUri.absoluteuri
$WDRequest = [System.Net.WebRequest]::Create($strRootURI)
$WDRequest.ContentType = "text/xml"
$WDRequest.Headers.Add("Translate", "F")
$WDRequest.Method = "Post"
$WDRequest.UseDefaultCredentials = $True
$bytes = [System.Text.Encoding]::UTF8.GetBytes($autodiscoResponse)
$WDRequest.ContentLength = $bytes.Length
$RequestStream = $WDRequest.GetRequestStream()
$RequestStream.Write($bytes, 0, $bytes.Length)
$RequestStream.Close()
$WDResponse = $WDRequest.GetResponse()
$ResponseStream = $WDResponse.GetResponseStream()
$ResponseXmlDoc = new-object System.Xml.XmlDocument
$ResponseXmlDoc.Load($ResponseStream)
$EWSNodes = @($ResponseXmlDoc.getElementsByTagName("ASUrl"))
if ($EWSNodes.length -ne 0){
$ewsURL = $EWSNodes[0].'#text'
than just clickin in Exchange System Manager and going to mailbox management like you had to in 2003.   Whew glad that trudgery is gone!   In just 20 lines I can do what I was forced to do in a couple of mouse clicks in the old version - happy days are finally here.
WM6 - the BT stack was horrible in PPC2003, WM5 it was still bad but we've made it intolerable in WM6 - and we've made sure you can't get in touch with anyone at MS to point out these issues.
Office 2007 - Gone are all those customizable menus that made your job easy - we've locked them down because we didn't have enough time to fix them after we scrapped our original ribbons interface - we tell you they are locked for security reasons but we'll bring it back as a new feature in the next version of Office.
Thanks for letting me dump on the *** coming from MS these days - if their surveys actually let you give open feedback it would be great but their surveys about products are more like -
Would you like to give feedback about VIsta?
Question 1 -
Do you think Vista is
a more colorful
b more intuitive
c more visually stimulating
Question 2
Do you think the menu bar
a Has better icons
b Has better fonts
c Looks more user friendly
A real question about my Vista experience would be
Question 1
What did you think was better about Vista
Question 2
What did you think needs fixing in Vista
Question 3
Any additional comments
MS is determined not to let in any info that might delay releases or improve their products.

Exchange 2010 Dynamic Distribution Group - RecipientContainer ignored

Maybe someone will be able to help me with this... I am trying to create DDGs for my organization but it seems the "RecipientContainer" is being ignored. I have reorganized AD to include a top level OU called "Active Employees"
and within that are sub-OUs for each department. I also have a top level OU for "Disabled Accounts" and users in those OUs are ending up on my DDG. Is this a known issue with Exchange 2010?
First I had created the DDG in EMC and everything looked good. I set the Recipient Container on the Filter tab by using the browse button and selecting mydomain.local\Active Employees, and then selected "Users with Exchange Mailboxes".
On the Conditions tab I left everything blank and when I clicked on Preview it returned the list of users I expected to see. After sending a test email and receiving an NDR from an email contact (not on the preview list) I realized something was
wrong.
At this point I found out how to query the group members using the shell and saw that all users in the entire domain were being put into the group. To resolve this I added a Condition for Company name and then tediously updated the field for each user
in AD. After querying the group from the shell again the results looked a little better - it was actually only pulling users with the correct "Company" in AD. The problem is it still seems to be ignoring the RecipientContainer parameter
and querying the entire domain instead of my Active Employees OU.
I have reproduced the same results whether creating the DDG from EMC or from the Shell. When I try to use the Set-DynamicDistributionGroup cmdlet to update the recipient container it warns me that the commad was successful but nothing has been modified.
This was supposed to be a simple solution for keeping our distribution groups up to date - maybe I should've known better...

Hello Dave,
Thanks for the post. Let me tell you how I was able to go ahead and resolve the issue in my lab.
I had created a OU called Enabled users
Then I created Two different Child Ou's : Disabledusersou1 and DisabledUsersou2
So if I open the ADUC my OU would look something like this
EnabledUsers
Disbaledusersou1
Disbaledusersou2
Now I Had created users on all the above Ou's. When I created a Dynamicdistributiongroup with the recipientcontainer as EnabledUsers, it picked up users even from Disabledusersou1 and Disabledusersou2. Then I set the
customattribute1 to test in the DynamicDistributiongroup.
Then I went ahead and ran the following command
Get-mailbox | {$_.Organizationalunit -like "domain.local\EnabledUsers"}
The above command listed only the users from the enabledusers Ou. Now the next step was to go ahead and add the customattribute1 to test on the Users in the EnabledUsers OU. So I ran the following command
Get-mailbox | {$_.Organizationalunit -like "domain.local\EnabledUsers"} | set-mailbox -customattribute1 test
After I ran the above command. I waited for the AD replication. Once the Ad was replicated, I went ahead and did a Preview in the DynamicDistributiongroup and only found users from the EnabledUsers.
I even confirmed by sending an email to the dynamicdistributiongroup with a delivery receipt. I got the receipt for all the users in the EnabledUsers OU.
Waiting to hear from you
Naveen V Microsoft Forum Specialist

Custom Distribution Group management role (manager excpeiton)

My organization is medium size with multiple support groups (15+) that each support a subset of users (350+). I want to create a management role that is scoped so each support group can manage the distribution groups in their respective OU space.
By manage I mean edit the group membership. I realize I can achieve this with AD permissions but I’d like to achieve this in a way that leverages RBAC so the support groups can use OWA. I also want to leverage RBAC\OWA because not all my support groups are
technical, some are office admins. Anyways, below is what I’ve tried in my lab scoped to one of my support groups.
Using the cmdlets below I’ve created a custom management scope, role and group. However, this does not work. While it lets my sales support group view and edit some random attributes on the group, it fails when they try to edit the group membership. In other
words, they can logon to OWA, click options\see all options\manage your organization\distribution groups\open the group\edit description etc. but when they select “Add…” under membership then select the user and hit ok\save they get the error “you don’t have
sufficient permissions. this operation can only be performed by a manger of the group”.
New-ManagementScope -Name “Sales Support DG MScope” -RecipientRestrictionFilter {RecipientType -eq "MailUniversalSecurityGroup"} -RecipientRoot “lab.com/sales”
New-ManagementRole -name “Sales Support DG MRole” -Parent "Distribution Groups"
New-RoleGroup -name “Sales “Sales Support DG MGroup” -Roles "Sales Support DG MRole" -CustomRecipientWriteScope "Sales Support DG MScope"
When I do as the error asks (i.e. add my support user as a manager of the group via the EMC), then my support user is able to edit the group's membership in OWA. The problem with this solution is that it would require me to add my support users to my role
group “Sales Support DG MGroup” AND as a manager of the DG and every DG that is created down the line. Not ideal. Any ideas, some RBAC magic I’m missing?
Below confirms by scope.
Get-Group -OrganizationalUnit “lab.com/sales” | ?{$_.RecipientType -eq "MailUniversalSecurityGroup"}
Name DisplayName SamAccountName GroupType
distro1 distro1 distro1 Universal, SecurityEnabled
distro2 distro2 distro2 Universal, SecurityEnabled
distro3 distro3 distro3 Universal, SecurityEnabled
On a side note, I realize by sourcing my management role off of distribution groups gives me more cmdlets\access than my support group needs (see below). I’m first just trying to get it to work :).
Get-ManagementRole “Sales Support DG MRole” | Get-ManagementRoleEntry | select name
Name
Add-DistributionGroupMember
Disable-DistributionGroup
Enable-DistributionGroup
Get-ADServerSettings
Get-AcceptedDomain
Get-DistributionGroup
Get-DistributionGroupMember
Get-DomainController
Get-DynamicDistributionGroup
Get-Group
Get-MailUser
Get-Mailbox
Get-OrganizationalUnit
Get-Recipient
Get-ResourceConfig
Get-User
New-DistributionGroup
New-DynamicDistributionGroup
Remove-DistributionGroup
Remove-DistributionGroupMember
Remove-DynamicDistributionGroup
Set-ADServerSettings
Set-DistributionGroup
Set-DynamicDistributionGroup
Set-Group
Set-OrganizationConfig
Update-DistributionGroupMember
Write-AdminAuditLog

Hello,
I understand that you have create custom management scope for each group and assigned a custom role to it.
But whenever user try to edit (add/remove membership ) ,it shows errors "you dont have sufficient permissions". I face similar problem when we move from 2007 to 2010, 2010 by default disabled editing options for Dl membership.
You can enable it by Graphic mode or powershell. Would suggest that you have created custom role, you follow powershell mode. I had written a blog on that.
Check below link. http://exchange2010cmd.blogspot.de/
You have created new management role “Sales Support DG MRole”, but you need to assign this role to users/administrators in your case through role assignment policy.
You can either use existing default policy or create new policy and assign this management role to it.
Use below cmd: New-ManagementRoleAssignment -Role “Sales Support DG MRole” –Policy “Default Role Assignment Policy”
NOTE: If you are creating new policy , place that name instead of default policy name".
I recommend you continue with defalut policy. After this check with any admin, he should have rights to edit membership.
Now, regarding your second concern, that your custon role has to many role entries.
You can remove unwanted role entries.
Use this cmd: Get-ManagemenRoleEntry “Sales Support DG MRole\*” | where{ $_.name –like “Set-distributionGroup” } | remove-managementroleentry
Before linking management role to email policy, remove unwanted role entry from role.
I tried to explain it in easy way, but still it is not understood, write back to me. I am new to technet forum, I started few days back replying to questions. If you get your answer,dont forget to propose it as answer.

Cannot Send Mail to Distribution Group

We are running Exchange 2013 and have a problem where users are getting NDR reports when trying to send mail with a small attachment a Universal Distribution Group. The message received back is:
Delivery has failed to these recipients or groups:
_Group ([email protected])
The recipient won't be able to receive this message because it's too large.
The maximum message size that's allowed is 2 MB. This message is 3 MB
Why are messages to distribution groups capped at 2MB and how can I increase it to at least 10?

Hi Will,
Check the distributiongroup maxreceivesize parameter. With Powershell.
Get-DistributionGroup -Name <Name> | FL
It can be changed using:
Set-DistributionGroup -Name <Name> -MaxReceiveSize XXXXX
It can also be changed in the Exchange Administreative Center here:
Recipients > Mailboxes > EditEdit icon > Mailbox features > Mail flow > Message size restrictions > View details > Received messages
You can Refer to this link for further Exchange 2013 Message size limits.
http://technet.microsoft.com/en-us/library/bb124345(v=exchg.150).aspx
All the best, Jesper Hassing - MCTS SCCM 2012 - MCSA 2012 Server - MCP

Create/Edit "Custom Attributes" in Dynamic Distribution Groups

Hi,
I wanna create a Dynamic Distribution Group based on the users "title" and "company".
I've noticed that there are 15 "Custom Attributes" that I can edit in someway, I guess via PowerShell?
So what is the easiest way to accomplice this?

Hi,
Agree with the above suggestion, you can also bulk change the custom attributes:
Get-Mailbox -ResultSize Unlimited -Database Execs | Set-Mailbox -CustomAttribute1 “title”
http://dougg.co.nz/2012/05/01/bulk-setting-exchange-2010-custom-attributes/
to Edit Custom Attributes：
get-mailbox -filter {customattribute1 -eq ""} | set-mailbox -customattribute1 = "<value>"
And here is a reference about Create/Edit "Custom Attributes" in Dynamic Distribution Groups：
http://windowsitpro.com/exchange-server-2010/exchange-2010-sp2-value-custom-attributes
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
sure that you completely understand the risk before retrieving any suggestions from the above link.
Best regards,
Angela Shi
TechNet Community Support

Distribution Group to Mailbox conversion

Similar Messages

Maybe you are looking for