<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>VMware Communities : All Content - All Communities</title>
    <link>http://communities.vmware.com/index.jspa</link>
    <description>All Content in VMware Communities</description>
    <language>en</language>
    <pubDate>Sun, 01 Nov 2009 21:29:26 GMT</pubDate>
    <generator>Clearspace 1.10.12 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2009-11-01T21:29:26Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>Hitachi AMS 2300</title>
      <link>http://communities.vmware.com/message/1405564</link>
      <description>&lt;br /&gt;
We purchased new units recently and all the firmware was up to date. The only downtime was licence installation (there are 3 licences which require reboots when installed).&lt;br /&gt;
&lt;p /&gt;
We have a good relationship with the local service guys, emails are always quickly answered and onsite support is prompt. The Department I indirectly work for has a fair bit of HDS kit so there is an existing enterprise support agreement - can't comment on what the standard support would be like if, for example, a single AMS unit was the only infrastructure purchased from them.</description>
      <pubDate>Sun, 01 Nov 2009 21:29:26 GMT</pubDate>
      <author>bazza52</author>
      <guid>http://communities.vmware.com/message/1405564</guid>
      <dc:date>2009-11-01T21:29:26Z</dc:date>
      <clearspace:dateToText>3 weeks, 1 day ago</clearspace:dateToText>
      <clearspace:replyCount>8</clearspace:replyCount>
    </item>
    <item>
      <title>I give -- Advanced Options</title>
      <link>http://communities.vmware.com/message/1334855</link>
      <description>&lt;p /&gt;
&lt;p /&gt;
The Help button linked to the following information:&lt;br /&gt;
&lt;br /&gt;
(Optional)   For Microsoft Windows guest operating systems only, specify a location for the log file by entering values in the Advanced Options field.|Microsoft Windows Guest Operating Systems Advanced Values|Description|&lt;br /&gt;
&lt;table class="jive-wiki-table"&gt;
&lt;tr&gt;
&lt;td&gt;/s /v "/qn"&lt;/td&gt;
&lt;td&gt;Same as the default behavior. Performs a silent upgrade of VMware Tools.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;/s /v "/qn" /l "&amp;lt;Microsoft Windows_location\filename.log&amp;gt;"&lt;/td&gt;
&lt;td&gt;Performs a silent upgrade of VMware Tools and creates a log file in the specified location on the guest operating system.&lt;/td&gt;
&lt;/tr&gt;
&lt;/table&gt;
&lt;br clear="left" /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;
 The standard install switches for the setup.exe should be these:&lt;br /&gt;
&lt;p /&gt;
&lt;img src="http://communities.vmware.com/servlet/JiveServlet/downloadImage/6557/2009-08-11_00003.jpg" alt="http://communities.vmware.com/servlet/JiveServlet/downloadImage/6557/2009-08-11_00003.jpg" class="jive-image"  /&gt;&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;
I don't see in either location an option for a shutdown switch. Perhaps adding /shutdown as an option might work.</description>
      <pubDate>Tue, 11 Aug 2009 20:04:25 GMT</pubDate>
      <author>nkbaumer</author>
      <guid>http://communities.vmware.com/message/1334855</guid>
      <dc:date>2009-08-11T20:04:25Z</dc:date>
      <clearspace:dateToText>3 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Missing local SCSI VMFS partition</title>
      <link>http://communities.vmware.com/message/1246872</link>
      <description>Yes - there was nothing on there I needed.</description>
      <pubDate>Fri, 08 May 2009 12:42:33 GMT</pubDate>
      <author>jaygriffin</author>
      <guid>http://communities.vmware.com/message/1246872</guid>
      <dc:date>2009-05-08T12:42:33Z</dc:date>
      <clearspace:dateToText>6 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>9</clearspace:replyCount>
    </item>
    <item>
      <title>Checking logs for a VM that locked up</title>
      <link>http://communities.vmware.com/message/1213617</link>
      <description>If we find anything else we will follow up with you off line through our support group.&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;
www.phdvirtual.com, makers of esXpress</description>
      <pubDate>Tue, 31 Mar 2009 16:33:42 GMT</pubDate>
      <author>petedr</author>
      <guid>http://communities.vmware.com/message/1213617</guid>
      <dc:date>2009-03-31T16:33:42Z</dc:date>
      <clearspace:dateToText>7 months, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>10</clearspace:replyCount>
    </item>
    <item>
      <title>Linked Clones with Vista 64-bit</title>
      <link>http://communities.vmware.com/message/1212392</link>
      <description>&lt;br /&gt;
