?
Solved

Exchange 2010 in 2008 R2 root Domain needs to be available to accounts in 2008 x32 child Domains.

Posted on 2011-03-21
3
Medium Priority
?
791 Views
Last Modified: 2012-05-11
I have a test network that I'm using to teach a class in a few weeks. For a variety of reasons, small groups of students will each create and administer their own child Domains and controllers.

The network is as such:

This is a Windows 2008 R2 network with two Domain controllers in the root Domain, and a very basic Exchange 2010 server installed on a member server in the root Domain. Using Windows 7 Pro x32 workstations joined to the root Domain, and using Outlook 2010 as a client, the Exchange system is verified as working.

Here is the issue:

Each student team will have a physical box with Windows 2008 Server Enterprise installed. I only have 32-bit machines available for these child Domain servers, so they'll be non-R2 Windows 2008, and the forest and root Domain are set to Windows 2008 mode.

The students will run dcpromo and create child Domains in the existing tree, and in their respective Domains, create user accounts.

When I taught this class with Windows 2003 and Exchange 2003, it was a simple matter of having them run DomainPrep after creating the child Domain controllers, and then I'd simply create Recipient Update connectors to these child Domains from the Exchange 2003 server.

Obviously, Exchange 2010 is different. I *think* I've successfully extended the schema in the child Domain by running Exchange 2010 setup (on the root Domain member Exchange server), but can't find anything resembling Recipient Update connectors on the Exchange console.

What am I missing here?
0
Comment
Question by:shrudlu
[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
3 Comments
 
LVL 44

Accepted Solution

by:
Amit earned 2000 total points
ID: 35183105
0
 

Author Comment

by:shrudlu
ID: 35183429
Those are great links, and I read in the third that RUS is an Exchange 2003 thing, and not needed in Exchange 2010. My base assumption, then, is wrong: that the only reason that I'm not able to bind Exchange accounts to user AD accounts residing in the child Domain(s) is because of the missing RUS connections.

This means that there's something else I'm not doing correctly.
0
 
LVL 44

Expert Comment

by:Amit
ID: 35183509
You need to prepare the child domain also.  Use setup /PrepareAllDomains

Let me know if this doesn't works out
0

Featured Post

Are your AD admin tools letting you down?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

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

How to resolve IMCEAEX NDRs in Exchange or Exchange Online related to invalid X500 addresses.
This article will help to fix the below error for MS Exchange server 2010 I. Out Of office not working II. Certificate error "name on the security certificate is invalid or does not match the name of the site" III. Make Internal URLs and External…
To show how to generate a certificate request in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Servers >> Certificates…
how to add IIS SMTP to handle application/Scanner relays into office 365.
Suggested Courses
Course of the Month14 days, 6 hours left to enroll

771 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