You are reading the blog of @PSUStevens. You can reach me through one of the social accounts below.
This post will walk through the steps to connect Entrust KeyControl to Active Directory.
To get started here is what you will need to complete the steps in this post:
A deployed Entrust KeyControl v5.4 cluster (Click this sentence to learn how to do this) Active Directory service account Now, let’s get started…
Connect KeyControl to Active Directory Log in to the deployed Entrust KeyControl cluster.
Read how easy it is to deploy a 2-node Entrust (formerly HyTrust) KeyControl Key Management Server (KMS) for encrypting sensitive data in virtual machines.
Around this time last year I wrote about how to deploy a 2-node HyTrust KeyControl cluster. That post covered KeyControl version 5.2.1. You can find that blog post over here.
This post is very similar. The difference between it and the last post is that I will cover Entrust KeyControl version 5.
See how easy it is to deploy a 2-node HyTrust KeyControl v5.2.1 Key Management Server (KMS) for encrypting sensitive data in virtual machines.
To get started here is what you will need to complete the steps in this post:
KeyControl OVA v5.2.1 vCenter and ESX host at least version 6.5 or greater 2 vCPU, 8GB RAM, 60GB disk per KeyControl node Network address information such as: IP address (one per node) Subnet mask Gateway address DNS server information DNS registered hostname for each node Deploy the First HyTrust KeyControl Appliance Log in to the Virtual Center Appliance (VCSA).
This is my personal blog about technical topics including virtualization, storage, networking, backups, and some random IT stuff that strikes my fancy.