<?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>Tue, 17 Nov 2009 04:00:12 GMT</pubDate>
    <generator>Clearspace 1.10.12 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2009-11-17T04:00:12Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>VCDX Defense, what's it like?</title>
      <link>http://communities.vmware.com/message/1418731</link>
      <description>As long as the whole of your design is comprehensive and can help someone get from a pile of servers, storage and network gear to a functional VMware architecture then you should be fine.&lt;br /&gt;
&lt;br /&gt;
If a customer wants you to place a specific piece of information into a document that you feel its out of place then it shouldn't cast you in a negative light (at least in my opinion.) The end goal is to make sure you are capable of making architecture decisions and can confidently act as a VMware expert.</description>
      <pubDate>Tue, 17 Nov 2009 04:00:12 GMT</pubDate>
      <author>RussellCorey</author>
      <guid>http://communities.vmware.com/message/1418731</guid>
      <dc:date>2009-11-17T04:00:12Z</dc:date>
      <clearspace:dateToText>6 days, 1 hour ago</clearspace:dateToText>
      <clearspace:replyCount>19</clearspace:replyCount>
    </item>
    <item>
      <title>How to check which NIC takes over when Primary nic fails?</title>
      <link>http://communities.vmware.com/message/1414625</link>
      <description>Simliar Question to this one.  We are also Setting up as much redundancy as we can.  V3.5 u4 and we have 10 NIC's.  Want to have mutiple physical adapters for each Vswitch but we are also connected to 2 core physical cisco switches.  Want to have standby for the 2nd physical switch incase we have a hardware failure of the actual switch.&lt;br /&gt;
&lt;br /&gt;
Anyway that anyone is aware of to configure the nic's in standy mode or any other way to allow 4 NIC's to be in the vswitch with the 2 active NIC's connected to the active core switch and 2 in standby mode pointing to the 2nd Physcial switch ?&lt;br /&gt;
&lt;br /&gt;
Any suggestions would be appreciated</description>
      <pubDate>Wed, 11 Nov 2009 18:27:56 GMT</pubDate>
      <author>kenconrad2009</author>
      <guid>http://communities.vmware.com/message/1414625</guid>
      <dc:date>2009-11-11T18:27:56Z</dc:date>
      <clearspace:dateToText>1 week, 4 days ago</clearspace:dateToText>
      <clearspace:replyCount>10</clearspace:replyCount>
    </item>
    <item>
      <title>Thinapp and AVG Anti-Virus, false positive!</title>
      <link>http://communities.vmware.com/message/1281815</link>
      <description>&lt;br /&gt;
Hi,&lt;br /&gt;
&lt;p /&gt;
Does anyone have an update on this issue ? we requested a trendmicro support case with our local vendor, but till now we don't have any feedback. Maybe someone else had more success ?&lt;br /&gt;
&lt;p /&gt;
what would be a good pattern file version to rollback to ? i guess this rollback would impact all TM officescan clients, or can the rollback be applied to a certain number of clients ?&lt;br /&gt;
&lt;p /&gt;
thx</description>
      <pubDate>Fri, 12 Jun 2009 08:53:32 GMT</pubDate>
      <author>KoenVerheyden</author>
      <guid>http://communities.vmware.com/message/1281815</guid>
      <dc:date>2009-06-12T08:53:32Z</dc:date>
      <clearspace:dateToText>5 months, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>6</clearspace:replyCount>
    </item>
    <item>
      <title>Clone and roll out template fail with "failed to connect to host"</title>
      <link>http://communities.vmware.com/message/1236672</link>
      <description>&lt;br /&gt;
Rather than loose all you performance data this article:&lt;br /&gt;
&lt;br /&gt;
*&lt;br /&gt;
&lt;a class="jive-link-external" href="http://www.yellow-bricks.com/2008/01/24/clone-and-roll-out-template-fail-with-failed-to-connect-to-host/"&gt;http://www.yellow-bricks.com/2008/01/24/clone-and-roll-out-template-fail-with-failed-to-connect-to-host/&lt;/a&gt;&lt;br /&gt;
&lt;p /&gt;
 This sql should update:&lt;br /&gt;
