asked on
GAL DL - Add public folder DL to it
Gidday
I have a need to allow a user to administer a DL containing external email address, but would like to have that DL easily accessible to users, i.e. have it appear in the GAL.
Presently using Exchange 2003, but moving to Exchange 2013. Outlook Clients are 2007 and Up.
For the user administrated DL the two options I know of are;
- Either a Public Folder where the user can add/maintain a DL with the list of external email address
- create a user account and share out its 'Contacts' where again the user can administrator a DL within that Contact list.
However I am unable to get either of these to be added to a GAL DL.
How can I configure it so a user can add external email address to a list and it be easily accessed by all users?
Thanks for your suggestions
I have a need to allow a user to administer a DL containing external email address, but would like to have that DL easily accessible to users, i.e. have it appear in the GAL.
Presently using Exchange 2003, but moving to Exchange 2013. Outlook Clients are 2007 and Up.
For the user administrated DL the two options I know of are;
- Either a Public Folder where the user can add/maintain a DL with the list of external email address
- create a user account and share out its 'Contacts' where again the user can administrator a DL within that Contact list.
However I am unable to get either of these to be added to a GAL DL.
How can I configure it so a user can add external email address to a list and it be easily accessed by all users?
Thanks for your suggestions
OutlookExchange
Last Comment
Jamie McKillop
ASKER
Thanks jjmck,
That's what I thought from testing and reading, but thought I would ask just encase I missed something or someone had done this another way.
As I deal with small business, I have never had to delegate permissions for OU's.
I read somewhere that you can have an 'Auto Join' group which would pick up objects in an OU.
Based on that, is it create and then delegate one OU to a couple of 'Users' so they could maintain the contacts in that OU?
If that is possible, how would they run ADU&C to access that one OU. Can ASU&C be installed on a PC, run from a share (with a shortcut on the PC), would they need admin rights on the server or just access to the one OU.
As indicated above, I have not had to delegate permissions before, hence the questions.
thanks
That's what I thought from testing and reading, but thought I would ask just encase I missed something or someone had done this another way.
As I deal with small business, I have never had to delegate permissions for OU's.
I read somewhere that you can have an 'Auto Join' group which would pick up objects in an OU.
Based on that, is it create and then delegate one OU to a couple of 'Users' so they could maintain the contacts in that OU?
If that is possible, how would they run ADU&C to access that one OU. Can ASU&C be installed on a PC, run from a share (with a shortcut on the PC), would they need admin rights on the server or just access to the one OU.
As indicated above, I have not had to delegate permissions before, hence the questions.
thanks
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Hi JJ
Thanks for the quick reply.
I would have been looking at doing it through AD Users & Computers - so thank you for that correction.
I take it you know of no 3rd party utility that I could use to accomplish this while restricting the user?
Again thank you for you help.
BC
Thanks for the quick reply.
I would have been looking at doing it through AD Users & Computers - so thank you for that correction.
I take it you know of no 3rd party utility that I could use to accomplish this while restricting the user?
Again thank you for you help.
BC
I'm not aware of any 3rd party utility that would let you do this.
-JJ
-JJ
What you are trying to do is not possible. The external addresses need to be created as contacts in AD and that can only be done by a user with the appropriate Exchange permissions.
-JJ