<?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 EXPLORE 2024 Archives - ESX Virtualization</title>
	<atom:link href="https://www.vladan.fr/tag/vmware-explore-2024/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.vladan.fr/tag/vmware-explore-2024/</link>
	<description>VMware ESXi, vSphere, VMware Backup, Hyper-V... how-to, videos....</description>
	<lastBuildDate>Tue, 27 Aug 2024 13:24:55 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.3</generator>
	<item>
		<title>VMware vDefend 4.2 announcement &#8211; VMware EXPLORE 2024</title>
		<link>https://www.vladan.fr/vmware-vdefend-4-2-announcement-vmware-explore-2024/</link>
		
		<dc:creator><![CDATA[Vladan SEGET]]></dc:creator>
		<pubDate>Tue, 27 Aug 2024 13:24:55 +0000</pubDate>
				<category><![CDATA[Cloud]]></category>
		<category><![CDATA[VMware EXPLORE 2024]]></category>
		<guid isPermaLink="false">https://www.vladan.fr/?p=233183</guid>

					<description><![CDATA[<p>This blog post is from a VMware/Broadcom NDA briefing before VMware EXPLORE 2024 Las Vegas. The NDA has finished the 27th of August 2024. VMware vDefend now is a security solution that is formerly known as VMware NSX Security Solutions. Enterprises do need a comprehensive solution that requires visibility that requires micro segmentation, application, level [&#8230;]</p>
<p>Read the full post <a href="https://www.vladan.fr/vmware-vdefend-4-2-announcement-vmware-explore-2024/">VMware vDefend 4.2 announcement &#8211; VMware EXPLORE 2024</a> at <a href="https://www.vladan.fr">ESX Virtualization</a>.</p>
]]></description>
		
		
		
			</item>
	</channel>
</rss>
