Its sorta clear.. but this stood out the most.. My thought is the user should be able to set up a OUTLOOK 2013 people/contact list, share with others user wants included, and maintain member changes.
Why not just create the distribution list, have the requester set to the owner and then have THEM modify the list via Outlook / OWA? In theory they would just need the MyDistributionGroup RBAC role assigned to them, and also be the "Owner" of the list to make these changes (add / remove members). This is how most of my customers do it.. we usually just handle the initial setup and import of users into the group. From: [email protected] To: [email protected] Subject: [Exchange] Share a contact/people list OUTLOOK 2013 client Date: Thu, 21 Aug 2014 02:15:57 +0000 Greetings EXCHANGE 2010 SP3 U3 backend. OUTLOOK 2013 clients one WIN7. Doing my best to ask the question in an understandable manner - after reviewing a lot on GOOGLE searches – so sorry if not clear. We rarely get this type of request, so not something I have dealt with recently. User requests we set up a server side Distribution List and populate with specified users – which we do not support due to managing all the continued changes on a large dynamic campus. My thought is the user should be able to set up a OUTLOOK 2013 people/contact list, share with others user wants included, and maintain member changes. Even though I tried to contain my searches to OUTLOOK 2013 clients, the results often contain older information with previous versions. Hoping someone that has dealt with this can point me in the correct direction on how this has been handled to avoid ITS management of these lists. If you have specific user TID document links, etc. that works for your sites, that would help as well. Again, sorry for not being clear. Thanks for any help. Dana
