I am starting over with this thread, alot has changed but problem remains. I sucessfully ran the setup /NewProvsionedServer proceedure to provision Exchange server for delegated setup. I see the new server obect in the configuration container. The domain admin account that will install Exchange Server is a member in the RBAC group 'Delegated Setup' Exchange setup installed some exchange server files and the management consoles yet the install fails when trying to install server roles with the error 'domain cannot be contacted or does not exist'. The error message telle me setup program is trying to connect with forest root domain. Exchange setup is running in a remote site without direct connection to the root domain controllers and network firewalls will not allow the connection. I expected delegated setup get around this type of behavior, is there a work around for this?

Are you sure, AD is replicating with this site properly? Second idea - maybe IP address of this new Exchange machine is not belong to subnets for this AD site?Regards, Konrad Sagala, MCT, MCSE+M, MCITP: Exchange 2007/2010

Are you sure, AD is replicating with this site properly? Second idea - maybe IP address of this new Exchange machine is not belong to subnets for this AD site?Regards, Konrad Sagala, MCT, MCSE+M, MCITP: Exchange 2007/2010

Is AD replicating correctly to the remote site? Can you open ADUC and check the group membership of the account you are using on the local (remote) domain controller? Perhaps AD replication is not working, and this is the reason for the failure. Or replication is slow. What are the errors from the event logs?Lance Wilson Sr. Lead Consultant Catapult Systems Inc.

Is AD replicating correctly to the remote site? Can you open ADUC and check the group membership of the account you are using on the local (remote) domain controller? Perhaps AD replication is not working, and this is the reason for the failure. Or replication is slow. What are the errors from the event logs?Lance Wilson Sr. Lead Consultant Catapult Systems Inc.

Replication is working and site information is accurate. I'm not sure we identified the problem but we noticed the remote site domain controller wants to communicate with root domain controllers in the datacenter to resolve tust but the remote site is intentionally blocked from reaching the datacenter directly. We assumed remote site could resolve trust through domain controllers in the Hub Site. For clarity site oragnization looks something like this: Datacenter --> Hub Site --> Remote site.

Replication is working and site information is accurate. I'm not sure we identified the problem but we noticed the remote site domain controller wants to communicate with root domain controllers in the datacenter to resolve tust but the remote site is intentionally blocked from reaching the datacenter directly. We assumed remote site could resolve trust through domain controllers in the Hub Site. For clarity site oragnization looks something like this: Datacenter --> Hub Site --> Remote site.

Hi 1. You server must be domain member. 2. You network must open port and your server need to communicate with DC. Terence Yu TechNet Community Support

Hi 1. You server must be domain member. 2. You network must open port and your server need to communicate with DC. Terence Yu TechNet Community Support