<?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>ITExperience.NET &#187; VMWare</title>
	<atom:link href="http://www.itexperience.net/category/vmware/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.itexperience.net</link>
	<description>where IT meets experience</description>
	<lastBuildDate>Thu, 02 Feb 2012 21:03:13 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>VMWare ESX4 WebAccess: 503 Service Unavailable</title>
		<link>http://www.itexperience.net/vmware-esx4-webaccess-503-service-unavailable/</link>
		<comments>http://www.itexperience.net/vmware-esx4-webaccess-503-service-unavailable/#comments</comments>
		<pubDate>Tue, 25 Oct 2011 12:27:31 +0000</pubDate>
		<dc:creator>Christian</dc:creator>
				<category><![CDATA[VMWare]]></category>
		<category><![CDATA[vsphere]]></category>
		<category><![CDATA[webaccess]]></category>

		<guid isPermaLink="false">http://www.itexperience.net/vmware-esx4-webaccess-503-service-unavailable/</guid>
		<description><![CDATA[By default, the Web Access service of VMWare ESX4 does not automatically start. The easiest way to check whether the web access is functioning correctly is by typing in the IP address, or DNS name of the ESX server in your browser. Click “Log in to Web Access” and verify you get the following window: [...]]]></description>
		<wfw:commentRss>http://www.itexperience.net/vmware-esx4-webaccess-503-service-unavailable/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>vSphere 4.1: Number of virtual devices exceeds the maximum for a given controller.</title>
		<link>http://www.itexperience.net/vsphere-4-1-number-of-virtual-devices-exceeds-the-maximum-for-a-given-controller/</link>
		<comments>http://www.itexperience.net/vsphere-4-1-number-of-virtual-devices-exceeds-the-maximum-for-a-given-controller/#comments</comments>
		<pubDate>Wed, 13 Oct 2010 11:15:57 +0000</pubDate>
		<dc:creator>Christian</dc:creator>
				<category><![CDATA[VMWare]]></category>
		<category><![CDATA[clone]]></category>
		<category><![CDATA[vsphere]]></category>

		<guid isPermaLink="false">http://www.itexperience.net/2010/10/13/vsphere-4-1-number-of-virtual-devices-exceeds-the-maximum-for-a-given-controller/</guid>
		<description><![CDATA[While cloning a Virtual Machine, the following error may occur when the cloning process is at 90%: Clone virtual machine %computername% Number of virtual devices exceeds the maximum for a given controller. Reconfiguring the new Virtual Machine When this is the case, you probably have selected the “Edit Virtual hardware (Experimental)” checkbox during the Cloning [...]]]></description>
		<wfw:commentRss>http://www.itexperience.net/vsphere-4-1-number-of-virtual-devices-exceeds-the-maximum-for-a-given-controller/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>vSphere Virtual Center service starts and then stops again</title>
		<link>http://www.itexperience.net/vsphere-virtual-center-service-starts-and-then-stops-again/</link>
		<comments>http://www.itexperience.net/vsphere-virtual-center-service-starts-and-then-stops-again/#comments</comments>
		<pubDate>Fri, 03 Sep 2010 15:01:28 +0000</pubDate>
		<dc:creator>Christian</dc:creator>
				<category><![CDATA[VMWare]]></category>
		<category><![CDATA[sql 2005 express]]></category>
		<category><![CDATA[vcenter]]></category>
		<category><![CDATA[vsphere]]></category>

		<guid isPermaLink="false">http://www.itexperience.net/2010/09/03/vsphere-virtual-center-service-starts-and-then-stops-again/</guid>
		<description><![CDATA[Recently I upgraded vSphere 4.0 to 4.1. Therefore, I first backed up the vCenter data, configured a new Windows Server 2008 R2 server, and then used install.bat to install vCenter 4.1 with all the data from the old server. After only a couple of hours, I could not connect to my Virtual Center server anymore. [...]]]></description>
		<wfw:commentRss>http://www.itexperience.net/vsphere-virtual-center-service-starts-and-then-stops-again/feed/</wfw:commentRss>
		<slash:comments>11</slash:comments>
		</item>
		<item>
		<title>&quot;Backing up vCenter Orchestrator configuration failed&quot; during upgrade to vSphere vCenter 4.1</title>
		<link>http://www.itexperience.net/backing-up-vcenter-orchestrator-configuration-failed-during-upgrade-to-vsphere-vcenter-4-1/</link>
		<comments>http://www.itexperience.net/backing-up-vcenter-orchestrator-configuration-failed-during-upgrade-to-vsphere-vcenter-4-1/#comments</comments>
		<pubDate>Thu, 02 Sep 2010 12:43:46 +0000</pubDate>
		<dc:creator>Christian</dc:creator>
				<category><![CDATA[VMWare]]></category>
		<category><![CDATA[vcenter]]></category>
		<category><![CDATA[vsphere]]></category>

		<guid isPermaLink="false">http://www.itexperience.net/2010/09/02/backing-up-vcenter-orchestrator-configuration-failed-during-upgrade-to-vsphere-vcenter-4-1/</guid>
		<description><![CDATA[Today I prepared the upgrade from vSphere vCenter 4.0 to 4.1. One of the steps that must be completed is running Backup.bat. At the end of backup.bat, I got the following error: &#34;Backing up vCenter Orchestrator configuration failed&#34; First I verified that all VMWare related services were stopped. This was the case. Google didn’t show [...]]]></description>
		<wfw:commentRss>http://www.itexperience.net/backing-up-vcenter-orchestrator-configuration-failed-during-upgrade-to-vsphere-vcenter-4-1/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Automatically upgrade VMWare Tools on multiple Virtual Machines</title>
		<link>http://www.itexperience.net/automatically-upgrade-vmware-tools-on-multiple-virtual-machines/</link>
		<comments>http://www.itexperience.net/automatically-upgrade-vmware-tools-on-multiple-virtual-machines/#comments</comments>
		<pubDate>Thu, 27 Aug 2009 14:58:46 +0000</pubDate>
		<dc:creator>Christian</dc:creator>
				<category><![CDATA[PowerShell]]></category>
		<category><![CDATA[VMWare]]></category>
		<category><![CDATA[vmware tools]]></category>
		<category><![CDATA[vsphere]]></category>

		<guid isPermaLink="false">http://www.itexperience.net/?p=401</guid>
		<description><![CDATA[A new version of ESX often comes with a new version of VMWare Tools. In my case, I did a migration of ESX 3.5 to vSphere (4.0). A manual installation of VMWare Tools would be pretty time-wasting (50 virtual machines). Therefore, I&#8217;ve searched on Google, and found the following solution: Powershell! With a Powershell command, [...]]]></description>
		<wfw:commentRss>http://www.itexperience.net/automatically-upgrade-vmware-tools-on-multiple-virtual-machines/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Howto: Expand your C:\ drive in VMWARE ESX 3.5</title>
		<link>http://www.itexperience.net/howto-expand-your-c-drive-in-vmware-esx-35/</link>
		<comments>http://www.itexperience.net/howto-expand-your-c-drive-in-vmware-esx-35/#comments</comments>
		<pubDate>Tue, 24 Feb 2009 20:05:56 +0000</pubDate>
		<dc:creator>Christian</dc:creator>
				<category><![CDATA[VMWare]]></category>
		<category><![CDATA[vmware esx]]></category>

		<guid isPermaLink="false">http://www.itexperience.net/?p=298</guid>
		<description><![CDATA[Just as I did some days ago, you may face the problem that you&#8217;re running out of diskpace on your C:\ drive (system drive)  in VMWARE. Expanding the system drive is not as easy as expanding a non-system drive (like D:\, E:\ or whatever partitions you may have in your server :) ) These steps [...]]]></description>
		<wfw:commentRss>http://www.itexperience.net/howto-expand-your-c-drive-in-vmware-esx-35/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<item>
		<title>&#8220;Remove Snapshot: Operation Timed Out.&#8221; in VMWare ESX 3.5</title>
		<link>http://www.itexperience.net/remove-snapshot-operation-timed-out-in-vmware-esx-35/</link>
		<comments>http://www.itexperience.net/remove-snapshot-operation-timed-out-in-vmware-esx-35/#comments</comments>
		<pubDate>Tue, 24 Feb 2009 19:21:35 +0000</pubDate>
		<dc:creator>Christian</dc:creator>
				<category><![CDATA[VMWare]]></category>
		<category><![CDATA[vmware esx]]></category>

		<guid isPermaLink="false">http://www.itexperience.net/?p=296</guid>
		<description><![CDATA[When you (try to) delete a snapshot from a virtual machine in VMWare ESX 3.5, the following error may occur: &#8220;Remove Snapshot: Operation Timed Out.&#8221; This error typically occurs after 15 minutes, and only when your &#8220;delta&#8221;-file is large. I.e. when you&#8217;re making many changes on the server, or when you&#8217;re running on the snapshot [...]]]></description>
		<wfw:commentRss>http://www.itexperience.net/remove-snapshot-operation-timed-out-in-vmware-esx-35/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Determine VMWARE ESX version</title>
		<link>http://www.itexperience.net/determine-vmware-esx-version/</link>
		<comments>http://www.itexperience.net/determine-vmware-esx-version/#comments</comments>
		<pubDate>Mon, 01 Dec 2008 13:01:14 +0000</pubDate>
		<dc:creator>Christian</dc:creator>
				<category><![CDATA[VMWare]]></category>
		<category><![CDATA[vmware esx]]></category>

		<guid isPermaLink="false">http://www.itexperience.net/?p=216</guid>
		<description><![CDATA[If you&#8217;re trying to find and view the VMWARE ESX version, the easiest way is to export a Report Summary. From your Infrastructure Client: Choose the Inventory View Right click your host, and click Report Summary Choose a location to save the file Open the file with your internet browser. The version number of your [...]]]></description>
		<wfw:commentRss>http://www.itexperience.net/determine-vmware-esx-version/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Disable system beeps in VMWare Workstation</title>
		<link>http://www.itexperience.net/disable-system-beeps-in-vmware-workstation/</link>
		<comments>http://www.itexperience.net/disable-system-beeps-in-vmware-workstation/#comments</comments>
		<pubDate>Tue, 18 Mar 2008 20:09:00 +0000</pubDate>
		<dc:creator>Christian</dc:creator>
				<category><![CDATA[VMWare]]></category>

		<guid isPermaLink="false">http://www.itexperience.net/2008/03/18/disable-system-beeps-in-vmware-workstation/</guid>
		<description><![CDATA[After installing Windows Server 2008 (Longhorn) on a Virtual Machine, a system beep kept annoying me. The beep occurred with every system event. There are two possibilities: turn it off for one session, or turn it off for good. To turn it off for only one session, do the following: Click Start Click Run In [...]]]></description>
		<wfw:commentRss>http://www.itexperience.net/disable-system-beeps-in-vmware-workstation/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>SYSTEM process takes high CPU on server in VMWARE</title>
		<link>http://www.itexperience.net/system-process-takes-high-cpu-on-server-in-vmware/</link>
		<comments>http://www.itexperience.net/system-process-takes-high-cpu-on-server-in-vmware/#comments</comments>
		<pubDate>Tue, 18 Mar 2008 07:21:39 +0000</pubDate>
		<dc:creator>Christian</dc:creator>
				<category><![CDATA[VMWare]]></category>

		<guid isPermaLink="false">http://www.itexperience.net/2008/03/18/system-process-takes-high-cpu-on-server-in-vmware/</guid>
		<description><![CDATA[After upgrading to VMWARE 3.5 and VirtualCenter 2.5, the SYSTEM proces on our File server had an high CPU load (100%). This especially occurred when we were copying files from the file server. Killing the SYSTEM proces did not result in a lower CPU load. The problem had the following characteristics: After a migration of [...]]]></description>
		<wfw:commentRss>http://www.itexperience.net/system-process-takes-high-cpu-on-server-in-vmware/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

