Root CA migration


we have domain controller "dc01" has enterprise certificate services role installed , ca on domain controller named "dc01"
the cdp location on ca "dc01" <servername> it's ldap://dc01 (only ldap published on certificates, no http etc.)
the ca "dc01" issues version1 "computer" certificates autoenrollment clients , our internal clients , external clients have "computer" certificate ca "dc01"

now have uag sp3 server direct access , our clients connect successfull direct access it's setup now
in uag configuration (wizard) on ipsec certificate authentication screen on option "use certificate trusted root ca" "dc01" root ca certificate selected

as microsoft best-practises want move enterprise certificate services new member server "cs01" , create new root ca "cs01"

as use version1 "computer" certificate template cannot select "reenroll certificate holders"
so idea duplicate "computer" certificate template v2 template supersedes version1 computer template, replaces current computer certificates based on old v1 computer template on clients.
then clients new "computer" certificate new root ca in uag direct access configuration "ipsec certificate authentication" "use certificate trusted root ca" old "dc01" root ca certificate still selected

question1; lock out clients have new computer certificate new root ca uag direct access configuration still use root ca certificate old dc01 ca?

another idea not supersede the version1 computer certificate autoenroll new v2 duplicated computer template.
this means clients have computer certificate old ca "dc01" computer certificate new ca "cs1"

question2; can client have 2 computer certificates (1 old dc01 ca , 1 new cs01 ca) , connect direct access , still work?

for clarification say:

"the cdp location on ca "dc01" <servername> it's ldap://dc01 (only ldap published on certificates, no http etc.)"

i suspect may misinterpreting configuration. ldap entry default not tied specific dc, file placed in ad named after server. clients go domain controller retrieve information. not way me know sure, highly unusual if ldap entry changed specific dc only.

question 1: not clear if intending keep old ca. list original root ca dc01 reference new ca cs01. can not rename ca, if reading correctly, creating new root ca , abandoning old one. on related note, recommend more descriptive names cas aren't tied server. contoso root ca example. 

if creating new ca, old uag rule has specific trusted ca listed not work new ca. either need create new rule or migrate old ca , keep old name , keypair/certificate. 

the supersede best way clients re-enroll increase speed of moving clients new ca. not necessary if migrating root.

question 2: yes, clients can have more 1 certificate in store 1 or more cas. however, connection profiles "stick" last used certificate until no longer available or authentication has failed. further, if go the supersede route, old certificate no longer in personal store use.


mark b. cooper, president , founder of pki solutions inc., former microsoft senior engineer , subject matter expert microsoft active directory certificate services (adcs). known “the pki guy” @ microsoft 10 years. connect mark @ http://www.pkisolutions.com



Windows Server  >  Security



Comments

Popular posts from this blog

Edit Group Policy

Hyper-V VM not reaching OS 'Logon' screen

DNS question...