T
Trinity
Hi all,
My employer wants the users to use a different online directory rather then
the GAL, to lookup users phone and title etc. So they would like to know if
the users information from the GAL can be hidden, except for the name and
email address (i.e, they want all the phone, address, city, title, office
information hidden). I know that modify the schema will allow me to hide
certain attributes/contents from being display but will it let me hide all
of this information? or should I use permission in AD to prevent users
access to these information? or another solution is to remove the fields
contents (manually or script) and leave them visible and blank Or is there
an easy way to accomplished this request?
My preference would be to remove the contents and leave the fields blank and
visible, that way I can leave the schema alone. My second choice would be
using security in AD to deny access to those attributes. If I modify the
schema and hide the fields, will this lead to some problem down the road
when we upgrade to Exchange 2003? or when we upgrade AD to 2003?
Currently we run Exchange 2000 in Windows 2000 AD. All in native mode.
Your advise or comments on this issue is greatly appreciated. Thank you.
Cuong
My employer wants the users to use a different online directory rather then
the GAL, to lookup users phone and title etc. So they would like to know if
the users information from the GAL can be hidden, except for the name and
email address (i.e, they want all the phone, address, city, title, office
information hidden). I know that modify the schema will allow me to hide
certain attributes/contents from being display but will it let me hide all
of this information? or should I use permission in AD to prevent users
access to these information? or another solution is to remove the fields
contents (manually or script) and leave them visible and blank Or is there
an easy way to accomplished this request?
My preference would be to remove the contents and leave the fields blank and
visible, that way I can leave the schema alone. My second choice would be
using security in AD to deny access to those attributes. If I modify the
schema and hide the fields, will this lead to some problem down the road
when we upgrade to Exchange 2003? or when we upgrade AD to 2003?
Currently we run Exchange 2000 in Windows 2000 AD. All in native mode.
Your advise or comments on this issue is greatly appreciated. Thank you.
Cuong