<?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/tag/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 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>
	</channel>
</rss>