If there is anyone out there who has tried this, I am interested in hearing about your experience.  I have no problem getting the view Manager client to install on the 64-bit workstation.  I have installed it many times -- just turn off the USB support.&lt;br /&gt;
&lt;p /&gt;
I powered down the virtual workstation and I created a snapshot.&lt;br /&gt;
&lt;p /&gt;
When I go through the View Administrator wizard to add a linked-clone pool, the snapshot does not show up.   I did a 32-bit Windows XP workstation just to make sure I didn't have a problem unrelated to the 64-bit OS.  The Windows XP snapshot showed up fine.  But I can't see any Vista-64 snapshots.&lt;br /&gt;
&lt;p /&gt;
Is there anyone out there who has tried this?  Did you get it to work?</description>
      <pubDate>Mon, 30 Mar 2009 16:53:11 GMT</pubDate>
      <author>jaygriffin</author>
      <guid>http://communities.vmware.com/message/1212392</guid>
      <dc:date>2009-03-30T16:53:11Z</dc:date>
      <clearspace:dateToText>7 months, 4 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>7</clearspace:replyCount>
    </item>
    <item>
      <title>Problems install View Manager Agent</title>
      <link>http://communities.vmware.com/message/1211864</link>
      <description>&lt;br /&gt;
I hit upon a simple solution to the View Agent install error #28030.  Specifically, I used local admin account to launch the installer, which worked.  Windows XP SP2 - added to domain.&lt;br /&gt;
&lt;p /&gt;
This action resolved two issues I have been encountered when installing View Agent:&lt;br /&gt;
&lt;p /&gt;
1) ThinPrint Install Error:  "You do not have permission to modify the settings for this printer..."&lt;br /&gt;
&lt;p /&gt;
2) USB Hub and USB Device drivers:  "Error 28030. The Installer failed to install the USB driver."&lt;br /&gt;
&lt;p /&gt;
Frankly, I do not know specifically which policy is keeping me from installing the drivers when I log in as a domain user/administrator.  I strongly suspected  the &lt;b&gt;local&lt;/b&gt; policy "load and unload device driver" - particularly because this was disabled whenever I was logged in as a domain user.  This included Domain Admin user.&lt;br /&gt;
&lt;p /&gt;
Incidentally, I tried to push down these rights from within AD.  (Domain controller: Domain Security Policy | + Local Policies | User Rights Assignment | Load and Unload Device Drivers).  &lt;br /&gt;
&lt;p /&gt;
I then used GPUDPDATE.EXE /FORCE, and although the local policy changed, the install still failed for both print &amp;#38; USB.&lt;br /&gt;
&lt;p /&gt;
The agent services &amp;#38; devices seem healthy when I log in as a domain user.  So, I was able to move forward.  Incidentally, this only led me to my next challenge... when I add desktop to an individual pool, the machine is not fully accessible. It's likely that my problem is unrelated to the view agent install workaround.  I add this for completeness, only. &lt;br /&gt;
&lt;p /&gt;
 For enquiring minds, my situation is that the individual desktop is created in view manager, however, under desktop sources, status is "waiting for agent."  This happens with more than one guest OS. As I said, I think this is unrelated to USB Driver Installation difficulties.</description>
      <pubDate>Mon, 30 Mar 2009 07:40:52 GMT</pubDate>
      <author>kconnor</author>
      <guid>http://communities.vmware.com/message/1211864</guid>
      <dc:date>2009-03-30T07:40:52Z</dc:date>
      <clearspace:dateToText>7 months, 4 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>6</clearspace:replyCount>
    </item>
    <item>
      <title>Hercules Load Balancer</title>
      <link>http://communities.vmware.com/message/1158280</link>
      <description>This is kind of a crazy way, but it seems to have worked --- I used the converter to convert the files to a Virtual Appliance.  Then I used the Converter to import the virtual appliance.</description>
      <pubDate>Fri, 30 Jan 2009 19:11:31 GMT</pubDate>
      <author>jaygriffin</author>
      <guid>http://communities.vmware.com/message/1158280</guid>
      <dc:date>2009-01-30T19:11:31Z</dc:date>
      <clearspace:dateToText>9 months, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Stored Performance Data</title>
      <link>http://communities.vmware.com/message/1156706</link>
      <description>Anyone?</description>
      <pubDate>Thu, 29 Jan 2009 14:27:49 GMT</pubDate>
      <author>jaygriffin</author>
      <guid>http://communities.vmware.com/message/1156706</guid>
      <dc:date>2009-01-29T14:27:49Z</dc:date>
      <clearspace:dateToText>9 months, 4 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Upgrade documentation</title>
      <link>http://communities.vmware.com/message/1119859</link>
      <description>&lt;br /&gt;
Thanks, but what I am really looking for is the documentation for doing the upgrade.&lt;br /&gt;
&lt;p /&gt;
There appears to be a great deal of documentation and KB articles for this new product.    Where is the documentation if you are doing a regular upgrade?  (Upgrading a single VDM server)</description>
      <pubDate>Tue, 09 Dec 2008 21:59:24 GMT</pubDate>
      <author>jaygriffin</author>
      <guid>http://communities.vmware.com/message/1119859</guid>
      <dc:date>2008-12-09T21:59:24Z</dc:date>
      <clearspace:dateToText>11 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>ESX Networking Configuration for HP 1510i</title>
      <link>http://communities.vmware.com/message/1104483</link>
      <description>If you found this helpful, please use of the Helpful /Correct buttons to award points. Thanks !!</description>
      <pubDate>Thu, 20 Nov 2008 19:00:21 GMT</pubDate>
      <author>bebman</author>
      <guid>http://communities.vmware.com/message/1104483</guid>
      <dc:date>2008-11-20T19:00:21Z</dc:date>
      <clearspace:dateToText>1 year, 3 days ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Search Community not working</title>
      <link>http://communities.vmware.com/message/1007035</link>
      <description>This is likely related to the other intermittent issues on the site.  We are working with Jive and Akamai to resolve them as soon as possible.&lt;br /&gt;
