Exchange 2007 SP1 RU5 - Error regarding replication between computers in different domains when using standby continuous replication (SCR).
Exchange 2007 SP1 RU5 introduces an error into the enable-storagegroupcopy -standbymachine commandlet when attempting to enable SCR on a storage group.
The error is only present when there is a parent domain -> child domain active directory domain structure. The issue does not occur if the active directory domain / forest is flat.
When attempting to use the enable-storagegroupcopy -standbymachine <scrTarget> commandlet, the following error is returned:
Enable-StorageGroupCopy: Standby continuous replication is not supported between computers in different Active Directory domains. The target node is in domain <child.parent.com>, which is different from the source domain <parent.com>.
This error is correct if the machines are actually in different domains, as SCR targets must be in the same domain as their sources. In this case the error is being thrown incorrectly when the machines are actually members of the same domain.
To correct this issue:
1) Verify that all machines are actually members of the same domain.
2) From the machine where the commandlet is being run, uninstall RU5. (Note: If any of the machines are involved in replication, and RU5 is removed, it needs to be reinstalled after replication is established. All machines involved in replication should run the same release rollup update).
3) From a machine with just the management tools installed, with any RU prior to RU5, run the enable-storagegroupcopy -standbymachine commandlet. (This would be preferred as it does not involve uninstalling and re-installing any already applied RUs.) If any of the servers involved are cluster servers, the the command must be run from a management tools workstation that is the same version. For example, if Windows 2008 is the operating system hosting Exchange clustering, then the tools workstation must also run the Exchange 2007 SP1 management tools and the Windows 2008 failover cluster manager.
The issue is scheduled to be corrected in Exchange 2007 SP1 RU8.
***UPDATE: As of today this has been rescheduled for Exchange 2007 SP1 RU7***