<div>
You would probably be better off creating another Administrative Group and installing the new exchange server into that Admin Group. Admin Groups are for delegation of permissions, so that would probabaly be the better way to go.
</div>


<div>
Thanks. That is a great idea. <br />
As the name implies, a new AG will clearly separate administration. But we can administer that AG by giving ourself permission at the root of Exch org? OR can the Admin of that AG remove propagation of permissions?<br />
Jay<br />

</div>


<div>
I am glad I asked the question. (I expected a simple Yes answer -- ignorant me!)
</div>


<div>
<div class="content wysiwyg-content">
We have a back-end and a front-end Exchange 2003 running in our AD domain. For a new branch we want to install another back-end Exchange 2003 in the same Administrative Group but do NOT want that user (who will not be a member of domain admins) to have any control over our current Exchange servers -- just fully manage his new Exchange 2003. Is this doable or are there some pitfalls? (He will get view-only rights on the whole Exchange organization.)
</div>
</div>


We have a back-end and a front-end Exchange 2003 running in our AD domain. For a new branch we want to install another back-end Exchange 2003 in the same Administrative Group but do NOT want that user (who will not be a member of domain admins) to have any control over our current Exchange servers -- just fully manage his new Exchange 2003. Is this doable or are there some pitfalls? (He will get view-only rights on the whole Exchange organization.)

Separate administration of Exchange 2003 in one AG

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.