 




<?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>The musings of an IT Consultant &#187; 3.5</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/it-consultant/tag/35/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/it-consultant</link>
	<description></description>
	<lastBuildDate>Wed, 01 May 2013 01:19:15 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>VMWare &#8211; Major Bug with ESX 3.5 Update 2</title>
		<link>http://itknowledgeexchange.techtarget.com/it-consultant/vmware-major-bug-with-esx-35-update-2/</link>
		<comments>http://itknowledgeexchange.techtarget.com/it-consultant/vmware-major-bug-with-esx-35-update-2/#comments</comments>
		<pubDate>Tue, 12 Aug 2008 15:10:25 +0000</pubDate>
		<dc:creator>Raj Perumal</dc:creator>
				<category><![CDATA[3.5]]></category>
		<category><![CDATA[ESX]]></category>
		<category><![CDATA[ESX 3.5 Update 2]]></category>
		<category><![CDATA[patches]]></category>
		<category><![CDATA[Update 2]]></category>
		<category><![CDATA[VMWare]]></category>
		<category><![CDATA[VMWare bug]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/it-consultant/vmware-major-bug-with-esx-35-update-2/</guid>
		<description><![CDATA[Hi folks, breaking news in the virtual world! Apparently ESX 3.5 Update 2 is wreaking havoc with people&#8217;s ESX servers. According to reports it is throwing &#8220;A general system error occurred: Internal Error&#8221;. This is a known problem at VMWare and there is no known fix as of yet.  You can read more about it [...]]]></description>
				<content:encoded><![CDATA[<p>Hi folks, breaking news in the virtual world! Apparently ESX 3.5 Update 2 is wreaking havoc with people&#8217;s ESX servers. According to reports it is throwing &#8220;A general system error occurred: Internal Error&#8221;. This is a known problem at VMWare and there is no known fix as of yet.</p>
<p> You can read more about it <a href="http://communities.vmware.com/thread/162377?tstart=0">here.</a></p>
<p> This goes back to a rule of thumb I always like to follow with patching. When a patch comes out, don&#8217;t apply it right away. Sit on it for awhile and adopt a wait and see approach to see if there are any ill effects experienced by others in the industry before you apply to your production systems. Also install the patch in a sandbox environment and do a flurry of tests to see if you can get it to break.</p>
<p>After it seems that the patch is acceptable then you can apply it to your production systems. This will save you a lot of headaches in the long run.</p>
<p> -RP</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/it-consultant/vmware-major-bug-with-esx-35-update-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
