<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>How to create a nested ESXi 6.5 Template Archives - ESX Virtualization</title>
	<atom:link href="https://www.vladan.fr/tag/how-to-create-a-nested-esxi-6-5-template/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.vladan.fr/tag/how-to-create-a-nested-esxi-6-5-template/</link>
	<description>VMware ESXi, vSphere, VMware Backup, Hyper-V... how-to, videos....</description>
	<lastBuildDate>Mon, 30 Jan 2017 09:13:50 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.4</generator>
	<item>
		<title>How to create a nested ESXi 6.5 Template</title>
		<link>https://www.vladan.fr/how-to-create-a-nested-esxi-6-5-template/</link>
		
		<dc:creator><![CDATA[Vladan SEGET]]></dc:creator>
		<pubDate>Mon, 30 Jan 2017 10:45:30 +0000</pubDate>
				<category><![CDATA[Server Virtualization]]></category>
		<category><![CDATA[How to create a nested ESXi 6.5 Template]]></category>
		<guid isPermaLink="false">http://www.vladan.fr/?p=200405</guid>

					<description><![CDATA[<p>The way of installing or creating ESXi hosts as VMs (mean nested virtualization) has changed many times in the past. But as VMware introduces new features and improvements in every release of vSphere, the time has come again to check what's the best practices and How to create a nested ESXi 6.5 template. It is [&#8230;]</p>
<p>Read the full post <a href="https://www.vladan.fr/how-to-create-a-nested-esxi-6-5-template/">How to create a nested ESXi 6.5 Template</a> at <a href="https://www.vladan.fr">ESX Virtualization</a>.</p>
]]></description>
		
		
		
			</item>
	</channel>
</rss>
