VmWare vSphere Administration Lab
IP Addressing
You will be assigning static IPs to your systems in this lab. Please use these settings:
- Subnet Mask: 255.255.255.0
- Default Gateway: 192.168.1.1
- DNS Server 192.168.1.1
| System | IP |
|---|---|
| HV-A | 192.168.1.20 |
| HV-B | 192.168.1.21 |
| VCSA | 192.168.1.22 |
Instructions
- Boot your ESXi Server systems (the two hv systems)
- Boot your VCSA VM Appliance using the ESXi web interface on the ESXi system hosting VCSA.
- Use the VCSA web interface to create a new VM which is running on an ESXi server OTHER than the one running VCSA (so more RAM is available) to install Windows Server 2019. You will need a VM with 2GB RAM and a 50GB hard drive minimum.
- Complete the installation of Windows Server 2019 into the new VM.
- NOTE: Click the link that you do not have a key and install the standard version of Server 2016, this will give you a trial license.
- NOTE: You will need to upload the ISOs to the datastore on the ESXi system which you are creating the VM on before you can install the systems. This uploading can be done through VCSA from your remote pod PC.
- The Windows Server 2019 installation ISO files can be found on the Windows SMB share "\\san1.campus.ihitc.net\Student Files\ITC2300" which you can access from your remote desktop VM. Use your VPN login credentials but with @campus.ihitc.net on the end like username@campus.ihitc.net to access the files.
- Add the Active Directory Domain Services role to the server. Use "podX-ad.local" (where X is your pod number) as the root domain name and "podX-ad" as the NetBIOS domain name.
- While the Active Directory role is installed and the domain controller promotion script is running (these will take some time to complete) continue through this lab.
- It's sometimes the case that you may have a malfunctioning web interface and need to start some critical VMs such as VCSA and some Active Directory servers only through the host command line interface. We'll simulate this setup by checking the status and powering on one of your previously installed Linux or Windows VMs through this host console.
- Use the host command line console on your ESXi machines to get a list of the VMs registered at each host.
- Use the host command line console on your ESXi machines to check the power status of one of your previously installed Linux or Windows VMs (they should be off)
- Verify the VMs are off in the vCenter Server web client
- Use the host command line console on your ESXi machines to power on one of your previously installed Linux or Windows VMs.
- Verify the VM is powering on through both the host command line console on your ESXi machine as well as through the vCenter web interface.
- Another useful virtual machine task is to set certain VMs to automatically power on when the ESXi server powers on. Read the VMware documentation on the topic.
- Set the VCSA VM to automatically power on with the ESXi host.
- One benefit of the vCenter Server system is that you can migrate VMs from one ESXi host to another. First let's try this with a powered off virtual machine.
- Choose one of the powered off VMs on one of your hosts in the VCSA Web Client. On the summary tab check to see which host the VM currently resides on.
- Right click on it and choose migrate to open the migration wizard. You want to move both the compute (CPU/RAM) and storage (disk images) to a new host so make that selection.
- Select a different ESXi server and a datastore attached to that server and begin the migration.
- Once the migration is complete check that the VM shows it is on a different host and verify that it still powers up and works.
- An even more powerful tool is to be able to migrate VMs while they are running, VMware calls this feature vMotion. Take the same VM and try the migration process again (back to the original host) while the machine is powered on.
- This may take quite a bit longer to complete so let's go back to our Windows Server setup while the vMotion magic is happening.
- It would be nice to have a single sign on for VMware vCenter Server users which is backed by our Active Directory domain so let's see if we can get that running.
- Follow the VMware instructions for adding a vCenter Server Single Sign-On identity source. You may also need to read the Active Directory Identity Source Settings.
- NOTE: You will need to know the Base DN for the users and groups in your Active Directory. A Base DN is a path to the location in Active Directory where something is stored (in this case user accounts and groups). You may need to do some research online and make some inferences to figure out what your Base DNs are.
- You are going to want to setup Active Directory as an LDAP server so that you don't need to join your VCSA system to your domain. Instructions for setting that up can be found here.
- NOTE: If you instead want to try joining your VCSA system to the domain and using Integrated Windows Authentiction see https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vcsa.doc/GUID-08EA2F92-78A7-4EFF-880E-2B63ACC962F3.html how to join the vCenter Server Appliance to an Active Directory Domain].
- Create a new user account in AD and then try adding it as an administrator in vCenter Server.
- Try logging in with the new account to your vCenter Server web interface.
- Safely shutdown all running VMs except VCSA
- Safely shutdown the VCSA appliance
- Safely shutdown all ESXi hosts
- Disconnect from the VPN