PKI Fresh re-Installation after badly configured first attempt

hi, 

i've been getting grips operations of 2 tier pki (offline root , online issuing/policy ca's) , previous installation of ad cs i've uninstalled, there's data in configuration naming context within ad still. 

there's entries relating original - uninstalled - pki in:-

cn=aia,cn=public key services,cn=services,dc=domain,dc=local
cn=cdp,cn=public key services,cn=services,dc=domain,dc=local
cn=certificate templates,cn=public key services,cn=services,dc=domain,dc=local
cn=certification authorities,cn=public key services,cn=services,dc=domain,dc=local
cn=kra,cn=public key services,cn=services,dc=domain,dc=local
cn=oid,cn=public key services,cn=services,dc=domain,dc=local

in new test domain (yes should have done in test first - i've got test servers i've running new processes on) there's 0 entries in these locations safe in saying can go hacking these old entries out of ad before install new ad cs implementation?

fyi, there nothing in operational domain that's relying on pki, there no auto enrollment done or that. 

i want ad , feel if got right first time round , first installation using ad cs, though i've described, isn't.

regards

paul.

do not delete of oids oid container. delete specific oids application policies or certificate policies have created. can use adsiedit.msc verify custom oids vieiwing cn attribute.

brian

Windows Server  >  Security