<?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: General System Error occurred: Internal error</title>
	<atom:link href="http://www.vdi.co.nz/2008/08/12/general-system-error-occurred-internal-error/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.vdi.co.nz/2008/08/12/general-system-error-occurred-internal-error/</link>
	<description></description>
	<lastBuildDate>Wed, 17 Feb 2010 15:30:44 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Oops! VMware's VI 3.5 Update 2 locks out customers, pulls Update 2 download. - Gabe Knuth - BrianMadden.com</title>
		<link>http://www.vdi.co.nz/2008/08/12/general-system-error-occurred-internal-error/comment-page-1/#comment-29</link>
		<dc:creator>Oops! VMware's VI 3.5 Update 2 locks out customers, pulls Update 2 download. - Gabe Knuth - BrianMadden.com</dc:creator>
		<pubDate>Tue, 30 Sep 2008 18:33:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.vdi.co.nz/?p=18#comment-29</guid>
		<description>[...] on the street is that VMware Infrastructure 3.5 Update 2 and ESXi 3.5 Update 2 have been affected by a [...]</description>
		<content:encoded><![CDATA[<p>[...] on the street is that VMware Infrastructure 3.5 Update 2 and ESXi 3.5 Update 2 have been affected by a [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://www.vdi.co.nz/2008/08/12/general-system-error-occurred-internal-error/comment-page-1/#comment-10</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Wed, 13 Aug 2008 01:29:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.vdi.co.nz/?p=18#comment-10</guid>
		<description>@ chandran &amp; rajheet. keep an eye on http://kb.vmware.com/kb/1006716.

temporary workaround is to put the date back of the host &amp; power the vm&#039;s on while it booting, change to current  date</description>
		<content:encoded><![CDATA[<p>@ chandran &#038; rajheet. keep an eye on <a href="http://kb.vmware.com/kb/1006716" rel="nofollow">http://kb.vmware.com/kb/1006716</a>.</p>
<p>temporary workaround is to put the date back of the host &#038; power the vm&#8217;s on while it booting, change to current  date</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VMware ESX 3.5 update 2 August 12 bug - Cult of the Bicycle</title>
		<link>http://www.vdi.co.nz/2008/08/12/general-system-error-occurred-internal-error/comment-page-1/#comment-8</link>
		<dc:creator>VMware ESX 3.5 update 2 August 12 bug - Cult of the Bicycle</dc:creator>
		<pubDate>Tue, 12 Aug 2008 17:04:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.vdi.co.nz/?p=18#comment-8</guid>
		<description>[...] ESX 3.5 update 2 August 12 bug   Work. This is the bug. It bit me hard. The workaround is lame. The bug is lame. Me spending half the night trying to [...]</description>
		<content:encoded><![CDATA[<p>[...] ESX 3.5 update 2 August 12 bug   Work. This is the bug. It bit me hard. The workaround is lame. The bug is lame. Me spending half the night trying to [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rajheet</title>
		<link>http://www.vdi.co.nz/2008/08/12/general-system-error-occurred-internal-error/comment-page-1/#comment-7</link>
		<dc:creator>Rajheet</dc:creator>
		<pubDate>Tue, 12 Aug 2008 16:35:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.vdi.co.nz/?p=18#comment-7</guid>
		<description>Chandran, you might consider choosing a more direct update, like a phone call or other update directly from the offending vendor, in this instance, VMware, as opposed to looking to a blog for an update.  Since your &quot;entire organization runs on VM and we are is serouse situation now&quot;.  Expecting a blog to reply to you because you&#039;ve posted that it&#039;s urgent is somewhere between foolish and incompetent.  It&#039;s urgent for tens of thousands of ESX users around the world, you tool.  Sorry english my broken not good so, very much to be thanking you.  Ugh.  Get a clue.</description>
		<content:encoded><![CDATA[<p>Chandran, you might consider choosing a more direct update, like a phone call or other update directly from the offending vendor, in this instance, VMware, as opposed to looking to a blog for an update.  Since your &#8220;entire organization runs on VM and we are is serouse situation now&#8221;.  Expecting a blog to reply to you because you&#8217;ve posted that it&#8217;s urgent is somewhere between foolish and incompetent.  It&#8217;s urgent for tens of thousands of ESX users around the world, you tool.  Sorry english my broken not good so, very much to be thanking you.  Ugh.  Get a clue.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://www.vdi.co.nz/2008/08/12/general-system-error-occurred-internal-error/comment-page-1/#comment-6</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Tue, 12 Aug 2008 10:38:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.vdi.co.nz/?p=18#comment-6</guid>
		<description>Yea saw the Kb. Once the vm&#039;s are powerd on, can change it to current date</description>
		<content:encoded><![CDATA[<p>Yea saw the Kb. Once the vm&#8217;s are powerd on, can change it to current date</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PhoenixCH</title>
		<link>http://www.vdi.co.nz/2008/08/12/general-system-error-occurred-internal-error/comment-page-1/#comment-5</link>
		<dc:creator>PhoenixCH</dc:creator>
		<pubDate>Tue, 12 Aug 2008 09:15:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.vdi.co.nz/?p=18#comment-5</guid>
		<description>http://communities.vmware.com/thread/162377?tstart=0

KB (temporary not available)
http://kb.vmware.com/kb/1006716</description>
		<content:encoded><![CDATA[<p><a href="http://communities.vmware.com/thread/162377?tstart=0" rel="nofollow">http://communities.vmware.com/thread/162377?tstart=0</a></p>
<p>KB (temporary not available)<br />
<a href="http://kb.vmware.com/kb/1006716" rel="nofollow">http://kb.vmware.com/kb/1006716</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://www.vdi.co.nz/2008/08/12/general-system-error-occurred-internal-error/comment-page-1/#comment-4</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Tue, 12 Aug 2008 09:12:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.vdi.co.nz/?p=18#comment-4</guid>
		<description>Yes have restarted the VC. I will post here as soon as I hear about the patch. The company I work is a VIP Enterprise and VAC Partner.</description>
		<content:encoded><![CDATA[<p>Yes have restarted the VC. I will post here as soon as I hear about the patch. The company I work is a VIP Enterprise and VAC Partner.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
