ere is the agenda from our live Q&A at our PKI Solutions "Office Hours." - the Migration Edition
While our focus was on Windows Server 2012 R2 migration "common gotchas", questions and concerns about this topic, and specifically how to align key, certificate infrastructure strategy with the cloud first approach, developer productivity and strategic business initiatives were all touched on.
Attendees had an opportunity to ask us anything within the webinar's chat function.
Even attendees that thought they had 100% of their Windows Server 2012 R2 migration issues handled by the right staff with the right skillset found that there are OFTEN issues that slip through the cracks. We address some of those questions and concerns in the transcript we are uploading to our site.
If you are facing challenges migrating your PKI and have issues with remote access, availability, scale, and management, we are here to help.
- Shawn Rabourn, CTO, PKI Solutions
- Mark B. Cooper, president and founder, PKI Solutions, aka The PKI Guy
2. Agenda
• Windows Server 2012 R2 End of Support: Frequently Asked Questions
• Migration Preparation Discussion
• Top 10 Migration Issues
• Additional Q&A
8. • Do you thoroughly know the state and components in your PKI?
• Is the PKI worth keeping and migrating?
• Has your business use cases changed since the PKI was deployed?
• Have you tested your migration plan?
• What is your backout plan?
What can I do to prepare for my migration?
Things to check to assess your readiness.
9. What are the 10 most common
“gotchas” my team might miss?
12. No recent CA Backup -
Considerably increases backup
time. Check for *.log files
13. Broken/Failing CAs - If the CA is in
poor shape, the migration will likely
not be successful
14. Hardware Security Modules -
Migrating CAs, OCSP, NDES with
NDES integration with break key
and certificate binding.
Requires manual "reconnection"
15. Missing Keys - If you CA has been
previously renewed with a new key,
make sure ALL CA keys are backed
up and moved.
16. Expiring CRLs - Make sure your
CRLs will be valid for the expected
period of migration
17. Backups and Templates - Ensure
your CA doesn't continue to issue
certificates after it is backed up, and
service is still running prior to
migration
18. CDP Publishing ACLs - Ensure
network based CAs can access and
update CRL locations after
migration
19. Handling LDAP based variables
(%2) - Migrating CA to a new host
name will affect how CDP locations
are parsed by the CA
20. Questions?
1 . A sk f u r t h er q u est i o n s
2 . G et an assessm en t o n yo u r
P K I en vi r o n m en t
3 . G et so l u t i o n s
Reach out today for an
assessment
Schedule today
On e o f o u r e x p e r t s w i l l h e l p
c r a f t y o u r P K I s t r a t e g y
For details contact:
Carolyn Ballo, Client Relationship Manager
carolyn@pkisolutions.com