Solved

Exchange 2007 servers not being added to Exchange Domain Servers in a Mixed Mode Organization

Posted on 2008-10-20
4
1,624 Views
Last Modified: 2010-01-15
Hello,

We have a root domain that holds the schema configuration and enterprise resources.

We have a child "parrallel" domain. its not really a child. anyways.

We have an Exchange Organization that was already installed and it was a 2003 mode exchange org.

now when we installe exchange 2007 servers in the org if we do not manually add the new 2007 servers to the Exchange 2003 security group "Exchange Domain Servers" then the exchange 2007 servers can not use the global catalog and domain controllers on the child domain.

Does anyone know why when the new Exchange 2007 servers get installed they 1. don't get automatically added to Exchange Domain Servers 2. have to be added to this group before they have SACL Rights on the child domain's domain controllers/global catalog servers?

Microsoft isn't proving to be very helpful on this issue.

if you need mroe information please let me know.

thanks!!!!
0
Comment
Question by:StarkJC
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
4 Comments
 
LVL 33

Expert Comment

by:Exchange_Geek
ID: 22757659
"now when we installe exchange 2007 servers in the org if we do not manually add the new 2007 servers to the Exchange 2003 security group "Exchange Domain Servers" then the exchange 2007 servers can not use the global catalog and domain controllers on the child domain"

Have you run the setup commands on child domains for Exchange 2007 ?

setup.exe /pl
setup.exe /preparedomain: FQDN of Child domain.

I do not see a reason why E2k7 won't use the child domain controllers if Exchange is allowed by running the above commands.
0
 

Author Comment

by:StarkJC
ID: 22757821
We ran setup /preparead

this preps all domains in the forest.

The Exchange Servers didn't have SACL Rights on the child domains until we added them to Exchange Domain Servers.

when i look through the exchange setup logs everything was done properly when ad was prepd.

when i look in the exchange setup logs on a 2007 server during installation. No where in the logs does it indicate that it even tries to add the new server object to the group Exchange Domain Servers.

0
 
LVL 33

Expert Comment

by:Exchange_Geek
ID: 22757933
Was this command run setup.exe /pl ??
0
 

Accepted Solution

by:
StarkJC earned 0 total points
ID: 22803959
the prepare legacy switch is run when you run the setup.exe /preparead

I've figured out that the issue is when the prepare legacy permissions and prepare domain was run on the child domain that the permissions on the "Domain Controllers" policy the security settings were not properly updated.

The only group that had permissions on the Domain Controllers Security policy in the child domain was the Exchange 2003 group "Exchange Enterprise Servers" which the group Exchange Domain Servers is a member of thus when we manually added the Exchange 2007 servers to the Exchange 2003 security group Exchange Domain Servers they could then use the global catalog servers in the child domain because this group had permissions for SACL Rights on those global catalog / domain controllers.

So we manually added the group for the 2007 exchange servers "Exchange Servers" to have the same permissions on the Domain Controllers policy in the child domain and now they have the rights they need to use the domain controllers and global catalog servers on the child domain.

When i look at the setup logs on the exchange 2007 servers the setup is successfully adding the computer objects to the "Exchange Servers" security group and is correctly NOT adding them and NOT even trying to add them to the "Exchange Domain Servers" as the Exchange 2007 servers should not be in the security group Exchange Domain Servers.

We could try running setup /prepdomain on the child domain again but i don't think its needed or worth the effort.

The final resolution is to modify the Domain Controllers security policy to give the new security group Exchange Servers the same permissions as the old 2003 security group Exchange Domain Servers has on this policy.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

A project that enables an administrator to perform actions within a user session context not just at the time of login but any time later on day(s) or week(s) later.
A company’s centralized system that manages user data, security, and distributed resources is often a focus of criminal attention. Active Directory (AD) is no exception. In truth, it’s even more likely to be targeted due to the number of companies …
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…

733 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question