&lt;br /&gt;
Regards, Robert&lt;br&gt;&lt;br&gt;Robert Dell'Immagine, Director of VMware Communities</description>
      <pubDate>Wed, 30 Jul 2008 17:12:54 GMT</pubDate>
      <author>RDellimmagine</author>
      <guid>http://communities.vmware.com/message/1007035</guid>
      <dc:date>2008-07-30T17:12:54Z</dc:date>
      <clearspace:dateToText>1 year, 3 months ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Consolidated Backup and Backup Exec Questions</title>
      <link>http://communities.vmware.com/message/1007005</link>
      <description>Ive been testing VCB for the last 3 months, very tricky.  browse-start command is away of mounting manually; in your backupExec after running this command will show what VM has been mounted, this is more like a testing ground. You can run a backup at file level for this.  The Pre-Backup is a script backup exec uses to mount a vm for backup, what i have notice is that it actually uses the browse start bat and other scripts to go forward with processing a backup.  I aslo had errors when mounting backups similar to yours.  I still had a snapshot or partial snapshot mounted and this returned the same error.  I ran vcbcleanup.bat to clean up the folder, then ran a backup and it worked correctly.</description>
      <pubDate>Wed, 30 Jul 2008 16:22:29 GMT</pubDate>
      <author>ederaco</author>
      <guid>http://communities.vmware.com/message/1007005</guid>
      <dc:date>2008-07-30T16:22:29Z</dc:date>
      <clearspace:dateToText>1 year, 3 months ago</clearspace:dateToText>
      <clearspace:replyCount>8</clearspace:replyCount>
    </item>
    <item>
      <title>Are the March Patches working for you?</title>
      <link>http://communities.vmware.com/message/885883</link>
      <description>After I updated BESX4, I vmotioned a couple of VMs to it and it seems to be fine.    Not sure why the first server had a problem, but something definitely was not right.</description>
      <pubDate>Thu, 13 Mar 2008 16:52:48 GMT</pubDate>
      <author>jaygriffin</author>
      <guid>http://communities.vmware.com/message/885883</guid>
      <dc:date>2008-03-13T16:52:48Z</dc:date>
      <clearspace:dateToText>1 year, 8 months ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>Vmware workstation connect to VirtualCenter 2.5</title>
      <link>http://communities.vmware.com/message/869987</link>
      <description>&lt;br /&gt;
Thanks Kevin -- I guess that's the problem then.&lt;br /&gt;
&lt;p /&gt;
I found another solution.  From Virtual Center, I did an EXPORT and put the files on my PC's C: drive.  I specified in the export that it was a VMware workstation.  After the export completed, I simply "open"ed the vm from VMware workstation.  Seems to be working fine.&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <pubDate>Sat, 23 Feb 2008 04:01:55 GMT</pubDate>
      <author>jaygriffin</author>
      <guid>http://communities.vmware.com/message/869987</guid>
      <dc:date>2008-02-23T04:01:55Z</dc:date>
      <clearspace:dateToText>1 year, 9 months ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
    <item>
      <title>Hosts not responding after VPN downtime</title>
      <link>http://communities.vmware.com/message/861013</link>
      <description>Did you just remove them from the cluster on friday or did you have to do anything else? Hope they stay.</description>
      <pubDate>Mon, 11 Feb 2008 15:43:00 GMT</pubDate>
      <author>Chamon</author>
      <guid>http://communities.vmware.com/message/861013</guid>
      <dc:date>2008-02-11T15:43:00Z</dc:date>
      <clearspace:dateToText>1 year, 9 months ago</clearspace:dateToText>
      <clearspace:replyCount>11</clearspace:replyCount>
    </item>
    <item>
      <title>iSCSI clearing up failed logins</title>
      <link>http://communities.vmware.com/message/847796</link>
      <description>Man, you'd think with as many problems as this MSA is causing people, they (HP) might consider not selling it... but nah, that'd impact the sales numbers.  Wouldn't want to do what's best for the customers, now would we?&lt;br /&gt;
