• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1051
  • Last Modified:

Exchange 2010 Admin Rights

I was given a task to find out if this is possible in MS Exchange 2010. We are going to get an Exchange server which will host 2 post office. ex. lala.com and tata.com. First of all is this considered 2 post offices?

We would like to have 1 admin per domain. Ideally this would give them the rights do any and everything needed to administer their perspective domain only.

They should not have rights to administer any high level tasks such as add new post offices, manage/create other post offices, and so on.

I am looking for resources or (the correct terminology so I can find resource) on how to get this done.

Or even an example of how my Google query should look, to find the correct resources.

Any help on this will be appreciated
0
EnriquePhoenix
Asked:
EnriquePhoenix
  • 4
  • 3
1 Solution
 
AkhaterCommented:
>> lala.com and tata.com. First of all is this considered 2 post offices?
no they are called SMTP domains

and no this cannot be done, in exchange the delegation can be made on exchange servers but not on smtp domains
0
 
EnriquePhoenixAuthor Commented:
Not exactly the start I wanted to see. :( So do I have to run 2 Exchange servers to separate the rights.
0
 
AkhaterCommented:
not really it will not even work since you have no way of stopping admin1 to assign users emails @domain2.com

the only thing that would do what you want is exchange hosted
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
EnriquePhoenixAuthor Commented:
Any other takers? I will end this post tomorrow if nobody has anymore input on the matter.
0
 
EnriquePhoenixAuthor Commented:
Configuration scopes enable you to control who can manipulate servers and databases.

Recipient and configuration scopes enable you to segment the management of server, database or recipient objects in your organization. For example, a recipient scope can be added to a role assignment so that administrators in Vancouver can only manage recipients in the same office. A server configuration scope could be added to a different role assignment so that administrators in Sydney can only manage servers in their Active Directory site.

http://technet.microsoft.com/en-us/library/dd335131.aspx
0
 
AkhaterCommented:
that is true I am aware of this but, if i understood correctly, you want these ppl to administer a domain name not a specific OU or database .

you cant deny the admin of lala.com to create a user @tata.com for example that's why i told you it can't be done
0
 
EnriquePhoenixAuthor Commented:
Thanks
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now