<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>VSphere 8.0 on iThinkVirtual™</title><link>https://ithinkvirtual.com/tags/vsphere-8.0/</link><description>Recent content in VSphere 8.0 on iThinkVirtual™</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 08 Jan 2025 19:33:24 -0500</lastBuildDate><atom:link href="https://ithinkvirtual.com/tags/vsphere-8.0/index.xml" rel="self" type="application/rss+xml"/><item><title>Nested vSphere Home Lab – Part 3 – vSphere 8.x Lab Deployment</title><link>https://ithinkvirtual.com/posts/nested-vsphere-home-lab-part-3-vsphere-8-x-lab-deployment/</link><pubDate>Sat, 06 Jan 2024 20:22:55 -0500</pubDate><guid>https://ithinkvirtual.com/posts/nested-vsphere-home-lab-part-3-vsphere-8-x-lab-deployment/</guid><description>&lt;h2 id="intro">Intro&lt;/h2>
&lt;p>Welcome back! In my &lt;a href="https://ithinkvirtual.com/2023/04/23/nested-vsphere-home-lab-part-2-active-directory-certificate-authority/">previous&lt;/a> post, I covered the deployment and configuration of an Active Directory and Microsoft Certificate Authority server(s) for the nested lab environment.&lt;/p>
&lt;p>Next, I will cover the steps used to deploy the nested lab via William Lam&amp;rsquo;s Automated Nested Lab Deployment &lt;a href="https://github.com/lamw/vsphere-8-lab-deployment">script&lt;/a>. This script makes it easy to deploy a set of vSphere Hypervisor (ESXi) VMs, along with a VMware vCenter Server Appliance virtual machine to manage the nested lab environment.&lt;/p></description></item><item><title>Nested vSphere Home Lab - Part 2 - Active Directory &amp; Certificate Authority</title><link>https://ithinkvirtual.com/posts/nested-vsphere-home-lab-part-2-active-directory-certificate-authority/</link><pubDate>Sun, 23 Apr 2023 21:05:13 -0400</pubDate><guid>https://ithinkvirtual.com/posts/nested-vsphere-home-lab-part-2-active-directory-certificate-authority/</guid><description>&lt;h2 id="intro">Intro&lt;/h2>
&lt;p>Welcome back! In my &lt;a href="https://ithinkvirtual.com/2023/04/23/nested-vsphere-home-lab-part-1-sophos-firewall/">previous&lt;/a> post, I covered the deployment and configuration of a virtual &lt;a href="https://www.sophos.com/en-us/products/free-tools/sophos-xg-firewall-home-edition.aspx">Sophos XG Firewall&lt;/a> router appliance to provide routing services for the nested lab environment.&lt;/p></description></item><item><title>Nested vSphere Home Lab – Part 1 – Sophos Firewall</title><link>https://ithinkvirtual.com/posts/nested-vsphere-home-lab-part-1-sophos-firewall/</link><pubDate>Sun, 23 Apr 2023 21:03:00 -0400</pubDate><guid>https://ithinkvirtual.com/posts/nested-vsphere-home-lab-part-1-sophos-firewall/</guid><description>&lt;h2 id="intro">Intro&lt;/h2>
&lt;p>Welcome to Part 1 of my Nested vSphere Home Lab Series. In my &lt;a href="https://ithinkvirtual.com/2023/03/24/nested-vsphere-home-lab-series-2023/">previous post&lt;/a>, I went over the gist of what I plan to do for my nested Nested &lt;a href="https://www.vmware.com/products/vsphere.html">vSphere&lt;/a> Home Lab. In this post, I will cover the setup and configuration of a &lt;a href="https://www.sophos.com/en-us/products/free-tools/sophos-xg-firewall-home-edition.aspx">Sophos XG Firewall Home Edition&lt;/a> which will serve as the router for my nested lab environment. My physical Home Lab is configured with Virtual Distributed Switches, or VDS (sometimes seen as DVS) for short, and since this is a nested lab environment that will not have any physical uplinks connected, I will need to create a new VDS without physical uplinks connected to it along with a portgroup for the nested environment and then configure access to the environment from my LAN. This can also be configured on a Virtual Standard Switch, or VSS for short, in the same fashion. All network traffic will flow through the virtual router/firewall to communicate to and from the nested lab. Afterward, I&amp;rsquo;ll cover the Active Directory Server setup.&lt;/p></description></item></channel></rss>