&lt;br /&gt;
Jay, I'm sorry to tell you that shutting everything down is the only way you're going to be able to clear this out.  And, unfortunately,  you're going to need to get use to the idea of taking everything offline every month or so while the MSA does what it does.  We've got a 1500 we've almost completely migrated off of - once we do, we're going to bash its little SCSI controllers in &lt;img class="jive-emoticon" border="0" src="http://communities.vmware.com/images/emoticons/happy.gif" alt=":)" /&gt;&lt;br /&gt;
&lt;br /&gt;
HP has not been helpful to us, either.  Even getting regional reps involved has proved a waste of time, despite their assurances they'd "fix" the problems.  So we spoke with our money, and aren't buying HP anymore.&lt;br /&gt;
&lt;br /&gt;
The only bit of helpful advice I can give you is a sequence we do on our 1500 to fix locking problems... but I don't know if it'll work for your situation, as we're on FC not iSCSI with the 1500.&lt;br /&gt;
&lt;br /&gt;
1) Fail working controller in ACU.&lt;br /&gt;
2) Pull 'failed' controller.&lt;br /&gt;
3) Wait a bit.&lt;br /&gt;
4) Put controller back in.&lt;br /&gt;
5) Wait a bit.&lt;br /&gt;
&lt;br /&gt;
See if things clear up.  If not, repeat 1 -&amp;gt; 5.  If it still doesn't work, after step 5, pull the other controller and follow the same steps with it.&lt;br /&gt;
&lt;br /&gt;
Eventually, we'll get the unit online without taking our VM's offline, but some VMs will die due to timeouts.&lt;br /&gt;
&lt;br /&gt;
&lt;br&gt;&lt;br&gt;----&lt;br /&gt;
Carter Manucy</description>
      <pubDate>Fri, 25 Jan 2008 01:03:47 GMT</pubDate>
      <author>cmanucy</author>
      <guid>http://communities.vmware.com/message/847796</guid>
      <dc:date>2008-01-25T01:03:47Z</dc:date>
      <clearspace:dateToText>1 year, 10 months ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Searching specific communities</title>
      <link>http://communities.vmware.com/message/843254</link>
      <description>Weird, my earlier response from my Blackberry never made it through.  Here is what I wanted to say, Jay:&lt;br /&gt;
&lt;p /&gt;
It is a problem that the advanced search is not a link from the standard screen. We have this on our list of UI bugs. (Which Robert has since mentioned in his post.)&lt;br /&gt;
&lt;p /&gt;
You do have another simple option, if you don't know the link oreeh sent you, but it is not intuitive or obvious:&lt;br /&gt;
&lt;p /&gt;
(1) Go to the community/ sub-community you wish to search and perform a simple search.  By default, the search engine will search that particular community only.&lt;br /&gt;
&lt;p /&gt;
(2) You will also notice that in addition to getting the preliminary results, you will be presented with the advanced options that include search within a specific community. When you look closely at the initial settings, you will see the current community selected.&lt;br /&gt;
&lt;p /&gt;
Thanks.&lt;br /&gt;
&lt;p /&gt;
Badsah.  &lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;i&gt;"VMW - The Ultimate Virtual Machine"&lt;/i&gt;&lt;br /&gt;
VMVMVMVMVMVMVMVMVMVMVMVMVMVMVMVMVMVMVMVMVMVMVMVMVMVMVMVMVMVMVMVMVM&lt;br /&gt;
Badsah Mukherji | Senior Community Manager | VMware Communities | &lt;a class="jive-link-external" href="http://www.vmware.com/"&gt;http://www.vmware.com/&lt;/a&gt;&lt;br /&gt;
VMVMVMVMVMVMVMVMVMVMVMVMVMVMVMVMVMVMVMVMVMVMVMVMVMVMVMVMVMVMVMVMVM</description>
      <pubDate>Fri, 18 Jan 2008 19:00:11 GMT</pubDate>
      <author>Badsah</author>
      <guid>http://communities.vmware.com/message/843254</guid>
      <dc:date>2008-01-18T19:00:11Z</dc:date>
      <clearspace:dateToText>1 year, 10 months ago</clearspace:dateToText>
      <clearspace:replyCount>5</clearspace:replyCount>
    </item>
    <item>
      <title>VM won't power up after 3.5 upgrade (or very, very slow)</title>
      <link>http://communities.vmware.com/message/824312</link>
      <description>&lt;br /&gt;
I get some great information from these forums, so I thought I would share this in case anyone else encounters the same problem.  After upgrading to VC 2.5 and ESX 3.5 I had some VM's that would not power up or woudl take forever to powerup.  Even after powering up they were non-functional -- could not even RDP into them.  They all exhibited the same behavior -- when powered on they would go to 95% and hang.&lt;br /&gt;
&lt;p /&gt;
 Problem:  The vmx file had a sched.max.cpu = "0" in it.  They weren't getting any CPU time!  Not sure how this like got there.&lt;br /&gt;
&lt;p /&gt;
 This find statement revealed all the VM's that had the problem:&lt;br /&gt;
