<?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>AndreParsons Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>AndreParsons Tracker</description>
    <pubDate>Wed, 15 Nov 2023 13:49:08 GMT</pubDate>
    <dc:date>2023-11-15T13:49:08Z</dc:date>
    <item>
      <title>Re: a general system error occurred: failed to register VRMS</title>
      <link>https://communities.vmware.com/t5/vSphere-Replication-Discussions/a-general-system-error-occurred-failed-to-register-VRMS/m-p/2974965#M3703</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;In case anyone is still having this issue, try the following:&lt;/P&gt;&lt;P&gt;In my case, I was connected via VPN to the environment and although I could access both the VC and VR using FQDNs, I kept having the issue mentioned in this thread, so I eventually logged into a server inside the VMware environment and retried re-configuring the appliance and this time it went through without any issues. I suspect it was something to do with the proxy server.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 28 Jun 2023 18:01:37 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Replication-Discussions/a-general-system-error-occurred-failed-to-register-VRMS/m-p/2974965#M3703</guid>
      <dc:creator>AndreParsons</dc:creator>
      <dc:date>2023-06-28T18:01:37Z</dc:date>
    </item>
    <item>
      <title>Re: VMware upgrade 6.5 to 6.7 issue</title>
      <link>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Re-VMware-upgrade-6-5-to-6-7-issue/m-p/1842365#M21448</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just an update. I noticed that if I use the HTML5 client, I don't see this "HD audio" device under "Edit setting". I only see it when using the "flex" client. It doesn't appear on all VMs, just a few. Why would the Flex client show different hardware settings?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 Oct 2019 09:27:54 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Re-VMware-upgrade-6-5-to-6-7-issue/m-p/1842365#M21448</guid>
      <dc:creator>AndreParsons</dc:creator>
      <dc:date>2019-10-31T09:27:54Z</dc:date>
    </item>
    <item>
      <title>Re: VMware upgrade 6.5 to 6.7 issue</title>
      <link>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Re-VMware-upgrade-6-5-to-6-7-issue/m-p/1842364#M21447</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I haven't done extensive searches but could not find anything about the issue I encountered during an upgrade from VMware 6.5 to 6.7.&lt;/P&gt;&lt;P&gt;The vCenter and hosts were upgraded to 6.7U2. I then upgraded the vCenter to 6.7U3 and was trying to upgrade the hosts when I hit an issue where the hosts would not enter maintenance mode. I did some digging and found out that all my VMs suddenly have this "HD audio" device attached to them which was not there before the upgrade from 6.7U2 to 6.7U3. None of these VMs were P to V'd so I don't expect to see this device.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Has anyone encountered this before? I need to get to the bottom of this as I have other sites to upgrade and I don't want to have this happen again. Any thoughts will be appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I now have to shutdown approx 300 VMs and remove the device from each one so that I can continue the upgrade.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 29 Oct 2019 19:26:06 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Re-VMware-upgrade-6-5-to-6-7-issue/m-p/1842364#M21447</guid>
      <dc:creator>AndreParsons</dc:creator>
      <dc:date>2019-10-29T19:26:06Z</dc:date>
    </item>
  </channel>
</rss>

