<?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>V blog &#187; ESX</title>
	<atom:link href="http://www.vdi.co.nz/category/esx/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.vdi.co.nz</link>
	<description></description>
	<lastBuildDate>Tue, 17 Jan 2012 04:53:33 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>MSCS nodes with RDM LUNs slow to boot</title>
		<link>http://www.vdi.co.nz/2011/04/20/mscs-nodes-with-rdm-luns-slow-to-boot/</link>
		<comments>http://www.vdi.co.nz/2011/04/20/mscs-nodes-with-rdm-luns-slow-to-boot/#comments</comments>
		<pubDate>Wed, 20 Apr 2011 10:50:19 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[ESX]]></category>
		<category><![CDATA[ESXi]]></category>
		<category><![CDATA[MSCS]]></category>
		<category><![CDATA[SQL Node]]></category>

		<guid isPermaLink="false">http://www.vdi.co.nz/?p=309</guid>
		<description><![CDATA[This was one of the frustrating thing to wait for the node to boot.  Finally found a solution I was looking for. For ESX and ESXi 4.0 hosts The Scsi.UWConflictRetries parameter for ESX/ESXi 4 Update 1 hosts have a default value of 1000. This increases the time spent enumerating LUN and VMFS volumes. To resolve this issue and to speed up [...]]]></description>
			<content:encoded><![CDATA[<p>This was one of the frustrating thing to wait for the node to boot.  Finally found a solution I was looking for.</p>
<h4><span style="color: #000000;">For ESX and ESXi 4.0 hosts</span></h4>
<div>The Scsi.UWConflictRetries  parameter for ESX/ESXi 4 Update 1 hosts have a default value of 1000.  This increases the time spent enumerating LUN and VMFS volumes.</div>
<div>To resolve this issue and to speed up the boot process, modify this value to 80.</div>
<div><strong> </strong></div>
<div>To modify the Scsi.UWConflictRetries parameter from the GUI:</div>
<ol>
<li>Go to <strong>Host</strong> &gt; <strong>Configuration</strong> &gt; <strong>Advanced settings</strong>.</li>
<li>In the Advanced settings window, select <strong>SCSI</strong>.</li>
<li>Change the <strong>Scsi.UWConflictRetries</strong> value to 80.</li>
</ol>
<h4><span style="color: #000000;"><strong>For ESX and ESXi 4.1 hosts</strong></span></h4>
<div>To resolve this issue in ESX/ESXi 4.1 hosts, you must modify the Scsi.CRTimeoutDuringBoot parameter from the GUI.</div>
<div>To modify the Scsi.CRTimeoutDuringBoot parameter:</div>
<ol>
<li>Go to <strong>Host </strong>&gt; <strong>Configuration</strong> &gt; <strong>Advanced Settings</strong>.</li>
<li>Select <strong>SCSI</strong>.</li>
<li>Change the Scsi.CRTimeoutDuringBoot value to 1.</li>
</ol>
<p><a href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1016106" target="_blank">http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1016106 </a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.vdi.co.nz/2011/04/20/mscs-nodes-with-rdm-luns-slow-to-boot/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Error 1316 A network error occurred while attempting to read the file</title>
		<link>http://www.vdi.co.nz/2010/05/15/error-1316-a-network-error-occured-while-atempting-to-read-the-file/</link>
		<comments>http://www.vdi.co.nz/2010/05/15/error-1316-a-network-error-occured-while-atempting-to-read-the-file/#comments</comments>
		<pubDate>Sat, 15 May 2010 10:28:47 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[ESX]]></category>
		<category><![CDATA[VMware]]></category>
		<category><![CDATA[error 1316]]></category>
		<category><![CDATA[server 2008]]></category>
		<category><![CDATA[vmware tools]]></category>

		<guid isPermaLink="false">http://www.vdi.co.nz/?p=269</guid>
		<description><![CDATA[Came across this error &#8220;Error 1316 A network error occurred while attempting to read the file&#8221; when updating server 2008 vmware tools. Unable to uninstall the old version either. This is an issue with Microsoft Windows Installer and does not affect all Windows 2008 systems. The problem can occur when the original install path from [...]]]></description>
			<content:encoded><![CDATA[<p>Came across this error &#8220;Error 1316 A network error occurred while attempting to read the file&#8221; when updating server 2008 vmware tools. Unable to uninstall the old version either.</p>
<p>This is an issue with Microsoft Windows Installer and does not affect all Windows 2008 systems. The problem can occur when the original install path from the older version of VMware Tools is invalid</p>
<p>To correct this issue, you must perform a forced uninstall and re-install of VMware Tools.</p>
<p>To uninstall and re-install VMware Tools:</p>
<p>   1. Right-click on the virtual machine.<br />
   2. Click Guest > Install/Upgrade VMware Tools.<br />
   3. Open a Console to the virtual machine and log into the guest operating system.<br />
   4. Click Start > Run, type cmd, and click OK to open a command prompt in Windows.<br />
   5. Change the drive to your CD-ROM drive. For example, D:\.<br />
   6. Type setup /c and press Enter to force removal of all registry entries and delete the old version of VMware Tools.<br />
   7. In My Computer, double click the CD-ROM that contains VMware Tools.<br />
   8. Select setup.exe to install if Auto-Run doesn&#8217;t start.</p>
<p><script type="text/javascript"><!--
google_ad_client = "pub-8643272411983164";
google_ad_slot = "3007786398";
google_ad_width = 468;
google_ad_height = 60;
//--></script>
<script type="text/javascript" src="http://pagead2.googlesyndication.com/pagead/show_ads.js"></script>
</p>
]]></content:encoded>
			<wfw:commentRss>http://www.vdi.co.nz/2010/05/15/error-1316-a-network-error-occured-while-atempting-to-read-the-file/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Unable to connect to the MKS: Failed to connect to server XXXXXX:902</title>
		<link>http://www.vdi.co.nz/2009/08/02/unable-to-connect-to-the-mks/</link>
		<comments>http://www.vdi.co.nz/2009/08/02/unable-to-connect-to-the-mks/#comments</comments>
		<pubDate>Sun, 02 Aug 2009 08:05:12 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[ESX]]></category>
		<category><![CDATA[ESX 4]]></category>
		<category><![CDATA[vsphere]]></category>

		<guid isPermaLink="false">http://www.vdi.co.nz/?p=203</guid>
		<description><![CDATA[I came across the above error under vSphere &#8211; ESX 4.0 running under workstation. To fix it, add the following line to the /etc/vmware/config file in the VMware ESX Service Console: &#8221; vmauthd.server.alwaysProxy=TRUE &#8220;]]></description>
			<content:encoded><![CDATA[<p>I came across the above error under vSphere &#8211; ESX 4.0 running under workstation.<br />
To fix it, add the following line to the /etc/vmware/config file in the VMware ESX Service Console:</p>
<p>&#8221; vmauthd.server.alwaysProxy=TRUE &#8220;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.vdi.co.nz/2009/08/02/unable-to-connect-to-the-mks/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<item>
		<title>VDI Storage Considerations</title>
		<link>http://www.vdi.co.nz/2008/10/12/vdi-storage-considerations/</link>
		<comments>http://www.vdi.co.nz/2008/10/12/vdi-storage-considerations/#comments</comments>
		<pubDate>Sun, 12 Oct 2008 10:27:31 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[ESX]]></category>
		<category><![CDATA[Storage]]></category>
		<category><![CDATA[VDI]]></category>
		<category><![CDATA[VMware]]></category>
		<category><![CDATA[Howto]]></category>

		<guid isPermaLink="false">http://www.vdi.co.nz/?p=133</guid>
		<description><![CDATA[VMware released a new PDF called “VMware VDI Storage Considerations“ it focuses on design choices for the storage environment that forms the foundation of a production VMware VDI implementation. Check it out…]]></description>
			<content:encoded><![CDATA[<p>VMware released a new PDF called “<a title="VDI Storage Considerations" href="http://www.vmware.com/files/pdf/vdi-storage-considerations-v4.pdf" target="_blank">VMware VDI Storage Considerations</a>“ it focuses on design choices for the storage environment that forms the foundation of a production VMware VDI implementation. Check it out…<br />
<script type="text/javascript"><!--
google_ad_client = "pub-8643272411983164";
google_ad_slot = "3007786398";
google_ad_width = 468;
google_ad_height = 60;
//--></script>
<script type="text/javascript" src="http://pagead2.googlesyndication.com/pagead/show_ads.js"></script>
</p>
]]></content:encoded>
			<wfw:commentRss>http://www.vdi.co.nz/2008/10/12/vdi-storage-considerations/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>VMware ESX and ESXi Comparison</title>
		<link>http://www.vdi.co.nz/2008/09/05/vmware-esx-and-esxi-comparison/</link>
		<comments>http://www.vdi.co.nz/2008/09/05/vmware-esx-and-esxi-comparison/#comments</comments>
		<pubDate>Fri, 05 Sep 2008 09:31:22 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[ESX]]></category>
		<category><![CDATA[ESXi]]></category>
		<category><![CDATA[ESX and ESXi Comparison]]></category>

		<guid isPermaLink="false">http://www.vdi.co.nz/?p=70</guid>
		<description><![CDATA[What&#8217;s the difference between ESX and ESXi.  Check out this link here. The article provides detailed comparison between VMware ESX and ESXi]]></description>
			<content:encoded><![CDATA[<p>What&#8217;s the difference between ESX and ESXi.  Check out this link <a href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1006543" target="_blank">here</a>. The article provides detailed comparison between VMware ESX and ESXi</p>
]]></content:encoded>
			<wfw:commentRss>http://www.vdi.co.nz/2008/09/05/vmware-esx-and-esxi-comparison/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

