Organization Checks ......................... COMPLETEDThe Active Directory schema will be upgraded if you continue. Verify that the organization is ready for Exchange 2007 by running the Exchange 2007 Readiness Check, which is part of the Exchange Best Practices Analyzer. Configuring Microsoft Exchange Server Extending Active Directory schema Progress ......................... FAILED There was an error when executing 'ldifde.exe' to import schema file 'D:\stuffs\Exchange 2007\Setup\ServerRoles\Common\Setup\Data\PostExchange2003_schema0.ldf'. Error code: 8206. More details can be found in the error file 'C:\Documents and Settings\la01\Local Settings\Temp\2\ldif.err' The Exchange Server setup operation did not complete. Visit http://support.microsoft.com and enter the Error ID to find more information.

Hi, Did you check: More details can be found in the error file 'C:\Documents and Settings\la01\Local Settings\Temp\2\ldif.err' Leif

in 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!

Looks like you have some replication issues between your domain controllers, would suggest you move all the FSMO roles to new server which is promoted to a DC, after verifying that all roles are moved to the new server, would suggest you demote the problematic DC completely.

Yes you have lots of Replication issues with DC's first you need to rectify this. or else you will still face issues in future as in ex2007 Mailflow happens via active directory sites. Use the Replication Monitor to Determine the Operations Master and Global Catalog Roles http://support.microsoft.com/kb/297230 Vinod |CCNA|MCSE 2003 +Messaging|MCTS|ITIL V3|