Securing Exchange Server by Controlling Object Visibility - Part 2
| Published date | Thu, 2006-10-12 12:03 |
| Category | |
| Author | Nicolas Blank |
| Printable Version | Email this Article | |
|
|
|
| Post to del.icio.us | Furl it | Spurl it | |
|
|
|
How is this possible? When a user is mail or mailbox enabled, ADUC (AD Users and Computers) presents a number of options, such as the default mail store or Administration Group. However, what if users mailboxes should not be put into certain stores, such as VIP mailbox stores, or the mailbox store choice doesn’t suit the geography. Example – A Dallas user can be mailbox enabled using only the Mailbox Store on the Dallas Exchange server by the local administrator, whilst Los Angeles and New York aren’t listed as options. In larger organizations choices may be restricted by region, department or even politically, so that the VIP Storage Groups are invisible to normal users. In this article we’re going to look at limiting those choices by hiding mailbox stores from view.
To demonstrate this I have created two extra databases as shown. Note the VIP Mailbox Store.

Further to this I have assigned an extra ACE (access control entry) against the helpdesk on the VIP Mailbox Store as follows:
Helpdesk DENY Read

Here’s how to do this. Right click on the mailbox store you wish to hide, click on Properties, Security, Advanced, Click Add, find and add the users or groups desired. Then chose to Deny Read.Clicking OK closes the view and displays the new ACE we just added.
Lets look at the effect in AD Users and Computers. The first view is the view as seen by a user with no restrictions:
When logging in as the Helpdesk User and view the list of available Mailbox Stores I see the Mailbox Store list MINUS the VIP store as desired.
Opening Exchange System Manager as the Helpdesk user reveals the added benefit of hiding the VIP store object in this utility as well. Mailbox Store’s are not the only object type that may be hidden from view in either AD Users&Computers nor Exchange System Manager. Administrative Groups, Routing Groups, etc may all be hidden from view to provide a simplified administrative view or a limited view while manipulating possible values on a users exchange attributes.

Summary
Editing the ALC (Access Control List) on the Mailbox Store object can also be done using ADSIEDIT or a 3’ rd party utility or script. I prefer using third party tools for their obvious benefits. Testing, documenting and providing rollback play an important part in modifying permissions in Active Directory. As mentioned previously, editing at this level without thoroughly understanding the effects can be dangerous. I suggest proving functionality in a lab first, documenting it and using a trusted guaranteed method such as a script or utility to roll it out.
As originally published on outlookexchange.org
Discuss this in

About Nicolas Blank
Nicolas Blank - Operations Director, Credo Technical Services
Nicolas Blank is a Microsoft Infrastructure Architect and Operations Director for Credo Technical Services in South Africa and specializes in Exchange, Active Directory, architecture, systems management, migration and scripting. Nicolas is a Microsoft MVP for Exchange and spends what spare time he has writing, blogging and talking about Exchange and associated technologies. www.credotech.co.za
Recent Articles by the author
Featured Links
-
Free Download Trial: SharePoint Migration, Backup and Recovery Software
DocAve: Enterprise, full-fidelity backup & recovery software for SharePoint provides essential protection & management tools, and allows for a data migration from Exchange Public Folders in to SharePoint 2007 & 2003. -
Microsoft Exchange Hosting
24/7 US based support. 99.9% uptime guarantee. Your Mission Critical E-mail is Our Critical Mission. Sign up for our 30 day trial to see the difference. Questions? Call us toll free at (800) 967-3924. -
QuickEmbeddedTips: Tips for Embedded Systems Professionals
Quick Tips for Embedded System Engineers. Visit the site for the latest tips, tutorials on Arm, Linux and VxWorks.

