<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>nixman Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>nixman Tracker</description>
    <pubDate>Wed, 15 Nov 2023 12:46:48 GMT</pubDate>
    <dc:date>2023-11-15T12:46:48Z</dc:date>
    <item>
      <title>Re: Where can I download vCenter Converter?</title>
      <link>https://communities.vmware.com/t5/Converter-Standalone-Discussions/Where-can-I-download-vCenter-Converter/m-p/2948563#M44161</link>
      <description>&lt;P&gt;Looks like&amp;nbsp;VMware vCenter Converter has been re-released as v6.3.0 on the portal. If you search for the converter, you should find the download to it back in it's place.&lt;/P&gt;</description>
      <pubDate>Fri, 13 Jan 2023 15:11:35 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Converter-Standalone-Discussions/Where-can-I-download-vCenter-Converter/m-p/2948563#M44161</guid>
      <dc:creator>nixman</dc:creator>
      <dc:date>2023-01-13T15:11:35Z</dc:date>
    </item>
    <item>
      <title>Re: VMWare Converter: (A file I/O error occurred while accesssing ". )</title>
      <link>https://communities.vmware.com/t5/Converter-Standalone-Discussions/VMWare-Converter-A-file-I-O-error-occurred-while-accesssing-quot/m-p/977524#M14442</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I got the same error message. We use static IP's on our server equipment and the VMware Converter correctly identified the FQDN for my source.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Where I used it the vCenter destination for the VMware Converter was located in a different DMZ than the source I was running the VMware Converter from. I had previously allowed TCP/443 on my firewall for traffic to the vCenter from the source, but also had to allow TCP/902 from the source I was running VMware Converter on to access the cluster (management) IP's of my VMware hardware.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It looks like the VMware Converter establishes the connection to the vCenter (as the destination "manager" for the clone to be created), but then allows the VMware Converter source to directly "talk to" the cluster (on one of it's IP's) to stream the virtual to the storage for creation.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 24 Dec 2016 18:33:13 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Converter-Standalone-Discussions/VMWare-Converter-A-file-I-O-error-occurred-while-accesssing-quot/m-p/977524#M14442</guid>
      <dc:creator>nixman</dc:creator>
      <dc:date>2016-12-24T18:33:13Z</dc:date>
    </item>
    <item>
      <title>Re: problem virtualizing older Windows systems</title>
      <link>https://communities.vmware.com/t5/Virtual-Machine-Guest-OS-and-VM/problem-virtualizing-older-Windows-systems/m-p/107245#M153</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What about PC Tool v4.21... I had Xtree Pro and later Xtree Gold just about on all my workstations and even on my UNIX i386 and SunOS servers... &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My first "proof of concept" for VMWare was by creating a MS-DOS 6.22 virtual installation, loading a TCP/IP stack - think it was Novell's - and surfing the company intranet on Lynx... After that Win98 and the rest followed.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 Aug 2007 15:08:57 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Virtual-Machine-Guest-OS-and-VM/problem-virtualizing-older-Windows-systems/m-p/107245#M153</guid>
      <dc:creator>nixman</dc:creator>
      <dc:date>2007-08-23T15:08:57Z</dc:date>
    </item>
  </channel>
</rss>