&lt;p /&gt;
find /vmfs/volumes/ -name "*.vmx" -exec grep -Hi cpu.max {} \;&lt;br /&gt;
&lt;p /&gt;
Solution:&lt;br /&gt;
&lt;br /&gt;
&lt;ol&gt;
&lt;li&gt;Power off the VM's -- some wouldn't and I had to reboot the ESX server.&lt;/li&gt;
&lt;li&gt;Disconnect and Remove the ESX server from VC.&lt;/li&gt;
&lt;li&gt;Edit the vmx file and delete the sched.max.cpu line.&lt;/li&gt;
&lt;li&gt;Power on the vm from the command line: vmware-cmd /vmfs/volumes/8c72f5a5-da11b5c4-8699-8dd93c53fdb3/isweb4/isweb4.vmx start&lt;/li&gt;
&lt;li&gt;Make sure the VM is working properly.&lt;/li&gt;
&lt;li&gt;Add the ESX host back to VC.&lt;/li&gt;
&lt;/ol&gt;
&lt;br /&gt;
If you don't remove the ESX server from VC, the vmx keeps getting updated from the database and the sched.max.cpu line gets re-added.&lt;br /&gt;
&lt;p /&gt;
I am not sure how this line got in there.  But I had about 6 VM's that were all created at the same time that had this problem.  They all ran fine before the upgrade.&lt;br /&gt;
&lt;p /&gt;
Anyway, just wanted to post this in case it might help someone down the road.</description>
      <pubDate>Thu, 20 Dec 2007 19:02:20 GMT</pubDate>
      <author>jaygriffin</author>
      <guid>http://communities.vmware.com/message/824312</guid>
      <dc:date>2007-12-20T19:02:20Z</dc:date>
      <clearspace:dateToText>1 year, 11 months ago</clearspace:dateToText>
    </item>
    <item>
      <title>Replacing a VMware server -- not enough licenses</title>
      <link>http://communities.vmware.com/message/818084</link>
      <description>register for an evalulation, this will give you a 16 processor license, replace your current License with the 16 processor lic file and relicense your environement, do your vmotions and then switch off the old server, then revert to your original license key and you should be good to go.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
"Bravery is being the only one who knows you're afraid." - David Hackworth &lt;br /&gt;
&lt;br /&gt;
Kind Regards&lt;br /&gt;
&lt;br /&gt;
Tom,</description>
      <pubDate>Wed, 12 Dec 2007 22:31:33 GMT</pubDate>
      <author>tom howarth</author>
      <guid>http://communities.vmware.com/message/818084</guid>
      <dc:date>2007-12-12T22:31:33Z</dc:date>
      <clearspace:dateToText>1 year, 11 months ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>esXpress vs. 3.5 Backup / Restore Features</title>
      <link>http://communities.vmware.com/message/787479</link>
      <description>&lt;br /&gt;
Hey beckhamk,&lt;br /&gt;
&lt;p /&gt;
   I work for esxpress and it can do both. We can backup over the LAN to network targets (ftp/ssh/smb) and can also backup LAN Free to your SAN to vmfs partitions on it. &lt;br /&gt;
&lt;p /&gt;
pete@esxpress &lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <pubDate>Mon, 05 Nov 2007 22:39:01 GMT</pubDate>
      <author>petedr</author>
      <guid>http://communities.vmware.com/message/787479</guid>
      <dc:date>2007-11-05T22:39:01Z</dc:date>
      <clearspace:dateToText>2 years, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>3.0.2 Update 1</title>
      <link>http://communities.vmware.com/message/783883</link>
      <description>Duh! Downloaded the wrong file -- I d/l the from ESX2 file.</description>
      <pubDate>Wed, 31 Oct 2007 21:59:24 GMT</pubDate>
      <author>jaygriffin</author>
      <guid>http://communities.vmware.com/message/783883</guid>
      <dc:date>2007-10-31T21:59:24Z</dc:date>
      <clearspace:dateToText>2 years, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Notification of new patches</title>
      <link>http://communities.vmware.com/message/668776</link>
      <description>You can also go to the below link and manage your subscriptions, I received an email like below last week...&lt;br /&gt;
&lt;p /&gt;
****************************************************************************************&lt;br /&gt;
&lt;br /&gt;
Subject: ESX Server 2.0.2 / 2.1.3 / 2.5.3 / 2.5.4 / 3.0.0 / 3.0.1 - New Patch Available&lt;br /&gt;
&lt;br /&gt;
****************************************************************************************&lt;br /&gt;
&lt;br /&gt;
This communication is regarding the newly available patches for ESX Server 2.0.2, ESX Server 2.1.3, ESX Server 2.5.3, ESX Server 2.5.4, ESX Server 3.0.0 and ESX Server 3.0.1.&lt;br /&gt;
&lt;br /&gt;
To manage your VMware subscription, please visit VMware Subscriptions. &lt;br /&gt;
&lt;a class="jive-link-external" href="http://info.vmware.com/content/Subscription"&gt;http://info.vmware.com/content/Subscription&lt;/a&gt;</description>
      <pubDate>Tue, 12 Jun 2007 22:25:03 GMT</pubDate>
      <author>esiebert7625</author>
      <guid>http://communities.vmware.com/message/668776</guid>
      <dc:date>2007-06-12T22:25:03Z</dc:date>
      <clearspace:dateToText>2 years, 5 months ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>HA - power on / off settings</title>
      <link>http://communities.vmware.com/message/647055</link>
      <description>Autostart gets disabled when the host is part of a HA cluster. per host startup order does not make sense in a cluster setting where VMs move around between hosts. &lt;br /&gt;
