<?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>VMware Tools update Archives - ESX Virtualization</title>
	<atom:link href="https://www.vladan.fr/tag/vmware-tools-update/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.vladan.fr/tag/vmware-tools-update/</link>
	<description>VMware ESXi, vSphere, VMware Backup, Hyper-V... how-to, videos....</description>
	<lastBuildDate>Mon, 19 May 2025 06:14:32 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>Vulnerability in your VMs &#8211; VMware Tools Update</title>
		<link>https://www.vladan.fr/vulnerability-in-your-vms-vmware-tools-update/</link>
					<comments>https://www.vladan.fr/vulnerability-in-your-vms-vmware-tools-update/#respond</comments>
		
		<dc:creator><![CDATA[Vladan SEGET]]></dc:creator>
		<pubDate>Mon, 19 May 2025 06:14:32 +0000</pubDate>
				<category><![CDATA[Cloud]]></category>
		<category><![CDATA[Featured]]></category>
		<category><![CDATA[Free Stuff]]></category>
		<category><![CDATA[VMware Tools update]]></category>
		<guid isPermaLink="false">https://www.vladan.fr/?p=233901</guid>

					<description><![CDATA[<p>Recent news about vulnerabilities siting quietly inside our VMware VMs is rather worrying. What if, attacker was going to hack our infrastructure from inside of our VMs? And what if not only Windows VMs, but also Linux VMs were affected? VMware Tools Update is important as your ESXi patch update. This vulnerability is labeled as [&#8230;]</p>
<p>Read the full post <a href="https://www.vladan.fr/vulnerability-in-your-vms-vmware-tools-update/">Vulnerability in your VMs &#8211; VMware Tools Update</a> at <a href="https://www.vladan.fr">ESX Virtualization</a>.</p>
]]></description>
		
					<wfw:commentRss>https://www.vladan.fr/vulnerability-in-your-vms-vmware-tools-update/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Personalized install of VMware tools</title>
		<link>https://www.vladan.fr/personalized-install-of-vmware-tools/</link>
		
		<dc:creator><![CDATA[Vladan SEGET]]></dc:creator>
		<pubDate>Thu, 08 Jul 2010 11:39:27 +0000</pubDate>
				<category><![CDATA[Server Virtualization]]></category>
		<category><![CDATA[VMware tools selection install]]></category>
		<category><![CDATA[VMware Tools update]]></category>
		<category><![CDATA[VSS quiescing]]></category>
		<category><![CDATA[VSS support VMware]]></category>
		<guid isPermaLink="false">http://www.vladan.fr/?p=6581</guid>

					<description><![CDATA[<p>Installation personalized of VMware Tools. As I wrote in my previous article, sometimes when you're using third parties backup agents which installs itself inside of the VM (cause of Symantec BE 2010) there is a need for not installing the full package of vmware tools. You can proceed with a  personalized install of VMware tools [&#8230;]</p>
<p>Read the full post <a href="https://www.vladan.fr/personalized-install-of-vmware-tools/">Personalized install of VMware tools</a> at <a href="https://www.vladan.fr">ESX Virtualization</a>.</p>
]]></description>
		
		
		
			</item>
	</channel>
</rss>
