<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Lab Deployment on Matt Allford</title><link>https://www.mattallford.com/tags/lab-deployment/</link><description>Recent content in Lab Deployment on Matt Allford</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 07 Apr 2017 12:04:57 +0000</lastBuildDate><atom:link href="https://www.mattallford.com/tags/lab-deployment/index.xml" rel="self" type="application/rss+xml"/><item><title>Additions To vGhetto Automated vSphere Lab Deployment</title><link>https://www.mattallford.com/additions-to-vghetto-automated-vsphere-lab-deployment/</link><pubDate>Fri, 07 Apr 2017 12:04:57 +0000</pubDate><guid>https://www.mattallford.com/additions-to-vghetto-automated-vsphere-lab-deployment/</guid><description>&lt;p&gt;So last week I received a new lab server that is going to be housed at home. It is a Dell T430 with 128GB ram, which is exactly what I was after as I want to get right back into the lab work, but I didn&amp;rsquo;t want a heap of gear and network requirements. NestedESXi has worked reasonably well in the past few vSphere releases and there&amp;rsquo;s not much that can&amp;rsquo;t be simulated within a nested environment for the purposes of learning or testing.&lt;/p&gt;</description></item></channel></rss>