You are reading the blog of @PSUStevens. You can reach me through one of the social accounts below.
With 2021 in the rear view mirror I wanted to look back and talk about some recent changes that have already transpired in 2021
Most people post their New Years’ blog posts within the first week of the new year. But, there have been some things brewing that I needed to wait to complete. This blog post isn’t like my other posts. It’s a brief look back at what transpired in 2020 and what I hope to accomplish this year.
In vCenter 7 VMware moved away from the term KMS (Key Management Server) to Key Provider. This post will explain how to add HyTrust KeyControl as a Key Provider in vCenter 7.
Introduction In my How to Deploy a HyTrust KeyControl 2-node Cluster post I walked through the steps for deploying and configuring a 2-node HyTrust KeyControl cluster. Now that you have it deployed, let’s start using it. But before we can do that, we need to add it vCenter as a Key Provider.
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.