I have an exchange server that is set up on domain A and I want to enable 
users from child domain to be able to utilize the exchange server.  
I ran the domain prep on the the child domain contrller no issues I see that 
the security groups were created.
when I go to set up the recipient update service I am getting a System can 
not find the file specfied.
Facility: Win32
ID No:C0070002
Exchange System Manager

The mail boxes are not creating when you create a mail enabled user account.

Does the user account that is mail enabling the users in the child Domain 
have rights to create objects in the parent?


"Schuml" <larrys@news.postalias> wrote in message 
news:9ADF63CA-3BCF-4028-A8FB-E9FD8660657D@microsoft.com...
>I have an exchange server that is set up on domain A and I want to enable
> users from child domain to be able to utilize the exchange server.
> I ran the domain prep on the the child domain contrller no issues I see 
> that
> the security groups were created.
> when I go to set up the recipient update service I am getting a System can
> not find the file specfied.
> Facility: Win32
> ID No:C0070002
> Exchange System Manager
>
> The mail boxes are not creating when you create a mail enabled user 
> account.

Hello,

Thank you for posting.

According to the error message, I suggest you follow these steps to narrow 
down/fix this problem:
1.	Check the settings of TCP/IP on the Exchange server. Make sure the 
primary DNS server is pointing to the correct server. The DNS server should 
be able to resolve all records of DCs both in parent domain and in child 
domain.
2.	Verify if the primary DNS server IP address is correct on the server 
which you run domainprep. Re-run domainprep again.
3.	Try to create the RUS again in ESM.

If the problem persists, please collect two MPS reports for me. One for the 
Exchange server in the parent domain, one for the server in child domain:
1. Access the following URL:
<http://www.microsoft.com/downloads/details.aspx?familyid=cebf3c7c-7ca5-408f
-88b7-f9c79b7306c0&displaylang=en>
2. Download MPSRPT_Exchange.EXE and execute the exe file. (On the server in 
child domain, please download MPSRPT_DirSvc.EXE.)
3. Please send the resulting file (CAB file) to me at 
v-jochen@microsoft.com.

Please use "Recipient Policy to a child domain " as the title of your 
emails. Thanks!

If you have any questions or concerns, please feel free to let me know.

Sincerely,
John Chen, MCSE, MCSA, MCDBA, MCSD
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue. 
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

In reply to tecody I have delegated both administrator accounts from each 
domain full Exchange Adminstrator roles, so I should be OK there.

In Reply to John:
There really was no DNS changes to be made, I can ping each of the servers 
by  name and it resolves to the correct IP address.  I can successfully 
communicate between the two servers.

I have run the MPSrpt on both servers and I have e-mailed them to you.

Hi,

Please check if the SRV records are created on the DNS server. For the 
detailed steps, please refer to the following KB article:
How to Verify the Creation of SRV Records for a Domain Controller
http://support.microsoft.com/?id=241515

PS: So far, I did not receive your email.

Sincerely,
John Chen, MCSE, MCSA, MCDBA, MCSD
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue. 
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

I am not sure if my last post went through,  I am surprised you did not get 
my e-mail I did not receive an NDR back but I re-sent it to you this morning. 
 I sent it to 
v-jochen@microsoft.com with the subject of " Recipieient polict to a child 
domain"

I was able to resolve the recipient update I found out the child domain had 
not replicated to the domain controller so I followed the instructions in 
article 
http://technet2.microsoft.com/WindowsServer/en/Library/34c15446-b47f-4d51-8e4a-c14527060f901033.mspx?mfr=true 
and after replication I was able to successfully create the Recipient update 
Service.

I am left with on problem,  the Exchange Server still does not seem to 
recognize the domain controller in the child domain.  After I created the 
update service I created a new account and ran the service, the e-mail 
accounts were created as expected, however the mailbox was still not created, 
but I can see the user in the GAL.  I can not login to the account with 
outlook, or POP3. 
In the Directory access for the properties of the server I still dont see 
the Child domain controller being listed.  Any suggestions?

Hi,

I performed a test on my end. According to the testing result, the DCs in 
sub domain are not listed in Directory Access.

Now I suggest you make sure if AD is replicating well now. Please check the 
Directory Service log and verify if there are some replication errors in 
it. If the replication is not working well, we do not know if the issue is 
cause by Exchange itself. Replication error may also cause this issue. 

If you did not find anything related in the Directory Service log, please 
perform the following test:
1.	Open AD Users and Computers on the root domain controller. (Microsoft 
Excahnge-> AD Users and Computers)
2.	Right click "Active Directory Users and Computer (Domainname)", click 
Connect to Domain, and then locate to the sub domain.
3.	Create a new mail enabled user account in the sub domain.
4.	Open Exchange System Management. 
5.	Locate to Recipients->Recipient Update Services->Right click every 
service on the right panel and click Update Now.
6.	In AD Users and Computers, double click the user account and check if 
the SMTP addresses are created.
7.	If it works, please try to access in OWA.

PS: The mailbox will be created after the first logon.

Please let me know the result. Thanks. Have a good day.

Sincerely,
John Chen, MCSE, MCSA, MCDBA, MCSD
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue. 
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

I will get back with you John I was unable to work on this today

As it turns out the child domain was considered an orphan and I follwed the 
steps in these articles to demote the domian and then re-promote it. after 
this was accomplished everythig has worked as expected. An important lesson 
in monitoring your domain replication and solving issues before the y get 
bigger.

These are the articles I followed:
Orphaned child domain controller information may not be replicated to other 
Windows 2000 Server-based domain controllers
http://support.microsoft.com/?kbid=887430

332199 Using the DCPROMO /FORCEREMOVAL Command to Force the Demotion of 
Active
http://support.microsoft.com/?id=332199

216498 How to remove data in Active Directory after an unsuccessful domain
http://support.microsoft.com/?id=216498

Hi,

I am so happy to hear that the problem has been fixed. Thank you for 
sharing your experience here.

Have a nice day.

Sincerely,
John Chen, MCSE, MCSA, MCDBA, MCSD
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue. 
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.