I have a parent domain called contoso.com and a child-domain called child.contoso.com, with one Exchange server in the root domain. (Exchange 2007 SP3). I'd like to verify that the child-domain was prepped (it is supposed to have been) but I am receiving the following error in OWA when trying to login as an account that exists in the child domain: Request Url: https://rootexchange.com:443/owa/lang.owa User host address: <Internal IP> Exception Exception type: Microsoft.Exchange.Data.Directory.ADTransientException Exception message: Could not find any available Domain Controller in domain DC=CHILD,DC=CONTOSO,DC=COM. Call stack Microsoft.Exchange.Data.Directory.DSAccessTopologyProvider.GetServerFromDomainDN(String distinguishedName, NetworkCredential credential) Microsoft.Exchange.Data.Directory.ConnectionPoolManager.GetConnection(ConnectionType connectionType, ADObjectId domain, String serverName, Int32 port, NetworkCredential credential) Microsoft.Exchange.Data.Directory.ConnectionPoolManager.GetConnection(ConnectionType connectionType, NetworkCredential networkCredential, ADObjectId domain) Microsoft.Exchange.Data.Directory.ADSession.GetConnection(String preferredServer, Boolean isWriteOperation, Boolean isNotifyOperation, ADObjectId& rootId) Microsoft.Exchange.Data.Directory.ADSession.GetReadConnection(String preferredServer, ADObjectId& rootId) Microsoft.Exchange.Data.Directory.ADSession.Find(ADObjectId rootId, String optionalBaseDN, ADObjectId readId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults, IEnumerable`1 properties, CreateObjectDelegate objectCreator, CreateObjectsDelegate arrayCreator) Microsoft.Exchange.Data.Directory.ADSession.Read(ADObjectId entryId, IEnumerable`1 properties, CreateObjectDelegate objectCtor) Microsoft.Exchange.Data.Directory.Recipient.ADRecipientSession.Read(ADObjectId entryId) Microsoft.Exchange.Data.Storage.ExchangePrincipal.Save() Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.DispatchLanguagePostLocally(OwaContext owaContext, OwaIdentity logonIdentity, CultureInfo culture, String timeZoneKeyName, Boolean isOptimized) Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.DispatchLanguagePostRequest(OwaContext owaContext) Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.PrepareRequestWithoutSession(OwaContext owaContext, UserContextCookie userContextCookie) Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.InternalDispatchRequest(OwaContext owaContext) Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.DispatchRequest(OwaContext owaContext) System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) Also, I don't see any exchange permissions in the user/computer object's security tab relating to the parent domain. Inheritancy is on. The DC (and GC) in the child domain does not have a C:\ExchangeSetupLogs folder. The child.contoso.com domain partition doesnt have the Microsoft Exchange System Objects container. Advanced View is enabled in ADUC. I am using an Enterprise Administrator account to verify the above. It looks to me as if it has not been prepped, but how can I be sure? Is all my above reasoning correct? I am aware that Exchange 2007 does not use RUS anymore, so I am correct in assuming I can create Recipient Policy(s) for that child-domain to generate specific SMTP addresses (we use many throughout our forest) for these child-domain users? Thanks all.

http://technet.microsoft.com/en-us/library/bb125224(v=EXCHG.80).aspx Microsoft Exchange System Objects is created in the root domain only. You can look for the results of this: Creates a new domain global group in the current domain called Exchange Install Domain Servers. The command places this group in the Microsoft Exchange System Objects container. It also adds the Exchange Install Domain Servers group to the Exchange Servers USG in the root domain. It wouldn't hurt anything to run Setup.com /PrepareDomain again.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

http://technet.microsoft.com/en-us/library/bb125224(v=EXCHG.80).aspx Microsoft Exchange System Objects is created in the root domain only. You can look for the results of this: Creates a new domain global group in the current domain called Exchange Install Domain Servers. The command places this group in the Microsoft Exchange System Objects container. It also adds the Exchange Install Domain Servers group to the Exchange Servers USG in the root domain. It wouldn't hurt anything to run Setup.com /PrepareDomain again.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Ok thanks for clearing up the Exchange System Objects container with reference to the domain it is created in. What would explain the OWA error?

Ok thanks for clearing up the Exchange System Objects container with reference to the domain it is created in. What would explain the OWA error?

You could start by verifying that the CAS can find a domain controller.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

You could start by verifying that the CAS can find a domain controller.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Hi zxxzxx, Per your information you referred, it seems that the child domain has not been done the exchange prepare /domain. So, you tests could proove it, if you want to create a new accepted domain for the child domain, you could do that. Regards!Gavin TechNet Community Support

Hi zxxzxx, Per your information you referred, it seems that the child domain has not been done the exchange prepare /domain. So, you tests could proove it, if you want to create a new accepted domain for the child domain, you could do that. Regards!Gavin TechNet Community Support

The child-domain's SMTP address is already in the Accepted Domains in Exchange. This was already done but to me it didn't look right, and then I found an OWA error on all accounts in this child-domain. I think i'll prep the domain.

The child-domain's SMTP address is already in the Accepted Domains in Exchange. This was already done but to me it didn't look right, and then I found an OWA error on all accounts in this child-domain. I think i'll prep the domain.

I've just found that the SACL permission for the directory service of the child-domains GC is set to 0.