<div>
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.<br />
<br />
I have recommended this question be closed as follows:<br />
<br />
Accept: timgreen7077 (<a href="https:#a42469737" rel="ugc">https:#a42469737</a>)<br />
<br />
If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.<br />
<br />
Delphineous<br />
Experts-Exchange Cleanup Volunteer
</div>


No comment has been added to this question in more than 21 days, so it is now classified as abandoned.

I have recommended this question be closed as follows:

Accept: timgreen7077 (https:#a42469737 [https:#a42469737])

If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.

Delphineous
Experts-Exchange Cleanup Volunteer

<div>
<div class="content wysiwyg-content">
I noticed mailboxes have inherited permissions for a BES service account. This account is no longer needed. I tracked the inheritance up to the Server permissions in ADSIEDIT. <br />
How did this get there, and should I simply delete it from ADSIEDIT?
</div>
</div>


I noticed mailboxes have inherited permissions for a BES service account. This account is no longer needed. I tracked the inheritance up to the Server permissions in ADSIEDIT. 
How did this get there, and should I simply delete it from ADSIEDIT?

Exchange 2013 - Mailbox permissions inherited from server, how to remove

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.