&lt;br /&gt;
Your problem is likely that you lost both networks to your service console, thereby leaving the host isolated from the network, and its isolation response kicked in. The default behavior is to power down the VM, so that it can be restarted on another host by non-isolated hosts. &lt;br /&gt;
&lt;br /&gt;
HA requires redundant networking, so that if one path goes down, it at least has the other path for heartbeating and other communications.</description>
      <pubDate>Thu, 17 May 2007 01:45:50 GMT</pubDate>
      <author>sridharr</author>
      <guid>http://communities.vmware.com/message/647055</guid>
      <dc:date>2007-05-17T01:45:50Z</dc:date>
      <clearspace:dateToText>2 years, 6 months ago</clearspace:dateToText>
      <clearspace:replyCount>8</clearspace:replyCount>
    </item>
    <item>
      <title>Failed to obtain write lock</title>
      <link>http://communities.vmware.com/message/611560</link>
      <description>Did not find any read only files.&lt;br /&gt;
&lt;br /&gt;
I removed the VM's from my favorites and re-created using an existing file.  That seemed to work.  I can power them on now.&lt;br /&gt;
&lt;br /&gt;
Thanks for the reponses.</description>
      <pubDate>Fri, 30 Mar 2007 13:07:36 GMT</pubDate>
      <author>jaygriffin</author>
      <guid>http://communities.vmware.com/message/611560</guid>
      <dc:date>2007-03-30T13:07:36Z</dc:date>
      <clearspace:dateToText>2 years, 7 months ago</clearspace:dateToText>
      <clearspace:replyCount>6</clearspace:replyCount>
    </item>
    <item>
      <title>Windows Clustering -- what's the value in ESX?</title>
      <link>http://communities.vmware.com/message/598563</link>
      <description>IMHO clustering only makes sense if you need 24x7&lt;br /&gt;
&lt;br /&gt;
If you already have HA I don't see any benefit to MSCS but only drawbacks (additional management overhead using the cluster management stuff, cluster unaware apps which cause trouble,...)&lt;br /&gt;
&lt;br /&gt;
And yes you can use snapshots for "quick and dirty backups"&lt;br /&gt;
&lt;br /&gt;
Just my 0.02</description>
      <pubDate>Wed, 14 Mar 2007 20:11:00 GMT</pubDate>
      <author>oreeh</author>
      <guid>http://communities.vmware.com/message/598563</guid>
      <dc:date>2007-03-14T20:11:00Z</dc:date>
      <clearspace:dateToText>2 years, 8 months ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Unable to migrate ... device not accessible</title>
      <link>http://communities.vmware.com/message/597519</link>
      <description>That is expected behavior.&lt;br /&gt;
&lt;br /&gt;
When trying to Vmotion, there are several checks that take place.  One is to verify that the datastores are available on the host you are sending the VM to.  Every disk on a VM has a datastore associated with it, including floppy drives, cd-rom's, and hard disks.  If the datastore is not available on the target, the vmotion will not proceed.  By disconnecting the cd-rom that datastore is no longer required to be available on the target host.&lt;br /&gt;
&lt;br /&gt;
You can setup a shared datastore using NFS to help avoid this issue, but it is a best practice to disconnect your CD-ROM's when done using them.</description>
      <pubDate>Tue, 13 Mar 2007 20:15:39 GMT</pubDate>
      <author>impensb</author>
      <guid>http://communities.vmware.com/message/597519</guid>
      <dc:date>2007-03-13T20:15:39Z</dc:date>
      <clearspace:dateToText>2 years, 8 months ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Errors loading Win 2003 from ISO file</title>
      <link>http://communities.vmware.com/message/586295</link>
      <description>Problem with the ISO file.  Copied over a new one and it is working.</description>
      <pubDate>Tue, 27 Feb 2007 21:10:39 GMT</pubDate>
      <author>jaygriffin</author>
      <guid>http://communities.vmware.com/message/586295</guid>
      <dc:date>2007-02-27T21:10:39Z</dc:date>
      <clearspace:dateToText>2 years, 9 months ago</clearspace:dateToText>
      <clearspace:replyCount>5</clearspace:replyCount>
    </item>
    <item>
      <title>HA Agent Disabled on besx1.company.com in cluster Corp Cluster in Main DC</title>
      <link>http://communities.vmware.com/message/577404</link>
      <description>Thx.. Glad its sorted..!</description>
      <pubDate>Thu, 15 Feb 2007 22:21:31 GMT</pubDate>
      <author>acr</author>
      <guid>http://communities.vmware.com/message/577404</guid>
      <dc:date>2007-02-15T22:21:31Z</dc:date>
      <clearspace:dateToText>2 years, 9 months ago</clearspace:dateToText>
      <clearspace:replyCount>7</clearspace:replyCount>
    </item>
    <item>
      <title>New VM - blank console</title>
      <link>http://communities.vmware.com/message/467047</link>
      <description>I'm having the same problem.  New Esx server and user.  I created the VM, used the dd command on the root to upload the ISO but when I power on the VM, the console has always been blank.  There has been nothing on the window to try to get to the boot sequence.&lt;br /&gt;
