<?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>GBartsch Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>GBartsch Tracker</description>
    <pubDate>Wed, 15 Nov 2023 14:05:21 GMT</pubDate>
    <dc:date>2023-11-15T14:05:21Z</dc:date>
    <item>
      <title>OVF Import Fails Workstation, icuuc44.dll error</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/OVF-Import-Fails-Workstation-icuuc44-dll-error/m-p/1859482#M110544</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;When attempting to use Workstation 15.5.6 on Windows 10, 2003, OS Build 19041.329, I receive a failure in Workstation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After acknowledging the error, which tells me to look at the ovftool.log, I see this error:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"The code execution cannot proceed because icuuc44.dll was not found. Reinstalling the program may fix this problem."&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The DLL is missing, and installing the 4.4 version of the OVFTOOL has not solved the problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anyone know how to fix this?&amp;nbsp; Moreover, how to fix it without going to one of the MANY shady websites saying you can download that DLL from&amp;nbsp; us....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The OVFTOOL.LOG is not present in the location of the Workstation error.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Jun 2020 11:55:09 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/OVF-Import-Fails-Workstation-icuuc44-dll-error/m-p/1859482#M110544</guid>
      <dc:creator>GBartsch</dc:creator>
      <dc:date>2020-06-22T11:55:09Z</dc:date>
    </item>
    <item>
      <title>Re: Error, certificate failed to replace!</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Error-certificate-failed-to-replace/m-p/1861647#M59808</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Checked the logs... the errors don't tell you anything useful:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ERROR certificate-manager &amp;lt;date&amp;gt; &amp;lt;Time&amp;gt; Updating certificate for "com.vmware.vim.eam" extension&lt;/P&gt;&lt;P&gt;ERROR certificate-manager &amp;lt;date&amp;gt; &amp;lt;Time&amp;gt; Updating certificate for "com.vmware.rbd" extension&lt;/P&gt;&lt;P&gt;ERROR certificate-manager &amp;lt;date&amp;gt; &amp;lt;Time&amp;gt; Updating certificate for "com.vmware.imagebuilder" extension&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then there is:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ERROR certificate-manager {&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "translatable" : "An error occurred while invoking external command : '%(0)s'"&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "localized" : "An error occurred while invoking external command: 'None'"&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "Error while starting services, please see service-control log for more details"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm not certain where the service-control.log is, as it's not showing up in any of the KBBs for vCenter logs (6.x). Humph.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Mar 2020 12:50:48 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Error-certificate-failed-to-replace/m-p/1861647#M59808</guid>
      <dc:creator>GBartsch</dc:creator>
      <dc:date>2020-03-27T12:50:48Z</dc:date>
    </item>
    <item>
      <title>Re: VCSA 6.0 -&gt; 6.5 CLI Upgrade Fails at 58% with Vmware VirtualCenter failed firstboot.</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/VCSA-6-0-gt-6-5-CLI-Upgrade-Fails-at-58-with-Vmware/m-p/2223750#M73448</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Some Updates:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After upgradeing the vCenter 6.0 appliances to 6.5, we noticed that with 6.7 we saw some other issues:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The PSCs when going from 6.5 -&amp;gt; 6.7 also had some duplicate root certificates.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;At the end of the day, all appliances, vCenter or PSC, need to have any duplicate roots removed JUST prior to the upgrade.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It is critical that you do not restart any services. Simply SSH into the box just prior to upgrade (after you've shut down the entire vCenter appliance environment and take snapshots) and kill the duplicate certificates.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With the 6.5 upgrade installer, it doesn't notify you of any cert issues. The 6.7 upgrade installer is MUCH better, and will warn you of these issues.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Mar 2020 11:20:22 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/VCSA-6-0-gt-6-5-CLI-Upgrade-Fails-at-58-with-Vmware/m-p/2223750#M73448</guid>
      <dc:creator>GBartsch</dc:creator>
      <dc:date>2020-03-27T11:20:22Z</dc:date>
    </item>
    <item>
      <title>Error, certificate failed to replace!</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Error-certificate-failed-to-replace/m-p/1861644#M59805</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Anyone know why a 6.7 vCenter appliance would fail to accept new solution user certificates in both the UI and the CLI (Certificate-Manager)?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Specifics:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- 6.7U3C vCenter appliance in Enhanced-Linked mode&lt;/P&gt;&lt;P&gt;- Machine SSL certificate replaced without issue&lt;/P&gt;&lt;P&gt;- The VPXD, VPDX-extension, machine, and vsphere-webclient certificates will not replace&lt;/P&gt;&lt;P&gt;- &lt;STRONG&gt;There are no wild cards in the certificates [SANs or CNs, etc.]&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;- All of the vCenters in the environment have the same certificate templates and are the same, but they were upgraded to 6.7. This one is new.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The certificates were generated using open-ssl.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The template uses 4096, what should be the proper enhanced attributes, includes the corresponding type in the CN [e.g. machine-FQDN, VPXD-FQDN, etc.].&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is really odd.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;GB&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 25 Feb 2020 15:47:09 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Error-certificate-failed-to-replace/m-p/1861644#M59805</guid>
      <dc:creator>GBartsch</dc:creator>
      <dc:date>2020-02-25T15:47:09Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot type (using keyboard) on vSphere Web Client</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Cannot-type-using-keyboard-on-vSphere-Web-Client/m-p/1758469#M22559</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The easiest way to deal with this it to switch to another tab in the web browser, and then switch back.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It appears that tab switching fixes the issue 100% of the time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yeah, it's annoying. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Aug 2019 12:13:40 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Cannot-type-using-keyboard-on-vSphere-Web-Client/m-p/1758469#M22559</guid>
      <dc:creator>GBartsch</dc:creator>
      <dc:date>2019-08-26T12:13:40Z</dc:date>
    </item>
    <item>
      <title>Re: VCSA 6.0 -&gt; 6.5 CLI Upgrade Fails at 58% with Vmware VirtualCenter failed firstboot.</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/VCSA-6-0-gt-6-5-CLI-Upgrade-Fails-at-58-with-Vmware/m-p/2223749#M73447</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I was speaking with support the other day, and this issue is not commonly known.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'll see what I can do to reach back to engineering and have that fixed.&amp;nbsp; However, it's pretty rare thing...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 23 Aug 2019 16:33:44 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/VCSA-6-0-gt-6-5-CLI-Upgrade-Fails-at-58-with-Vmware/m-p/2223749#M73447</guid>
      <dc:creator>GBartsch</dc:creator>
      <dc:date>2019-08-23T16:33:44Z</dc:date>
    </item>
    <item>
      <title>Re: VCSA 6.0 -&gt; 6.5 CLI Upgrade Fails at 58% with Vmware VirtualCenter failed firstboot.</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/VCSA-6-0-gt-6-5-CLI-Upgrade-Fails-at-58-with-Vmware/m-p/2223748#M73446</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It turned out that the 6.0 vCenter server had some duplicate ROOT and INTERMEDIATE certificates in the TRUSTED ROOT STORE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Somehow some root CAs were not imported with the certificate thumbprint as the ALIAS for the certs; they were in fact the file name used for the certs when they were brought to the vCenter.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As such, there were two sets of the same certificates with different aliases.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This was causing the upgrade to explode when attempting to start the VPXD service. (...at 58%.)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PSC's did not appear to have the same issue; only the VPXD (virtual center server service) seemed to have this issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It is abolutely a bug that having two copies of the the same trusted root and intermediate certificates would cause a service to not start.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 03 Jul 2019 12:03:36 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/VCSA-6-0-gt-6-5-CLI-Upgrade-Fails-at-58-with-Vmware/m-p/2223748#M73446</guid>
      <dc:creator>GBartsch</dc:creator>
      <dc:date>2019-07-03T12:03:36Z</dc:date>
    </item>
    <item>
      <title>Re: VCSA 6.0 -&gt; 6.5 CLI Upgrade Fails at 58% with Vmware VirtualCenter failed firstboot.</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/VCSA-6-0-gt-6-5-CLI-Upgrade-Fails-at-58-with-Vmware/m-p/2223747#M73445</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So, not a total solution, but we downloaded the 6.5 U2G version and tried that this AM....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;....and guess what?&amp;nbsp; It got past 58%!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then it blew up on the VMware Authentication Services at 80%, which there is some sort of KB about that in 6.7.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 May 2019 15:03:21 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/VCSA-6-0-gt-6-5-CLI-Upgrade-Fails-at-58-with-Vmware/m-p/2223747#M73445</guid>
      <dc:creator>GBartsch</dc:creator>
      <dc:date>2019-05-23T15:03:21Z</dc:date>
    </item>
    <item>
      <title>Re: vCenter 6.0 -&gt; 6.5 Upgrade 'Failed normalizing ip" Messages</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-6-0-gt-6-5-Upgrade-Failed-normalizing-ip-quot-Messages/m-p/510820#M8381</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It's simply the standard CLI commands...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You prep your .JSON file for the type of upgrade destination, and then you enter the command-line parameters.&amp;nbsp; In this case, there is nothing unusual...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;vcsa-deploy upgrade --accept-eula --acknowledge-ceip --log-dir=&amp;lt;path&amp;gt; &amp;lt;JSON FIle with path&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Nothing interesting.&amp;nbsp; Thought I do typically add the verbose flag as well (--verbose)...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;During the process, you see the occasional 'failed normalizing ip: &amp;lt;FQDN&amp;gt; of the vCenter or PSC'&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I don't see it in any of our documentation, or posted anywhere else.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 May 2019 10:34:32 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-6-0-gt-6-5-Upgrade-Failed-normalizing-ip-quot-Messages/m-p/510820#M8381</guid>
      <dc:creator>GBartsch</dc:creator>
      <dc:date>2019-05-23T10:34:32Z</dc:date>
    </item>
    <item>
      <title>vCenter 6.0 -&gt; 6.5 Upgrade 'Failed normalizing ip" Messages</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-6-0-gt-6-5-Upgrade-Failed-normalizing-ip-quot-Messages/m-p/510818#M8379</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Does anyone know what the message &lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif;"&gt;&lt;STRONG&gt;Failed normalizing ip: &amp;lt;FQDN&amp;gt; &lt;/STRONG&gt;&lt;/SPAN&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif;"&gt;means when upgrading a vCenter server from 6.0 to 6.5?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif;"&gt;I'm using the 6.5 CLI upgrader, and I'm getting this "&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif;"&gt;Failed normalizing ip:" message, but with no any other useful diagnostic information.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 May 2019 14:53:07 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-6-0-gt-6-5-Upgrade-Failed-normalizing-ip-quot-Messages/m-p/510818#M8379</guid>
      <dc:creator>GBartsch</dc:creator>
      <dc:date>2019-05-22T14:53:07Z</dc:date>
    </item>
    <item>
      <title>Re: external PSC 6.0 upgrade to 6.5 fails - Internal error occurs during pre-upgrade checks</title>
      <link>https://communities.vmware.com/t5/vSphere-Upgrade-Install/external-PSC-6-0-upgrade-to-6-5-fails-Internal-error-occurs/m-p/1401925#M15613</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Do either of you have any idea as to what "&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif;"&gt;Failed normalizing ip: psc04.vlab.local" in the OPs CLI logs actually means?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 May 2019 13:33:54 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Upgrade-Install/external-PSC-6-0-upgrade-to-6-5-fails-Internal-error-occurs/m-p/1401925#M15613</guid>
      <dc:creator>GBartsch</dc:creator>
      <dc:date>2019-05-22T13:33:54Z</dc:date>
    </item>
    <item>
      <title>Re: VCSA 6.0 -&gt; 6.5 CLI Upgrade Fails at 58% with Vmware VirtualCenter failed firstboot.</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/VCSA-6-0-gt-6-5-CLI-Upgrade-Fails-at-58-with-Vmware/m-p/2223745#M73443</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We were able upgrade the PSCs (2 external PSCs) without issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have rebooted and tried this upgrade several times.&amp;nbsp; Same exact error every time...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Forward and Reverse DNS lookup zones are populated.&amp;nbsp; You can ping all of the appliances from each other. NSLOOKUPs working without issue.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 15 Feb 2019 12:07:59 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/VCSA-6-0-gt-6-5-CLI-Upgrade-Fails-at-58-with-Vmware/m-p/2223745#M73443</guid>
      <dc:creator>GBartsch</dc:creator>
      <dc:date>2019-02-15T12:07:59Z</dc:date>
    </item>
    <item>
      <title>VCSA 6.0 -&gt; 6.5 CLI Upgrade Fails at 58% with Vmware VirtualCenter failed firstboot.</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/VCSA-6-0-gt-6-5-CLI-Upgrade-Fails-at-58-with-Vmware/m-p/2223743#M73441</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We have a 6.0 vCenter Server Appliance with two external PSC [all 6.0.0.30800 build 9448190 / 6.0 Update 3h] we are attempting to upgrade to 6.5 U2e build 11347054.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We've been completely unsuccessful trying to use the GUI updater, as for some unknown reason the GUI upgrader will not connect to the vCenter/PSC during the initial connection in Stage 1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, with the CLI upgrader using a .JSON file, we've upgraded the PSCs (two external PSCs) without issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The vCenter Server Appliance, however, fails to upgrade with an error at 58%:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Progress: 58% Starting VMware vCenter Server...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Error:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Problem Id: install.vpxd.action.failed&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Component key: vpxd&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Detail:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Vmware VirtualCenter failed firstboot.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; An error occurred while invoking external command : 'Command: ['/usr/sbin/vpxd', '-L'] Strerr: '&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Resolution: Please search for these symptoms in the VMware Knowledge Base.....&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;...&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; vCSACliInstallLogger - DEBUG - Running command on vm [new vCenter name]: /bin/bash --login -c 'ls `install-parameter upgrade.import.directory` /system-data/revert_networking.py'&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; vCSACliInstallLogger - DEBUG - Running command on vm [new vCenter name]: /bin/bash --login -c '/opt/vmware/bin/python `install-parameter upgrade.import.directory` /system-data/revert_networking.py'&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; vCSACliInstallLogger - ERROR - Fail to revert the target vm IP address: Failed to run and wait for command in guest with error 'Command '[u'/opt/vmware/bin/python', u'`install-parameter upgrade.import.directory`/system-data/revert_networking.py']' exited with non-zero status 1'&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We were able to find a KB with the &lt;STRONG&gt;'Command: ['/usr/sbin/vpxd', '-L'] Strerr: '&lt;/STRONG&gt; issue listed, and it seems to refer to duplicate vDS and vDPG names.&amp;nbsp; However we were not able to find any dupes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(KB 2147547 for the vDS / vDPG issue: &lt;A href="https://kb.vmware.com/s/article/2147547" title="https://kb.vmware.com/s/article/2147547"&gt;VMware Knowledge Base&lt;/A&gt; and a related one showing how to connect to postgres &lt;A href="https://kb.vmware.com/s/article/2147285" title="https://kb.vmware.com/s/article/2147285"&gt;VMware Knowledge Base&lt;/A&gt; KB 2147285.)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is only one additional issue seen in the vcsa-installer.log.&amp;nbsp; We see a message "&lt;STRONG&gt;Failed normalizing ip: [FQDN of the vCenter being upgraded&lt;/STRONG&gt;"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does anyone have any ideas on this one?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Feb 2019 18:22:44 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/VCSA-6-0-gt-6-5-CLI-Upgrade-Fails-at-58-with-Vmware/m-p/2223743#M73441</guid>
      <dc:creator>GBartsch</dc:creator>
      <dc:date>2019-02-14T18:22:44Z</dc:date>
    </item>
    <item>
      <title>Re: Anyone run into an issue with you cannot add vCenters to vRSLCM 2.0?</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Suite-Lifecycle/Anyone-run-into-an-issue-with-you-cannot-add-vCenters-to-vRSLCM/m-p/2215343#M93</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The "+ Add vCenter Server" and the "+ Import" buttons are not appearing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thoughts?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Dec 2018 11:36:32 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Suite-Lifecycle/Anyone-run-into-an-issue-with-you-cannot-add-vCenters-to-vRSLCM/m-p/2215343#M93</guid>
      <dc:creator>GBartsch</dc:creator>
      <dc:date>2018-12-07T11:36:32Z</dc:date>
    </item>
    <item>
      <title>Anyone run into an issue with you cannot add vCenters to vRSLCM 2.0?</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Suite-Lifecycle/Anyone-run-into-an-issue-with-you-cannot-add-vCenters-to-vRSLCM/m-p/2215341#M91</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm configuring a vRSLCM 2.0 installation, and I'm noticing that I get options to attempt to add a Data Center, but not a vCenter.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I go to vCenter tab, there is no option to add a vCenter.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I know we need a vIDM for LCM to speak with AD, but LCM can speak directly with a vCenter? Correct?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anyone see this issue before?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Dec 2018 15:51:07 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Suite-Lifecycle/Anyone-run-into-an-issue-with-you-cannot-add-vCenters-to-vRSLCM/m-p/2215341#M91</guid>
      <dc:creator>GBartsch</dc:creator>
      <dc:date>2018-12-06T15:51:07Z</dc:date>
    </item>
    <item>
      <title>Re: How to Troubleshoot "Errors in Active Directory Operations" Messages</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/How-to-Troubleshoot-quot-Errors-in-Active-Directory-Operations/m-p/2223726#M216123</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Folks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regarding turning on SMB v1 on and Active Directory controller....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="text-decoration: underline;"&gt;&lt;EM&gt;&lt;STRONG&gt;This is a BAD idea.&lt;/STRONG&gt;&lt;/EM&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="text-decoration: underline;"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;It is also not something that we recommend.&amp;nbsp; The reason for it is as simple as EternalBlue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Malware is known to use SMBv1 and Microsoft has officially recommended that it be turned off.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you have an issue where you cannot join an ESXi host or vCenter to AD without SMBv1, please contact VMware GSS.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 24 Apr 2018 11:49:59 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/How-to-Troubleshoot-quot-Errors-in-Active-Directory-Operations/m-p/2223726#M216123</guid>
      <dc:creator>GBartsch</dc:creator>
      <dc:date>2018-04-24T11:49:59Z</dc:date>
    </item>
    <item>
      <title>Re: New Twist on "Unsuccessful - Test connection failed: The vSphere agent does not exist or may not be running." when registering an endpoint</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation-Tools/New-Twist-on-quot-Unsuccessful-Test-connection-failed-The/m-p/1415476#M10427</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="color: #303030;"&gt;Background:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #303030; font-family: Lato, 'Helvetica Neue', Helvetica, Verdana, Arial, sans-serif; font-size: 13.2192px; background-color: #fafafa;"&gt;Installed vRA 7.3 in HA using 2 appliances and 2 x each IaaS server type (web, dem-o, dem-w, ims, proxy agent), which were all configured using the wizard. On the "Agents" page during the vRA 7 Configuration Wizard run, there were 2 vCenter Endpoints added - for a total of FOUR proxy agents. ONE of the agents for a second vCenter had a typo in the Endpoint Name field. This has lead to the database having a reference in dbo.Agents for the Endpoint name being the typo/misspelled Agent Endpoint name. Subsequent attempts to uninstall the second vCenter agent for the two Agent Proxy Servers had been totally unsuccessful; the database entry for the Endpoint name is not corrected with an uninstall / reinstall of the Proxy Agents for the affected vCenter&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #303030; font-family: Lato, 'Helvetica Neue', Helvetica, Verdana, Arial, sans-serif; font-size: 13.2192px; background-color: #fafafa;"&gt;Solution (likely not supported by VMware - so open a support ticket and have GSS walk you through this):&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #303030; font-family: Lato, 'Helvetica Neue', Helvetica, Verdana, Arial, sans-serif; font-size: 13.2192px; background-color: #fafafa;"&gt;- Uninstall the Proxy Agents for the specific vCenter Endpoint that has an issue&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #303030; font-family: Lato, 'Helvetica Neue', Helvetica, Verdana, Arial, sans-serif; font-size: 13.2192px; background-color: #fafafa;"&gt;- SQL Management Studio, open the VRA database on your SQL server, and edit the first 200 rows of the dbo.Agents table&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #303030; font-family: Lato, 'Helvetica Neue', Helvetica, Verdana, Arial, sans-serif; font-size: 13.2192px; background-color: #fafafa;"&gt;- Find the row that has your mispelled Proxy Agent Endpoint listed (be VERY meticulous in reviewing that row for the Endpoint you are looking for)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #303030; font-family: Lato, 'Helvetica Neue', Helvetica, Verdana, Arial, sans-serif; font-size: 13.2192px; background-color: #fafafa;"&gt;- Delete the row that contains the misspelled Endpoint Name&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #303030; font-family: Lato, 'Helvetica Neue', Helvetica, Verdana, Arial, sans-serif; font-size: 13.2192px; background-color: #fafafa;"&gt;- Close the end table&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #303030; font-family: Lato, 'Helvetica Neue', Helvetica, Verdana, Arial, sans-serif; font-size: 13.2192px; background-color: #fafafa;"&gt;- Reinstall your Proxy Agents being very careful not to make any typos&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #303030; font-family: Lato, 'Helvetica Neue', Helvetica, Verdana, Arial, sans-serif; font-size: 13.2192px; background-color: #fafafa;"&gt;- Wait ~10 mintues&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #303030; font-family: Lato, 'Helvetica Neue', Helvetica, Verdana, Arial, sans-serif; font-size: 13.2192px; background-color: #fafafa;"&gt;- Check the ado.Agents table to see that your agents now appear in the table correctly&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #303030; font-family: Lato, 'Helvetica Neue', Helvetica, Verdana, Arial, sans-serif; font-size: 13.2192px; background-color: #fafafa;"&gt;- Logon to your vRA tenant, probably the Default Tenant&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #303030; font-family: Lato, 'Helvetica Neue', Helvetica, Verdana, Arial, sans-serif; font-size: 13.2192px; background-color: #fafafa;"&gt;- Add the Endpoint that was giving you the error previously&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Feb 2018 15:29:35 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation-Tools/New-Twist-on-quot-Unsuccessful-Test-connection-failed-The/m-p/1415476#M10427</guid>
      <dc:creator>GBartsch</dc:creator>
      <dc:date>2018-02-02T15:29:35Z</dc:date>
    </item>
    <item>
      <title>Re: New Twist on "Unsuccessful - Test connection failed: The vSphere agent does not exist or may not be running." when registering an endpoint</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation-Tools/New-Twist-on-quot-Unsuccessful-Test-connection-failed-The/m-p/1415475#M10426</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 10.5pt; font-family: Helvetica, sans-serif;"&gt;As an update, I've reached back to the mothership, and it appears that if these conditions exist:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.5pt; font-family: Helvetica, sans-serif;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.5pt; font-family: Helvetica, sans-serif;"&gt;1) You install vRA using the reference HA (high availability) design&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.5pt; font-family: Helvetica, sans-serif;"&gt;2) You run the vRA Configuration Wizard from the VAMI&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.5pt; font-family: Helvetica, sans-serif;"&gt;3) In the "Agents" screen you enter your EndPoint Names, but you misspell only &lt;EM&gt;ONE&lt;/EM&gt; of the &lt;SPAN style="text-decoration: underline;"&gt;TWO&lt;/SPAN&gt; Proxy Agents ENDPOINT NAMES; one endpoint name is correct and one is not&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.5pt; font-family: Helvetica, sans-serif;"&gt;4) When you check the VRA* SQL database table ado.Agents you see that the Proxy Agent in question shows the Endpoint Name as the &lt;EM&gt;misspelled&lt;/EM&gt; name&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.5pt; font-family: Helvetica, sans-serif;"&gt;5) When you attempt to add an Endpoint to vRA in the vRA console using the non-misspelled name you get "Test connection failed..."&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 10.5pt; font-family: Helvetica, sans-serif;"&gt;6) When you use the &lt;EM&gt;misspelled&lt;/EM&gt; Proxy Agent Endpoint Name the test connection works!&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 10.5pt; font-family: Helvetica, sans-serif;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 10.5pt; font-family: Helvetica, sans-serif;"&gt;…then you have a problem that uninstalling the Proxy Agents from both IaaS Agent servers does not appear to fix.&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 10.5pt; font-family: Helvetica, sans-serif;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 10.5pt; font-family: Helvetica, sans-serif;"&gt;I have not tried to edit the table on the database, &lt;EM style="text-decoration: underline;"&gt;as that would be a clearly unsupported by VMware&lt;/EM&gt;.&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 10.5pt; font-family: Helvetica, sans-serif;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 10.5pt; font-family: Helvetica, sans-serif;"&gt;However, there is an issue with borking the Endpoint Name for your Agents during the Configuration Wizard portion of the installation process. Specifically, when you only mess up one of the two HA proxy agents…&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Feb 2018 16:44:10 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation-Tools/New-Twist-on-quot-Unsuccessful-Test-connection-failed-The/m-p/1415475#M10426</guid>
      <dc:creator>GBartsch</dc:creator>
      <dc:date>2018-02-01T16:44:10Z</dc:date>
    </item>
    <item>
      <title>New Twist on "Unsuccessful - Test connection failed: The vSphere agent does not exist or may not be running." when registering an endpoint</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation-Tools/New-Twist-on-quot-Unsuccessful-Test-connection-failed-The/m-p/1415474#M10425</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="margin: 2px; font-family: proxima-nova, Arial, sans-serif; color: #666666;"&gt;Anyone every see this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin: 2px; font-family: proxima-nova, Arial, sans-serif; color: #666666;"&gt;We setup a HA vRA 7.3 installation.&amp;nbsp; So that means two vRA appliances, two Proxy Agents, two DEM workers, two DEM orchestrators, two IMS, two model manager webs, etc...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin: 2px; font-family: proxima-nova, Arial, sans-serif; color: #666666;"&gt;When the Proxy agent was configured in the vRA Configuration Wizard, one of two vCenter &lt;EM style="font-weight: inherit; font-size: inherit; font-family: inherit;"&gt;had a misspelled Endpoint Name&lt;/EM&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin: 2px; font-family: proxima-nova, Arial, sans-serif; color: #666666;"&gt;To lay it out:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin: 2px; font-family: proxima-nova, Arial, sans-serif; color: #666666;"&gt;Proxy Agent #1 on Windows Server #1&lt;/P&gt;&lt;P style="margin: 2px; font-family: proxima-nova, Arial, sans-serif; color: #666666;"&gt;vCenter:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; vcenter1.ad.local&lt;/P&gt;&lt;P style="margin: 2px; font-family: proxima-nova, Arial, sans-serif; color: #666666;"&gt;Endpoint Name:&amp;nbsp;&amp;nbsp; vcenter1.ad.local&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin: 2px; font-family: proxima-nova, Arial, sans-serif; color: #666666;"&gt;Proxy Agent #2 on Windows Server #2&lt;/P&gt;&lt;P style="margin: 2px; font-family: proxima-nova, Arial, sans-serif; color: #666666;"&gt;vCenter:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; vcenter1.ad.local&lt;/P&gt;&lt;P style="margin: 2px; font-family: proxima-nova, Arial, sans-serif; color: #666666;"&gt;Endpoint Name:&amp;nbsp;&amp;nbsp; &lt;STRONG style="font-style: inherit; font-size: inherit; font-family: inherit;"&gt;vcetner&lt;/STRONG&gt;1.ad.local&amp;nbsp; &amp;lt;----- TYPO! should have been "vcenter1.ad.local"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin: 2px; font-family: proxima-nova, Arial, sans-serif; color: #666666;"&gt;When you go to the vRA 7.3 default tenant -&amp;gt; Infrastructure -&amp;gt; Endpoints and attempt to add the vcenter1.ad.local Endpoint, you get:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin: 2px; font-family: proxima-nova, Arial, sans-serif; color: #666666;"&gt;"Unsuccessful - Test connection failed: The vSphere agent does not exist or may not be running."&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin: 2px; font-family: proxima-nova, Arial, sans-serif; color: #666666;"&gt;IF, on the other hand, you enter the typo for the Endpoint name ("&lt;EM style="font-weight: inherit; font-size: inherit; font-family: inherit;"&gt;vcetner1.ad.local"), &lt;/EM&gt;the test connection actually works!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin: 2px; font-family: proxima-nova, Arial, sans-serif; color: #666666;"&gt;&lt;SPAN style="font-weight: inherit; font-style: inherit; font-family: inherit; font-size: inherit !important;"&gt;&lt;EM style="font-weight: inherit; font-size: inherit; font-family: inherit;"&gt;Even after we uninstalled the Proxy Agent from BOTH servers and manually reinstalled them with the correct EndPoint names!!! &lt;/EM&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin: 2px; font-family: proxima-nova, Arial, sans-serif; color: #666666;"&gt;&lt;/P&gt;&lt;P style="margin: 2px; font-family: proxima-nova, Arial, sans-serif; color: #666666;"&gt;&lt;SPAN style="font-weight: inherit; font-style: inherit; font-family: inherit; font-size: inherit !important;"&gt;(So that means that uninstalling and reinstalling the Proxy Agents doesn't fix the issue...)&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Feb 2018 16:43:53 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation-Tools/New-Twist-on-quot-Unsuccessful-Test-connection-failed-The/m-p/1415474#M10425</guid>
      <dc:creator>GBartsch</dc:creator>
      <dc:date>2018-02-01T16:43:53Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot type (using keyboard) on vSphere Web Client</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Cannot-type-using-keyboard-on-vSphere-Web-Client/m-p/1758447#M22537</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yeah,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I don't see a current internal KB on this, but I can tell you all that using a 32bit browser seems to work in my case.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've been having issues where the screen will simply render black when we use 64bit browsers. Switch to IE 32bit, and it works fine.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'll dig around a big more.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 10 Dec 2017 12:04:56 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Cannot-type-using-keyboard-on-vSphere-Web-Client/m-p/1758447#M22537</guid>
      <dc:creator>GBartsch</dc:creator>
      <dc:date>2017-12-10T12:04:56Z</dc:date>
    </item>
  </channel>
</rss>

