Entry DN: CN=ms-Exch-Access-Control-Map,CN=Schema,CN=Configuration,DC=contoso113,DC=com
Add error on entry starting on line 1: Busy
The 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-030A0AF2, problem 5001 (BUSY), data 0

An error has occurred in the program

ldif.log:

Connecting to "IT260-PDC-sp1.contoso113.com"
Logging in as current user using SSPI
Importing directory from file "C:\Users\Administrator\Desktop\Exchange Server 2007 with Service Pack 3 (Trial Only) (x86) - (English)\Setup\ServerRoles\Common\Setup\Data\PostWindows2003_schema0.ldf"
Loading entries
1: CN=ms-Exch-Access-Control-Map,CN=Schema,CN=Configuration,DC=contoso113,DC=com
Entry DN: CN=ms-Exch-Access-Control-Map,CN=Schema,CN=Configuration,DC=contoso113,DC=com
Add error on entry starting on line 1: Busy
The 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-030A0AF2, problem 5001 (BUSY), data 0

i have tried editing the bindings, disabling Ipv6, making sure dns is pointed locally, edited the registry, edit the schema0 file (entry not even in there), run the setup.com /prepareschema, elevated my servers to 2003, forced replication (successfully on
all servers). i make it thru all the readiness checks and it still keeps failing at the same point with the same message.

i have tried with both server 2008 enterprise sp1 and sp2 (i have 4 servers setup in vmware 2 w/ sp1 and 2 w/ sp2, 2 separate domains) this is for my exchange server lab, i seem to be unable to resolve this issue even with clean installs of the os's

ed ... thanks for nothing ... i am quite aware of the short-commings of unsupported products ... i came here asking for suggestions not sarcasm.

thanks Jasjit

guess i needed the reminder from that link ... forced replication through ad sites and services then walked away for an hr or 2 w/ machines still open ... came back and tried the install again and everything went through w/o fail. Was indeed an issue
with the replication .. and a little with me not being patient enough to allow the replication process to complete.