I am in the middle of upgrading our AD/Domain from 2003 to 2012. Due to recent turnover we don't have a clear answer on what/who created the TAPI3 application partition. When running dcpromo to demote the 2003 dc, I am notified that TAPI3DIRECTORY is only on this DC, so I have done the following:
From the original domain controller (after migrating all fsmo roles off) I run:
ntdsutil:
domain management
connections
connect to server originaldc.xxx.local
q
add nc replication dc=tapi3directory,dc=xxx,dc=local newdc.xxx.local
The command completes successfully (no errors), I then can dcpromo/demote the original domain controller with no problem. Is it safe to say that the tapi3directory is now on the new domain controller and available should anything need to reference/access it?