I am curious what you meant by deleting and recreating the virtual disk. Is this the VM or the datacenter?&lt;br /&gt;
&lt;br /&gt;
Message was edited by: &lt;br /&gt;
        trdavis55</description>
      <pubDate>Thu, 31 Aug 2006 13:07:31 GMT</pubDate>
      <author>trdavis55</author>
      <guid>http://communities.vmware.com/message/467047</guid>
      <dc:date>2006-08-31T13:07:31Z</dc:date>
      <clearspace:dateToText>3 years, 2 months ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>NLB - leaving the Cluster</title>
      <link>http://communities.vmware.com/message/465405</link>
      <description>I am attempting to use NLB on VMware server - my VM's are Windows 2003 Std SP1.  VMware was so kind to include a section on this in their manual.  That was helpful -- I have used NLB in the past, but I would not have know I needed to use multicast mode instead of unicast.&lt;br /&gt;
&lt;br /&gt;
Anyway - I have VMware server running on a server called isweb2.  The VM on isweb2 is isweb4.  I wanted to test VMware server before putting other servers up so I NLB'ed isweb4 (the VM) with a physical server isweb1.  I used to have isweb1 and isweb2 NLB'ed, but I removed isweb2 and added isweb4.&lt;br /&gt;
&lt;br /&gt;
I have two NIC's in isweb1 and two in isweb2 - one used for NLB and the other for external traffic.  On the VM setup on isweb2 I setup two separate bridges - one for each NIC.  I use the NICs in the same manner on isweb4 -- the isweb2 external is the isweb4 external; the one that used to be for NLB on isweb2 is used for NLB on isweb4.&lt;br /&gt;
&lt;br /&gt;
Today a program I use to monitor the servers told me it could not ping isweb4.  I found this in the system event:&lt;br /&gt;
&lt;br /&gt;
(from isweb1)&lt;br /&gt;
Event Type:	Information&lt;br /&gt;
Event Source:	WLBS&lt;br /&gt;
Event Category:	None&lt;br /&gt;
Event ID:	69&lt;br /&gt;
Date:		8/25/2006&lt;br /&gt;
Time:		5:39:22 AM&lt;br /&gt;
User:		N/A&lt;br /&gt;
Computer:	ISWEB1&lt;br /&gt;
Description:&lt;br /&gt;
NLB Cluster 10.3.1.97 : Initiating convergence on host 1.  Reason: Host 2 is leaving the cluster.&lt;br /&gt;
&lt;br /&gt;
----  from Isweb4 -----&lt;br /&gt;
&lt;br /&gt;
Event Type:	Information&lt;br /&gt;
Event Source:	WLBS&lt;br /&gt;
Event Category:	None&lt;br /&gt;
Event ID:	65&lt;br /&gt;
Date:		8/25/2006&lt;br /&gt;
Time:		5:39:18 AM&lt;br /&gt;
User:		N/A&lt;br /&gt;
Computer:	ISWEB4&lt;br /&gt;
Description:&lt;br /&gt;
NLB Cluster 10.3.1.97 : Initiating convergence on host 2.  Reason: Host 1 is converging for an unknown reason.&lt;br /&gt;
&lt;br /&gt;
Not sure what to look for -- are there different NIC drivers that can be used?  Any other settings I should check?</description>
      <pubDate>Mon, 28 Aug 2006 21:32:27 GMT</pubDate>
      <author>jaygriffin</author>
      <guid>http://communities.vmware.com/message/465405</guid>
      <dc:date>2006-08-28T21:32:27Z</dc:date>
      <clearspace:dateToText>3 years, 2 months ago</clearspace:dateToText>
    </item>
    <item>
      <title>Virtual Center 2 Eval</title>
      <link>http://communities.vmware.com/message/464153</link>
      <description>In VI3 they do come with the agents but I'm pretty sure the agent licenses are part of VC and would go in the vmware.lic file and not on the host. I could be wrong on that though since we haven't done host based licensing on VI3.</description>
      <pubDate>Fri, 25 Aug 2006 13:10:56 GMT</pubDate>
      <author>mstahl75</author>
      <guid>http://communities.vmware.com/message/464153</guid>
      <dc:date>2006-08-25T13:10:56Z</dc:date>
      <clearspace:dateToText>3 years, 3 months ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>Network Load Balancing on VMware server</title>
      <link>http://communities.vmware.com/message/464069</link>
      <description>I am attempting to use NLB on VMware server.  VMware was so kind to include a section on this in their manual.  That was helpful -- I have used NLB in the past, but I would not have know I needed to use multicast mode instead of unicast.&lt;br /&gt;
