Hello, we're using the "manager" attribute in AD to associate service accounts with their owner.  In Outlook under Calendar this places those service accounts under the "Team: <MANAGER>" group.  So in addition to actual team members under a manager, service accounts are also listed.  Is there a way to hide those accounts so they aren't listed?

Thank you

Patient: "Doctor, it hurts when I do this."

Doctor: "Well, don't do that!"

You're using an attribute for a purpose different from the way it was intended.  Use a custom (extension) attribute for that in

The AD team chose that since it was the only built-in attribute that had a parent/child type relationship. If we wanted to duplicate that same functionality with an extension attribute is it as simple as using the Active Directory Schema MMC Snapin to copy the "manager" and "directReports" settings to two new attributes?  I'm not sure in AD how that relationship between the two attributes works.

The AD team made a mistake, then.

I'm not sure if you're actively trying to be rude, or if it's just coming out.  But you should work on your professional communication.

This isn't a debate on whether it's currently setup properly or not.  If the manager attribute is not used in the way it has and is being used, then i understand that this situation would not exist.  Environments are rarely setup per recommended best practices. Bubble wrap was originally used as wallpaper, not packing material, for example. But in our environment there is a need to track who the owner of service account is, and it's setup the way it is (for better or worse) because it's an easy way to assign a bunch of accounts to an owner and see who they belong to later.  I'm trying to find a way to improve it.  So, either there is a more effective way to track the owner of a service account, in which case i'm trying to understand how to mirror the manager/directReports attributes to new custom attributes for service accounts; or there isn't, and i'm trying to understand if there is a way to configure exchange so as to not visually display those service accounts to the end user within the Outlook client.

If manager/directReports type functionality can't be replicated with a new custom set of extension attributes, and there isn't a way to hide service accounts (or any type of account) in the Calendar field, then it's just something that has to be lived with today and a feature request could be submitted to Microsoft for the future.

If you don't have any actively helpful suggestions then please don't bother responding.  I'm trying to better my environment.

Thank you for the suggestion on my manners.  Sorry that I can't give you the answer you want.  The answer I gave you in my first response is the way to better your environment, i.e., to use an attribute that's more appropriate for the task.  Perhaps you should work on your own professional communication and read the answer provided and try to understand it instead of being argumentative.

I asked which attribute is more appropriate for that task.  You did not answer that nor give any answer on how to replicate what manager/directReport is doing.

Additionally, the original question was if it was possible in Exchange to hide certain accounts so that they would not display as being on a team in Calendar.  You side stepped that question and said those accounts shouldn't be there to begin with, not how an account could be hidden or if that's even possible.

Finally, I have yet to argue with you.  I've pointed out that your comments came off rude to me.  The doctor analogy did not add value nor represent this issue accurately.  If that were a real doctor it would show lack of empathy for the patient and a lack of interest in getting into the root of the problem.  The comment on the AD team making a mistake also did not add value or answer either of the two parts to my question.  They know what the manager attribute is for, but at the time chose to not modify the schema with a custom attribute, or perhaps they too do not know how to replicate the manager/directReport behavior.  In any case, pointing out that they're wrong, doesn't answer my question or show HOW to use an extension attribute to achieve this.

You're an MVP, a partner, and a consultant.  You should be familiar with the Code of conduct.  Please be considerate and respectful: http://social.technet.microsoft.com/wiki/contents/articles/112.wiki-code-of-conduct.aspx

I'll attempt a more targeted question in the Directory Services forum to see if someone can walk me through the steps to get a extension attribute that will be appropriate for storing service owner type data.

I answered part of your question:

You're using an attribute for a purpose different from the way it was intended.  Use a custom (extension) attribute for that instead.

As to "is it possible", it's always possible.  I didn't answer because I couldn't think of a practical way to do it.

As to respectful, I answered your question.  You chose to call me names.