rss-post-importer domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home1/yelofcom/public_html/wp-includes/functions.php on line 6121graphene domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home1/yelofcom/public_html/wp-includes/functions.php on line 6121
Jun 13
In a previous blog post I went over the details on how ESXi uses a TPM 2.0 chip to provide assurance that Secure Boot did its job and how that “attestation” rolls up to vCenter to be reported on.
In this blog article I’m going to go over some of steps necessary to configure the ESXi host to use TPM 2.0 chip. Now, I have only a limited number of hardware systems in my lab from which to do this, but the steps should be familiar, regardless of the server model.
Jun 06
When 6.7 went “GA” or General Availability, I was excited to get it installed and running on my bare metal hosts in my lab here at VMware. I had gotten my Dell R630’s updated with TPM 2.0 chips and was looking forward to booting with “attested” hosts. But I had a few issues before I was able to get everything working. This blog article is Part 1 of a two part series on how to configure your hosts to use Secure Boot and TPM 2.0.
May 04
As our vSphere 6.7 Security Week comes to a close I’d like to leave you with some more content. In this blog I’ll share with you a number of videos, walkthroughs and a podcast on all the 6.7 security features that have been covered so far.