In the last post we finished building the lab, all components are in place to actually follow the lab guide now. So the next couple of posts will consist of shorter lab exercises the students had to do during the actual training to get comfortable with using SSO and replacing/troubleshooting SSL certificates in a vSphere environment.
This time we will be setting up the vCenter Server for one of the lab sessions later. Since we intentionally want to break something we need a very specific procedure though.
After a little mishap in November (found a bug in the system, yay!) I could finally sit (and pass) the VCIX-NV exam yesterday. I will skip through telling about the obvious stuff like length and number of questions as they can be easily found in the exam blueprint.
As indicated in the last post this one will deal with the actual install and setup of the lab infrastructure. We will need 4 VMs as the basic minimum configuration. So let’s start by building out the Domain Controller machine.
As promised I wanted to start a small series on the content I developed to internally train TSEs to better handle SSL and SSO cases in vCenter Server 5.5. The whole training went from a mere 1 hour presentation to a full 2 day course and could easily enough be extended by another set of lab exercises and adding different products. As there is no hands on lab for replacing SSL certificates yet
Today was a rather productive day in terms of resolved cases, it sure helps to be part of the frontline again during the times of low staffing though, finally some easy stuff to deal with again 🙂
I am currently in the process of going through all my old slide decks and finally finishing the lab manual for the nasty lab that I used for training fellow Technical Support Engineers on SSL and SSO. The following slide deck might be a bit older but still useful for those who are still using Single Sign-On 5.1 (you really shouldn’t be though…). I solved a majority of the support calls we received regarding SSO just using the methods in that slide deck.
If I find the time for it I also plan to create a small series on how to recreate the “nasty lab” and develop a public version of the lab manual. The plan is that this manual will contain the majority of customer issues seen on a Windows based vCenter in version 5.5 that touch either SSO or SSL topics.
It looks like VMware modified the NSX beginner lab 1403 so that the tasks now are completely independent of each other and can be done in pretty much any order. Unfortunately this process lost all of the initial configuration steps that were included in the actual lab.
In a recent training for vCenter Server Orchestrator 5 we had to build a workflow that would leverage an email server to send mails. The lab was more of a theoretical practice as no actual email server was installed and a full blown Exchange is overkill for most homelab scenarios. I also do prefer Windows over any sendmail configuration at any point in time and have discovered hMailServer to be a perfect fit for my lab setups.
I had a customer a while ago who was unable to log in into the additional created tenant in vCloud Automation Center 6.0.1. The same issue can be reproduced in vRealize Automation as well. Logins to the default tenant would succeed without any issues and a very similar test environment did work without any issues at all for logins.