Installinig a Exchange 2007 w SP1 on 2008 Standard Server with a Server 2003 SP2 DC with all FSMO rolesand global catalog only one domain controler. there was a previous server that was taken away in 2008in the ldif.err we get :Connecting to "server2.Pridwin.local"Logging in as current user using SSPIImporting directory from file "C:\Exchange 2007\Setup\ServerRoles\Common\Setup\Data\PostExchange2003_schema0.ldf"Loading entries1: CN=ms-Exch-ELC-Expiry-Action,CN=Schema,CN=Configuration,DC=Pridwin,DC=localEntry DN: CN=ms-Exch-ELC-Expiry-Action,CN=Schema,CN=Configuration,DC=Pridwin,DC=localAdd error on entry starting on line 1: BusyThe server side error is: 0x21a2 The FSMO role ownership could not be verified because its directory partition has not replicated successfully with atleast one replication partner.The extended server error is:000021A2: SvcErr: DSID-030A09F3, problem 5001 (BUSY), data 00 entries modified successfully.An error has occurred in the programDCDIAG.exe on 2003 DC C:\Program Files\Support Tools>dcdiag.exe Domain Controller Diagnosis Performing initial setup: Done gathering initial info. Doing initial required tests Testing server: Default-First-Site\SERVER2 Starting test: Connectivity ......................... SERVER2 passed test Connectivity Doing primary tests Testing server: Default-First-Site\SERVER2 Starting test: Replications [Replications Check,SERVER2] A recent replication attempt failed: From SERVER-BACKUP to SERVER2 Naming Context: DC=ForestDnsZones,DC=Pridwin,DC=local The replication generated an error (1256): The remote system is not available. For information about network troubleshooting, see Windows Help. The failure occurred at 2009-08-19 08:49:09. The last success occurred at 2008-11-14 13:57:59. 6219 failures have occurred since the last success. [SERVER-BACKUP] DsBindWithSpnEx() failed with error 5, Access is denied.. [Replications Check,SERVER2] A recent replication attempt failed: From SERVER-BACKUP to SERVER2 Naming Context: DC=DomainDnsZones,DC=Pridwin,DC=local The replication generated an error (1256): The remote system is not available. For information about network troubleshooting, see Windows Help. The failure occurred at 2009-08-19 08:49:09. The last success occurred at 2008-11-14 13:57:59. 6220 failures have occurred since the last success. [Replications Check,SERVER2] A recent replication attempt failed: From SERVER-BACKUP to SERVER2 Naming Context: CN=Schema,CN=Configuration,DC=Pridwin,DC=local The replication generated an error (1722): The RPC server is unavailable. The failure occurred at 2009-08-19 08:49:51. The last success occurred at 2008-11-14 13:57:58. 6219 failures have occurred since the last success. The source remains down. Please check the machine. [Replications Check,SERVER2] A recent replication attempt failed: From SERVER-BACKUP to SERVER2 Naming Context: CN=Configuration,DC=Pridwin,DC=local The replication generated an error (1722): The RPC server is unavailable. The failure occurred at 2009-08-19 08:49:30. The last success occurred at 2008-11-14 13:57:58. 6219 failures have occurred since the last success. The source remains down. Please check the machine. [Replications Check,SERVER2] A recent replication attempt failed: From SERVER-BACKUP to SERVER2 Naming Context: DC=Pridwin,DC=local The replication generated an error (1722): The RPC server is unavailable. The failure occurred at 2009-08-19 08:49:09. The last success occurred at 2008-11-14 13:57:58. 6220 failures have occurred since the last success. The source remains down. Please check the machine. REPLICATION-RECEIVED LATENCY WARNING SERVER2: Current time is 2009-08-19 09:38:27. DC=ForestDnsZones,DC=Pridwin,DC=local Last replication recieved from SERVER-BACKUP at 2008-11-14 13:57:51. WARNING: This latency is over the Tombstone Lifetime of 60 days! DC=DomainDnsZones,DC=Pridwin,DC=local Last replication recieved from SERVER-BACKUP at 2008-11-14 13:57:51. WARNING: This latency is over the Tombstone Lifetime of 60 days! CN=Schema,CN=Configuration,DC=Pridwin,DC=local Last replication recieved from SERVER-BACKUP at 2008-11-14 13:57:51. WARNING: This latency is over the Tombstone Lifetime of 60 days! CN=Configuration,DC=Pridwin,DC=local Last replication recieved from SERVER-BACKUP at 2008-11-14 13:57:51. WARNING: This latency is over the Tombstone Lifetime of 60 days! DC=Pridwin,DC=local Last replication recieved from SERVER-BACKUP at 2008-11-14 13:57:51. WARNING: This latency is over the Tombstone Lifetime of 60 days!

You need to use Metadata cleanup utility to get rid of tombstone objects and then make sure dcdiag looks good. How to remove data in Active Directory after an unsuccessful domain controller demotion http://support.microsoft.com/kb/216498 In between if you still need help on this part you can always post in Windows Forum http://social.technet.microsoft.com/Forums/en-US/winserverDS/threads Vinod |CCNA|MCSE 2003 +Messaging|MCTS|ITIL V3|

Hi,I think we may need to solve the AD issue first. I recommend you to use Windows Server forum if you need further AD related help.Windows Serverhttp://social.technet.microsoft.com/Forums/en-US/category/windowsserverRegards,Xiu