&lt;br /&gt;
Anyway - I have VMware server running on a server called isweb2.  The VM on isweb2 is isweb4.  I wanted to test VMware server before putting other servers up so I NLB'ed isweb4 (the VM) with a physical server isweb1.  I used to have isweb1 and isweb2 NLB'ed, but I removed isweb2 and added isweb4.&lt;br /&gt;
&lt;br /&gt;
I have two NIC's in isweb1 and two in isweb2 - one used for NLB and the other for external traffic.  On the VM setup on isweb2 I setup two separate bridges - one for each NIC.  I use the NICs in the same manner on isweb4 -- the isweb2 external is the isweb4 external; the one that used to be for NLB on isweb2 is used for NLB on isweb4.&lt;br /&gt;
&lt;br /&gt;
Today a program I use to monitor the servers told me it could not ping isweb4.  I found this in the system event:&lt;br /&gt;
&lt;br /&gt;
(from isweb1)&lt;br /&gt;
Event Type:	Information&lt;br /&gt;
Event Source:	WLBS&lt;br /&gt;
Event Category:	None&lt;br /&gt;
Event ID:	69&lt;br /&gt;
Date:		8/25/2006&lt;br /&gt;
Time:		5:39:22 AM&lt;br /&gt;
User:		N/A&lt;br /&gt;
Computer:	ISWEB1&lt;br /&gt;
Description:&lt;br /&gt;
NLB Cluster 10.3.1.97 : Initiating convergence on host 1.  Reason: Host 2 is leaving the cluster.&lt;br /&gt;
&lt;br /&gt;
----  from Isweb4 -----&lt;br /&gt;
&lt;br /&gt;
Event Type:	Information&lt;br /&gt;
Event Source:	WLBS&lt;br /&gt;
Event Category:	None&lt;br /&gt;
Event ID:	65&lt;br /&gt;
Date:		8/25/2006&lt;br /&gt;
Time:		5:39:18 AM&lt;br /&gt;
User:		N/A&lt;br /&gt;
Computer:	ISWEB4&lt;br /&gt;
Description:&lt;br /&gt;
NLB Cluster 10.3.1.97 : Initiating convergence on host 2.  Reason: Host 1 is converging for an unknown reason.&lt;br /&gt;
&lt;br /&gt;
Not sure what to look for -- are there different NIC drivers that can be used?  Any other settings I should check?</description>
      <pubDate>Fri, 25 Aug 2006 10:12:03 GMT</pubDate>
      <author>jaygriffin</author>
      <guid>http://communities.vmware.com/message/464069</guid>
      <dc:date>2006-08-25T10:12:03Z</dc:date>
      <clearspace:dateToText>3 years, 3 months ago</clearspace:dateToText>
    </item>
    <item>
      <title>Why would VMware shutdown my vm?</title>
      <link>http://communities.vmware.com/message/430620</link>
      <description>now you tell me...</description>
      <pubDate>Thu, 06 Jul 2006 05:04:55 GMT</pubDate>
      <author>Rumple</author>
      <guid>http://communities.vmware.com/message/430620</guid>
      <dc:date>2006-07-06T05:04:55Z</dc:date>
      <clearspace:dateToText>3 years, 4 months ago</clearspace:dateToText>
      <clearspace:replyCount>5</clearspace:replyCount>
    </item>
    <item>
      <title>VM Crash</title>
      <link>http://communities.vmware.com/message/399065</link>
      <description>Run vm-support - open an SR with VMware and upload the output from the script.&lt;br /&gt;
&lt;br /&gt;
DB</description>
      <pubDate>Fri, 12 May 2006 14:19:38 GMT</pubDate>
      <author>boydd</author>
      <guid>http://communities.vmware.com/message/399065</guid>
      <dc:date>2006-05-12T14:19:38Z</dc:date>
      <clearspace:dateToText>3 years, 6 months ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Shared memory killing app?</title>
      <link>http://communities.vmware.com/message/396978</link>
      <description>I would check to see if there is any swapping occuring while you reboot.  That would have the most noticiable impact on performance.  &lt;br /&gt;
&lt;br /&gt;
It sounds like you are over committng your RAM, but the page sharing is able to free up enough memory so that is not a problem most of the time.  However, when you reboot a server it has to "touch" all of its RAM and it takes a while for it share all of the pages again.  &lt;br /&gt;
&lt;br /&gt;
So my initial thought is that by rebooting the virtual machine you causing ESX to need to swap memory.  Log into the MUI and look click on the the memory tab and see how much swapping is occuring.</description>
      <pubDate>Tue, 09 May 2006 16:31:34 GMT</pubDate>
      <author>dsanders</author>
      <guid>http://communities.vmware.com/message/396978</guid>
      <dc:date>2006-05-09T16:31:34Z</dc:date>
      <clearspace:dateToText>3 years, 6 months ago</clearspace:dateToText>
      <clearspace:replyCount>10</clearspace:replyCount>
    </item>
    <item>
      <title>virtual server NIC running at 10 mbps</title>
      <link>http://communities.vmware.com/message/394532</link>
      <description>Just got a call from VMware support.  He pointed out that the VMX driver is a more high performance driver.</description>
      <pubDate>Thu, 04 May 2006 14:50:33 GMT</pubDate>
      <author>jaygriffin</author>
      <guid>http://communities.vmware.com/message/394532</guid>
      <dc:date>2006-05-04T14:50:33Z</dc:date>
      <clearspace:dateToText>3 years, 6 months ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
  </channel>
</rss>

