Distribution Groups issue in Exchange Server 2013

Hello guys,

I have MS Exchange 2013 Server with thousands and more users with email addresses already created.

My company have a lot of branch offices and it is a necessity for us to create distribution group per branch in our Exchange server.
Fortunately, it is very easy for me to create distribution group per branch office, but there is a frequent user rotations from one branch office to another, from another to another and so on.. thus we have a bunch of tasks (every week there is a lot of user rotations) to remove relative users from one group and then add to another group.
Is there some feature or service in the Exchange Server to process this kind of tasks automatically, not manually.
Do you have a thought what will be the more precise solution for that issue.

What about this kind of solution that it will be Distribution lists to create in Exchange server ..? - (Despite everything, I think that there will not be the right decision)

Need your opinions

Thanks in advance,




  • Edited by GMG888 21 hours 47 minutes ago
February 3rd, 2015 9:04am

I would suggest using Dynamic DIstribution Groups.  These are groups where members are added or removed based on a query.  For example, if you have an Active Directory Attribute populated with the Office and you put a policy in place to change that value when users switch office locations, you wouldn't have to change the Distribution group to reflect the user office change.  If you want me to expand a little more I can but maybe if you try creating a dynamic group yourself to see the attributes to use, it may make sense after seeing it.

Thanks,

Jason

Free Windows Admin Tool Kit Click here and download it now
February 3rd, 2015 10:24am

Hi,

As Jason suggested, you can create a dynamic distribution group to achieve it, using the cmdlet below.

New-DynamicDistributionGroup -Name xxx -IncludedRecipients AllRecipients

For your reference:

Use a cmdlet to Create Dynamic Distribution Groups (Note: Though it is Exchange 2010, it also applies to Exchange 2013 about this issue.)

https://technet.microsoft.com/en-us/magazine/ff431730.aspx

Hope this can be helpful to you.

Best regards,

February 4th, 2015 4:40am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics