TAPI3 in Active Directory
Posted on 2006-07-17
I have two Win2003 Server DCs in a small (test) domain; I am planning to replace the original DC (with FISMOs). When I started to run dcpromo to demote the server from DC to standalone, I received a warning indicating that the DC contained the only copy of a TAPI3 application directory; replmon did indeed show a TAPI3 AD partition with no replication configured. I have no idea how the application partition came to be - I don't use (or test) any TAPI related software.
Note - I am the only domain admin (this is my own test domain) so no one might have put it there.
1. Where might this have come from? I would not have created this intentionally; could Windows have created this, is it a part of the fax services (which I may have tried installing once).
2. How can I browse the contents of the partition to see what is actually there (and maybe even why it is there)?
3. How can I enable replication on the partition so it will survive the DC replacement?
4. Can I simply ignore the TAPI application partition? Sure, it will be obliterated, but since it is unlikely that there is anything important in it, that may be the best solution.