Non-universal distribution groups - cant remove or add new members

Hello,
We are running MS Exchange 2010 on a MS Windows 2008 R2 domain.
I have two mail non-universal distribution groups that I am unable to add or delete members when I go to that group from Exchange -> Recipient Config -> Distribution Group.
What should I do to resolve this?
Thanks.

Hi,
Mail-enabled non-universal groups were discontinued in Exchange Server 2007 and can exist only if they were migrated from Exchange 2003 or earlier versions of Exchange.
Did you migrate the two non-universal groups from earlier version?
If so, I recommend you convert them to universal and then add or remove members in EMC. You can use the
Set-Group <Group Name> -Universal command to convert to universal type.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Similar Messages

  • 500 Internal Server Error when trying to add new members

    My Workspace is working correctly but when I try to add new users, I get the following error:
    500 Internal Server Error
    Thanks
    Michel C.

    Hello Michel,
    How are you processing to add new members?
    You should be manager of your workspace and
    - go to http://beehiveonline.oracle.com
    - click on buttom "Create Group or Add New Members"
    - Choose your group
    - CLick on the link "Add new member"
    regards
    Fred

  • Adding external mail contacts to a distribution group seems to randomly add the user instead of the mail contact

    I've added a external mail contact for all my mailbox users because all the users have other jobs and other external email addresses.  Since these users don't normally log on to my domain to get email, I need to create a distribution list with all their
    external email addresses.  I've scripted the creation of all the external mail contacts, from the mailbox users and I use AD's Notes field to contain the users external address. When using add-DistributionGroupMember and supplying the external mail
    contact email address as the "-Member" param, about half of the time the users mailbox user gets added to the group instead of the external contact.  I don't see any arguments to tell add-DistributionGroupMember to use only mail contacts.
    1) I don't even know how it's finding the mailbox user because I'm supplying an external email address which is only in the external mail contact.
    2) Some members of the group are correctly added as external contacts, some are mailbox users.
    3) I only want the external mail contacts in the group
    If it helps, here's the line that I use to add members to the group. I've tried mail enabling the mail contacts, no help...
    Add-DistributionGroupMember–identity“AltEveryone”–member(get-QADuser$_.Name).Notes 
    Thanks for any help.

    You should ask questions like this in the Exchange forum.  It is not a scripting question but is a product behavior question.
    You cannot add an external contact without first creating the contact first.
    ¯\_(ツ)_/¯

  • Send Emails to Distribution Group

    Hi All,
    I have a scenario where we need to create one distribution group and 4 users in that distribution group. There are almost 70 companies who will send email to this distribution group.
    Now i want to achieve below goals,
    1) lets support i create an distribution group [email protected] and add 4 members in this distribution group.
    user1, user2, user3,user4
    2) If Company A send email to [email protected] only user1 & user2 will receive that email.
    3) If Compnay B send email to [email protected] only user3 & user4 will receive that email.
    Is there any possibility to achieve this goal i am using Exchange 2010 with Microsoft Forefront Online Protection.
    Thanks & Regards,
    Zeeshan Butt

    Hi Zeeshan Butt,
    Agree with the above suggestion, transport rule can achieve your requirement.
    The sender address matches(the sender’s domain is)
    The recipient address matches [email protected]
    Redirect the message to user3 & user4
    Here are some references you can refer to:
    Transport Rule Predicates:
    http://technet.microsoft.com/en-us/library/dd638183(v=exchg.150).aspx
    Transport Rule Actions:
    http://technet.microsoft.com/en-us/library/aa998315(v=exchg.150).aspx
    Manage Transport Rules:
    http://technet.microsoft.com/en-us/library/jj657505(v=exchg.150).aspx
    If you have any question, please feel free to let me know.
    Thanks,
    Angela
    Angela Shi
    TechNet Community Support

  • Question about adding Distribution Groups to Lync 2013 clients

    Hello Everybody,
       Hopefully somebody can assist me with this issue. I created a Universal Distribution Group within our domain which consists of about 75 people. I logged onto the lync server and ran Update-CsAddressBook waited for it to complete and then
    followed Terence Luk guide to force the lync 2013 client update http://terenceluk.blogspot.com/2013/02/forcing-lync-2013-client-to-download.html However
    even after the update has completed I am unable to locate this group in the lync client any suggestions would be greatly appreciated. 

    Hi,
    Please type the complete sip address to search it.
    If the issue persists, please remove lync profile and sign in again.
    Kent Huang
    TechNet Community Support

  • Cannot add multiple members of a failover cluster to a DFSR replication group

    Server 2012 RTM. I have two physical servers, in two separate data centers 35 miles apart, with a GbE link over metro fibre between them. Both have a large (10TB+) local RAID storage arrays, but given the physical separation there is no physical shared storage.
    The hosts need to be in a Windows failover cluster (WSFC), so that I can run high-availability VMs and SQL Availability Groups across these two hosts for HA and DR. VM and SQL app data storage is using a SOFS (scale out file server) network share on separate
    servers.
    I need to be able to use DFSR to replicate multi-TB user data file folders between the two local storage arrays on these two hosts for HA and DR. But when I try to add the second server to a DFSR replication group, I get the error:
    The specified member is part of a failover cluster that is already a member of the replication group. You cannot add multiple members for the same cluster to a replication group.
    I'm not clear why this has to be a restriction. I need to be able to replicate files somehow for HA & DR of the 10TB+ of file storage. I can't use a clustered file server for file storage, as I don't have any shared storage on these two servers. Likewise
    I can't run a HA single DFSR target for the same reason (no shared storage) - and in any case, this doesn't solve the problem of replicating files between the two hosts for HA & DR. DFSR is the solution for replicating files storage across servers with
    non-shared storage.
    Why would there be a restriction against using DFSR between multiple hosts in a cluster, so long as you are not trying to replicate folders in a shared storage target accessible to both hosts (which would obviously be a problem)? So long as you are not replicating
    folders in c:\ClusterStorage, there should be no conflict. 
    Is there a workaround or alternative solution?

    Yes, I read that series. But it doesn't address the issue. The article is about making a DFSR target highly available. That won't help me here.
    I need to be able to use DFSR to replicate files between two different servers, with those servers being in a WSFC for the purpose of providing other clustered services (Hyper-V, SQL availability groups, etc.). DFSR should not interfere with this, but it
    is being blocked between nodes in the same WSFC for a reason that is not clear to me.
    This is a valid use case and I can't see an alternative solution in the case where you only have two physical servers. Windows needs to be able to provide HA, DR, and replication of everything - VMs, SQL, and file folders. But it seems that this artificial
    barrier is causing us to need to choose either clustered services or DFSR between nodes. But I can't see any rationale to block DFSR between cluster nodes - especially those without shared storage.
    Perhaps this blanket block should be changed to a more selective block at the DFSR folder level, not the node level.

  • 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

  • Can't uninstall Exchange 2013 - (Distribution groups)

    I need help uninstalling Exchange 2013. The uninstaller fails with these 2 errors:
    This computer is responsible for expanding the membership of 1 distribution groups. These groups must be reassigned to another server before Setup can continue.
    This computer is responsible for expanding the membership of 1 dynamic distribution groups. These groups must be reassigned to another server before Setup can continue.
    I've gone so far as to disabling all distribution groups which removes its email properties and the uninstaller still fails.
    This is what happens in the eventlog:
    System.Management.Automation.ParseException: At line:1 char:67
    + Get-DynamicDistributionGroup | where {$_.ExpansionServer -eq '/o='s-Hertogenbosc ...
    +                                                                   ~~~~~~~~~~~~~
    Unexpected token 's-Hertogenbosch/ou=Exchange' in expression or statement.
    At line:1 char:175
    + ... s/cn=CADEXCDB13'}
    +                    ~~
    The string is missing the terminator: '.
    At line:1 char:38
    + Get-DynamicDistributionGroup | where {$_.ExpansionServer -eq '/o='s-Hertogenbosc ...
    +                                      ~
    Missing closing '}' in statement block.
       at System.Management.Automation.PowerShell.EndInvoke(IAsyncResult asyncResult)
       at Microsoft.Exchange.Configuration.MonadDataProvider.MonadPipelineProxy.ClosePipeline(MonadAsyncResult asyncResult)
    ] [ParentValue:"<NULL>"] [Thread:11] [Duration:00:00:00.0156248]
    I'm sure what happens here is the powershell commands looking at the distribution groups fail, because of our city name ('s-Hertogenbosch). Because of the apostrophe, the parameter is not passed successfully of this legacyExchangeDN. As this check fails,
    I believe the readiness check fails on these steps.
    This legacy administrative group name is still left from a 2003 -> 2010 -> 2013 migration.
    I've opened a Microsoft support request for this last week, but I thought someone might have dealt with this? I want to do a clean uninstall if possible.

    After I removed the distribution groups, I did restart the server.
    The problem is the the powershell script to check for existing distribution groups use a single quote to pass the server name to it. The server name contains a single quote itself so the parameter is not passed successfully.  If the powershell script
    used a double quote it would pass the parameter correctly.
    This works:
    Get-DistributionGroup | where ExpansionServer -eq "/o='s-Hertogenbosch/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=CADEXCDB13"
    This does not work:
    Get-DistributionGroup | where ExpansionServer -eq '/o='s-Hertogenbosch/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=CADEXCDB13'
    Do you see the difference? (Parameter is passed in a single or double quotation)

  • 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

  • Cannot assign an email address to SharePoint group (distribution groups)

    Hello,
    I configured incoming email awhile back in our SharePoint 2010 environment and it works great. I can assign an email address to a list and the necessary contact is created in AD in the OU I configured for incoming email and of course the item emailed in
    is added to the list.  However, if I try to assign an email address to a SharePoint group to create a distribution group, the following happens:
    The following error has occurred while attempting to contact the Directory Management Service: The request failed with HTTP status 401: Unauthorized.
    From what I've found on Technet and other resources, if incoming email works as expected, assign an email address to a group should work without issue but this obviously isn't the case.  I've dug around in the 14 hive and pretty much the same exact error
    is found there (with just a little more detail):
    System.Net.WebException: The request failed with HTTP status 401: Unauthorized.
    at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
    at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
    at Microsoft.SharePoint.DirectorySoap.SPDirectoryManagementProxy.CreateDistributionGroup(String Alias, String Name, String Description, String ContactCN, RequestInfo Info, DistributionGroupFlags Flags)
    at Microsoft.SharePoint.SPGroup.CreateDMS(String dlAlias, String friendlyName, String description, String[] members, String requestor, String justification, Int32& jobId)
    Any ideas what this could be?  I'd imagine the timer service account has the appropriate permission on the OU as it can create objects for lists with incoming email enabled without issue.

    For the issue with group members who are not added during the creation process ...
    I followed this Technet article : Configure
    incoming email for a SharePoint 2013 farm
    But in the paragraph "Configure AD DS to be used with Directory Management Service", I added
    delegation of control for the following common tasks :
    Create, delete and manage groups
    Modify the membership of a group
    The distribution group gets created in AD with members in SharePoint 2013 ! It should work with 2010 as well…
    PS : Do not forget to set up these rights, not only for the Central Administration Application pool Identity account, but for all
    your Web Applications!

  • Group owner distribution list cant add/remove member via outlook but via ecp work fine

    Hi all,
    i user exchange server 2013 sp1 with domain contoler windows server 2008 R2.
    my end user have problem. When group owner want to add/remove member via outlook cant but via ecp work fine ?
    i try to folowing this article http://theucguy.net/group-owners-cannot-manage-distribution/ but not work.
    any ideas? please help
    thanks,

    Hi,
    Please share me the error message which is occurring when the group owner try to add or remove members.
    Note : Group owners cannot be as a group and it should be an individual member.
    Please execute the below mentioned command and let me know the status .
    Get-DistributionGroup –ID “DistributionGroupName”
    | Set-DistributionGroup –ForceUpgrade
    Execute the above mentioned command and check.
    Regards
    S.Nithyanandham
    Thanks & Regards S.Nithyanandham

  • Can't add or remove members from an exchange 2010 distribution group

    Hello.
    i have exchange 2010 SP1. When i connect to the server with administrator login in the EMC, i can't add or remove members from distribution group. I don t understand why because i am admin. I have this error : "You
    do not have sufficient permissions. This operation can be performed by a group leader"
    how i can change this. I wan t only admin can edit members group
    hanks for help

    Hi,
    If you have checked the permission, I suggest you checking the Membership Approval configuration.
    1. Closed the option “owner approval is required to join the group”
    2. Open the option “anyone can leave this group without being approved by the group owners”
    To do this, follow the details at
    http://technet.microsoft.com/en-us/library/bb125178.aspx
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • Can not edit mail non-universal group

    Hi all,
    After moving from Exchange 2003 to Exchange 2010, the previous distribution groups become mail non-universal groups and greyed out.  i can not edit them anymore.
    Some DGs contains some distribution groups or secutiry groups.
    I can not create  nested distribution groups anymore in Exchange 2010.
    How can I make them not greyout and I am ble to edit them?
    Thank you.

    Ok.
    So I’d use the code above and run it a couple of times, just it will error groups with group membership but the first pass will change the scope of the child group and the second should change the scope of the parent group. This is a lazy approach
    but I want to get you the code to create the DG’s ;o)
    Once you have your groups at Universal level you can make DG’s
    I use the code below to batch create DG's with prefixed names or email addresses
    Import-Module ActiveDirectory
    Add-PSSnapin Microsoft.Exchange.Management.PowerShell.E2010
    Connect-ExchangeServer -auto
    $GroupsWithOutEmails = @(Get-ADGroup -Filter {(mail -notlike "*")} -SearchBase 'OU=Staff,OU=Groups,OU=Live,DC=domain,DC=co,DC=uk' -Properties mail )
    ForEach ($GroupsWithOutEmail in $GroupsWithOutEmails){
    $Alias = $GroupsWithOutEmail.Name.Replace(" ","")
    $SimpleName = $Alias.Replace("_","")
    $Identity = $GroupsWithOutEmail.DistinguishedName
    $PrettyName = "StaffGroup - All " + $GroupsWithOutEmail.Name + " Staff"
    $PrettyeMailAddress = "SMTP:StaffGroup_" + $Alias + "@domain.co.uk"
    Write-Host $Alias $Identity $PrettyName $PrettyeMailAddress
    Enable-DistributionGroup -Identity $Identity -Alias $Alias
    Set-DistributionGroup -Identity $Identity -DisplayName $PrettyName -EmailAddressPolicyEnabled $false -EmailAddresses $PrettyeMailAddress -SimpleDisplayName $SimpleName
    There's some code in there to get around some of our groups which had "_" in them and Exchange didn't like. If you just want enalbe the groups as DG's then remove the "Set-DistributionGroup" line
    Is that any help?
    J

  • Can't add a mail enabled public folder to allowed senders on a mail universal security group in Exchange 2010

    Hello,
    I'm trying to allow a mail enabled public folder permissions to send to a mail universal security group. In the past if I wanted to add a PF as an allowed sender I would do it via the AuthOrig setting on that group using adsiedit.  I just noticed today
    that if I add the PFs DN to that attribute of the group, nothing happens.  No matter how long I wait the PF never shows up under the allowed senders list on the group. If you try and send as the PF you get a bounce about not being allowed to send to that
    group.  If I go back into AD and check, the PF is still listed under the AuthOrig attribute.  I tried this on a few different groups and with a few different PF and I'm stumped.  I think the last time I had to update this setting on a group
    was before I installed roll-up 5 for SP3. 
    If I do the same test with a user, it works as it should and they show up in the allowed senders list.  
    If I take a group that isn't restricted to specific senders and add a PF DN to the AuthOrig attribute of the group, the button in the message delivery restrictions for that group in the EMC will change from all senders to only senders in the following list,
    but the PF wont be listed in the box of allowed senders.  If I remove it from the AuthOrig attribute the group will change back to allow all senders.  It's really weird, so any help or light you can shed on this would be greatly appreciated. 
    -Mark

    Hello,
    I check many threads and articles, but there is no related information to verify the issue.
    If your purpose is that adding a mail-enabled public folder to allowed senders on a distribution group, there is a workaround method. You can create a new distribution group, and then add the public folder to the new distribution group, and add
    the new distribution group to the Only senders in the following list field of the target distribution group.
    Here is an article for your reference.
    http://support.microsoft.com/kb/2746885
    Cara Chen
    TechNet Community Support

  • Office 365 - Add single external sender to internal distribution group

    You may be able to do this by adding the external email address as a contact in exchange, I'm not sure though just an idea, I have never tried this.

    Similar to this question:
    http://community.spiceworks.com/topic/452106-problems-with-office365-distribution-group but in my case I have a vip asking me to allow him to send email to any group from his personal email address, but still restrict all other external senders.Office 365 allows me to universally say let external users send, or restrict by sender and I can add everyone in my organization manually.What is the best way to do this? Can I add him as a 'sender' after making him a mail contact and then add our 'everyone' distribution list to the allowed senders to get everyone else in the organization approved?
    This topic first appeared in the Spiceworks Community

Maybe you are looking for