&lt;p /&gt;
UPDATE &lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=VCDB"&gt;VCDB&lt;/a&gt;.&lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=dbo"&gt;dbo&lt;/a&gt;.&lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=VPX_HOST"&gt;VPX_HOST&lt;/a&gt;*&lt;br /&gt;
&lt;b&gt;SET &lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=IP_ADDRESS"&gt;IP_ADDRESS&lt;/a&gt; = &amp;lsquo;w.x.y.z'&lt;/b&gt;&lt;br /&gt;
*WHERE &lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=DNS_NAME"&gt;DNS_NAME&lt;/a&gt; = &amp;lsquo;name of esx host as it is listed in the table'&lt;br /&gt;
&lt;br /&gt;
*</description>
      <pubDate>Mon, 27 Apr 2009 12:55:47 GMT</pubDate>
      <author>smudge1977</author>
      <guid>http://communities.vmware.com/message/1236672</guid>
      <dc:date>2009-04-27T12:55:47Z</dc:date>
      <clearspace:dateToText>6 months, 4 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>14</clearspace:replyCount>
    </item>
    <item>
      <title>VirtualCenter Update 3 just been released!</title>
      <link>http://communities.vmware.com/message/1066789</link>
      <description>VirtualCenter Update 3 has just been &lt;a class="jive-link-external" href="http://www.vmware.com/support/vi3/doc/vi3_vc25u3_rel_notes.html"&gt;released&lt;/a&gt;. It contains fixes for the "incompatible network check" during HA configurations, the fact that you couldn't delete advanced options any more and the maintenance mode issues.&lt;br /&gt;
&lt;br /&gt;
&lt;br&gt;&lt;br&gt;Duncan&lt;br /&gt;
Blogging: &lt;a class="jive-link-external" href="http://www.yellow-bricks.com"&gt;http://www.yellow-bricks.com&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
If you find this information useful, please award points for "correct" or "helpful".</description>
      <pubDate>Sat, 04 Oct 2008 06:49:14 GMT</pubDate>
      <author>depping</author>
      <guid>http://communities.vmware.com/message/1066789</guid>
      <dc:date>2008-10-04T06:49:14Z</dc:date>
      <clearspace:dateToText>1 year, 1 month ago</clearspace:dateToText>
    </item>
    <item>
      <title>Default Isolation response changed in VC 2.5 U2 and ESX 3.5</title>
      <link>http://communities.vmware.com/message/1005997</link>
      <description>I'm also curious what people think the best option would be? I tend to go for "shutdown vm".&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
Duncan&lt;br /&gt;
My virtualisation blog:&lt;br /&gt;
&lt;a class="jive-link-external" href="http://www.yellow-bricks.com"&gt;http://www.yellow-bricks.com&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
If you find this information useful, please award points for "correct" or "helpful".</description>
      <category domain="http://communities.vmware.com/tags?communityID=1">ha</category>
      <category domain="http://communities.vmware.com/tags?communityID=1">update_2</category>
      <category domain="http://communities.vmware.com/tags?communityID=1">3.5</category>
      <pubDate>Tue, 29 Jul 2008 20:21:52 GMT</pubDate>
      <author>depping</author>
      <guid>http://communities.vmware.com/message/1005997</guid>
      <dc:date>2008-07-29T20:21:52Z</dc:date>
      <clearspace:dateToText>1 year, 3 months ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
    <item>
      <title>VMware ESX: Deleting snapshots</title>
      <link>http://communities.vmware.com/message/737056</link>
      <description>1) When deleting multiple level snapshots it would be handy to have an option to delete a snapshot when they are committed instead of merging all snapshots into eachother and deleting them when all is inserted into the main disk. this would save a lot of disk space and make snapshot removal / troubleshooting a lot easier.&lt;br /&gt;
&lt;br /&gt;
2) A revert and stop snapshot mode option would be handy, instead of continuing the snapshot mode when you revert.</description>
      <pubDate>Wed, 29 Aug 2007 20:51:25 GMT</pubDate>
      <author>depping</author>
      <guid>http://communities.vmware.com/message/737056</guid>
      <dc:date>2007-08-29T20:51:25Z</dc:date>
      <clearspace:dateToText>2 years, 2 months ago</clearspace:dateToText>
    </item>
    <item>
      <title>Connection error - could not read from connection</title>
      <link>http://communities.vmware.com/message/613561</link>
      <description>We've upgraded to version 2 and the problem is also gone. Thanks for the effort everyone.&lt;br /&gt;
&lt;br /&gt;
I've tested the root update cert just to be sure and it seems to also fix this problem. great work!</description>
      <pubDate>Tue, 03 Apr 2007 07:50:57 GMT</pubDate>
      <author>depping</author>
      <guid>http://communities.vmware.com/message/613561</guid>
      <dc:date>2007-04-03T07:50:57Z</dc:date>
      <clearspace:dateToText>2 years, 7 months ago</clearspace:dateToText>
      <clearspace:replyCount>10</clearspace:replyCount>
    </item>
  </channel>
</rss>

