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

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?
shrudluAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
shrudluAuthor Commented:
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
 
AmitIT ArchitectCommented:
You need to prepare the child domain also.  Use setup /PrepareAllDomains

Let me know if this doesn't works out
0
All Courses

From novice to tech pro — start learning today.