<?xml version="1.0" encoding="UTF-8"?><rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
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/"
> <channel><title>Comments on: VMtoday&#8217;s One Year Anniversary</title> <atom:link href="http://vmtoday.com/2009/11/vmtodays-one-year-anniversary/feed/" rel="self" type="application/rss+xml" /><link>http://vmtoday.com/2009/11/vmtodays-one-year-anniversary/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=vmtodays-one-year-anniversary</link> <description>VMware News, Views, &#38; How-To&#039;s from vExpert Josh Townsend</description> <lastBuildDate>Thu, 10 May 2012 22:21:08 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.2</generator> <item><title>By: Joshua Townsend</title><link>http://vmtoday.com/2009/11/vmtodays-one-year-anniversary/comment-page-1/#comment-210</link> <dc:creator>Joshua Townsend</dc:creator> <pubDate>Mon, 30 Nov 2009 18:39:24 +0000</pubDate> <guid
isPermaLink="false">http://vmtoday.com/?p=277#comment-210</guid> <description>Update 1 was found to have a problem relating to 3rd party management agents.  This was announced on Wednesday, 11/25 and is detailed here: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1016070.  VMware responded quickly to this through social media sites (Twitter, Facebook, blogs, etc.) and on their own KB.  As the problem was further analyzed, the scope of impact was narrowed to just HP Proliant servers running Insight Management Agents.  The Update 1 download is again available on the download site with links to the KB article I reference above.Josh</description> <content:encoded><![CDATA[<p>Update 1 was found to have a problem relating to 3rd party management agents.  This was announced on Wednesday, 11/25 and is detailed here: <a
href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&#038;cmd=displayKC&#038;externalId=1016070" rel="nofollow">http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&#038;cmd=displayKC&#038;externalId=1016070</a>.  VMware responded quickly to this through social media sites (Twitter, Facebook, blogs, etc.) and on their own KB.  As the problem was further analyzed, the scope of impact was narrowed to just HP Proliant servers running Insight Management Agents.  The Update 1 download is again available on the download site with links to the KB article I reference above.</p><p>Josh</p> ]]></content:encoded> </item> <item><title>By: alen</title><link>http://vmtoday.com/2009/11/vmtodays-one-year-anniversary/comment-page-1/#comment-207</link> <dc:creator>alen</dc:creator> <pubDate>Mon, 30 Nov 2009 14:08:50 +0000</pubDate> <guid
isPermaLink="false">http://vmtoday.com/?p=277#comment-207</guid> <description>i just found out the vmware removed the update1 patch from the download section...any comments?</description> <content:encoded><![CDATA[<p>i just found out the vmware removed the update1 patch from the download section&#8230;</p><p>any comments?</p> ]]></content:encoded> </item> <item><title>By: Cody</title><link>http://vmtoday.com/2009/11/vmtodays-one-year-anniversary/comment-page-1/#comment-193</link> <dc:creator>Cody</dc:creator> <pubDate>Tue, 24 Nov 2009 22:07:06 +0000</pubDate> <guid
isPermaLink="false">http://vmtoday.com/?p=277#comment-193</guid> <description>Welcome to 1yr!Go Go GO!</description> <content:encoded><![CDATA[<p>Welcome to 1yr!</p><p>Go Go GO!</p> ]]></content:encoded> </item> </channel> </rss>
<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced
Database Caching 6/31 queries in 0.096 seconds using disk: basic
Object Caching 416/442 objects using disk: basic
Content Delivery Network via Amazon Web Services: CloudFront: cloudfront.vmtoday.com

Served from: vmtoday.com @ 2012-05-17 23:43:40 -->
