First e2k10 server (CAS of course) in an e2k3 ORG. Empty root with child domains. Installing in child domain.Continue to get error:[04/15/2010 17:30:33.0207] [1] [ERROR] Active Directory operation failed on addcp004.regn.net. This error is not retriable. Additional information: The name reference is invalid.This may be caused by replication latency between Active Directory domain controllers.Active directory response: 000020B5: AtrErr: DSID-03152392, #1: 0: 000020B5: DSID-03152392, problem 1005 (CONSTRAINT_ATT_TYPE), data 0, Att 9bcc19bb (msExchRMSComputerAccountsLink)Any suggestions? Is it simply wait for replication and what is the best way to check for replication to be completed? It seems to have trouble with the computer account? It bounces back and forth between two DC's that are not GC's. There are also 2 GC's in that site. All four of these DC's are not in the site where I am installing Exchange.Exchange Freak | @ntpro | http://geekswithblogs.net/ntpro

I waited about 20 minutes and this error went away and the CAS role was able to install. However the exchange rpc mapper service, ad topology service and address book service all hang themselves when trying to start.Exchange Freak | @ntpro | http://geekswithblogs.net/ntpro

Please reboot the newly installed exchange server, monitor the services and also the events in the application logIs there any error info if the service can’t be started, or restarted?Please run ExBPA against the exchange server for health checkJames Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx)If you have any feedback on our support, please contact tngfb@microsoft.com

The ExBPA only shows the need to add the registry fix for the supress link state for the Exchange 2010 Hub role. We have installed\uninstalled many times with many reboots and the services that hang are the Exchange RPC service and the AD topology service. We get: Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=568). Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC). and Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=568). The configuration domain controller specified in a call to SetConfigDCName (LNGDAYDCXP001.legal.regn.net) is unreachable. Exchange Active Directory Provider will select the configuration domain controller from the list of available domain controllers. Exchange Freak | @ntpro | http://geekswithblogs.net/ntpro

Please see the suggestions in this thread for troubleshootingJames Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com

It did indeed end up being the fact that the computer account for the CAS (first 2010 server) we were trying to install wasnt getting added to the forest root\exchange servers group which in turn means it wasnt being given permissions on the default domain controller policy for Audit\Manage Security Event Logs. I assume then that being exluded from this means none of the domain controllers would communicate with the server or the AD topology service hence all the service failures. Once we added it manually to the group membership everything worked as planned. Shouldnt this get done automagically as part of the install process?? Burned a week on this and I still cannot find the requirement for it in the E2K10 docs. If anyone knows a link or pointer I would appreciate knowing where I missed this crucial step ...Exchange Freak | @ntpro | http://geekswithblogs.net/ntpro

Just an FYI for others that may have received this error, we got the exact same error until we made all the DC's in the same site into GC's. Hope that helps, Coco