<?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>jwininger Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>jwininger Tracker</description>
    <pubDate>Fri, 24 Nov 2023 01:25:18 GMT</pubDate>
    <dc:date>2023-11-24T01:25:18Z</dc:date>
    <item>
      <title>Re: VCSA 6.7 U2 Converge failure</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/VCSA-6-7-U2-Converge-failure/m-p/1855156#M59618</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Same issue here...anyone resolve yet?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 13 Oct 2019 02:27:48 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/VCSA-6-7-U2-Converge-failure/m-p/1855156#M59618</guid>
      <dc:creator>jwininger</dc:creator>
      <dc:date>2019-10-13T02:27:48Z</dc:date>
    </item>
    <item>
      <title>Re: VMware horizon crashing mac update</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/VMware-horizon-crashing-mac-update/m-p/1843931#M83486</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The issue seems to be related to automatic graphics switching in MacOS 10.14.4.&amp;nbsp; I disabled it and the crashes have stopped with the latest View client.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 May 2019 02:13:53 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/VMware-horizon-crashing-mac-update/m-p/1843931#M83486</guid>
      <dc:creator>jwininger</dc:creator>
      <dc:date>2019-05-09T02:13:53Z</dc:date>
    </item>
    <item>
      <title>Re: VMware horizon crashing mac update</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/VMware-horizon-crashing-mac-update/m-p/1843922#M83477</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Crashing for me as well.&amp;nbsp; I'm running MacOS 10.14.4.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Apr 2019 01:54:53 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/VMware-horizon-crashing-mac-update/m-p/1843922#M83477</guid>
      <dc:creator>jwininger</dc:creator>
      <dc:date>2019-04-04T01:54:53Z</dc:date>
    </item>
    <item>
      <title>Re: Identity Manager 3.3.0 cannot save licenese Key</title>
      <link>https://communities.vmware.com/t5/Workspace-ONE-Discussions/Identity-Manager-3-3-0-cannot-save-licenese-Key/m-p/1368555#M4754</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I had a support request open for this same issue and we discovered that the key does get saved to the database even though the error occurs on the admin page.&amp;nbsp; How this issue made it to a released product I don't understand.&amp;nbsp; Every release has bug(s) like this...making it impossible to get on a stable release.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Nov 2018 02:56:30 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Workspace-ONE-Discussions/Identity-Manager-3-3-0-cannot-save-licenese-Key/m-p/1368555#M4754</guid>
      <dc:creator>jwininger</dc:creator>
      <dc:date>2018-11-08T02:56:30Z</dc:date>
    </item>
    <item>
      <title>Re: Trend Micro Deep Security with Instant Clone Desktops</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Trend-Micro-Deep-Security-with-Instant-Clone-Desktops/m-p/1376909#M80024</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Did you get a resolution to this issue?&amp;nbsp; I'm seeing the same thing with instant clones and Deep Security 11.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Jun 2018 13:21:07 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Trend-Micro-Deep-Security-with-Instant-Clone-Desktops/m-p/1376909#M80024</guid>
      <dc:creator>jwininger</dc:creator>
      <dc:date>2018-06-28T13:21:07Z</dc:date>
    </item>
    <item>
      <title>Re: View crashing hostd on ESXi hosts</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/View-crashing-hostd-on-ESXi-hosts/m-p/2737346#M91827</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I identified the source of the issue.&amp;nbsp; When View initiates space reclamation against VMs on ESXi 6.5 VMFS 6 volumes, it crashes hostd.&amp;nbsp; I disabled space reclamation on the desktop pools, and the crashes stopped.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 02 Jun 2018 04:10:46 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/View-crashing-hostd-on-ESXi-hosts/m-p/2737346#M91827</guid>
      <dc:creator>jwininger</dc:creator>
      <dc:date>2018-06-02T04:10:46Z</dc:date>
    </item>
    <item>
      <title>Re: view 7.5 upgrade issue</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/view-7-5-upgrade-issue/m-p/489622#M11542</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I had the same issue in my test environment.&amp;nbsp; I resolved it by uninstalling the Connection server, but leaving the AD LDS data in place...then reran the 7.5 installer.&amp;nbsp; Wonder if it's an issue upgrading from versions other than 7.4.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 May 2018 17:58:41 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/view-7-5-upgrade-issue/m-p/489622#M11542</guid>
      <dc:creator>jwininger</dc:creator>
      <dc:date>2018-05-31T17:58:41Z</dc:date>
    </item>
    <item>
      <title>Re: View crashing hostd on ESXi hosts</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/View-crashing-hostd-on-ESXi-hosts/m-p/2737345#M91826</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It's more of a theory at this point. I have an SR opened regarding the issue, but the engineer has only stated that it's a known issue and that I need to install update 2...which is doesn't sound feasible since it was just released a few weeks ago.&amp;nbsp; He refuses to provide any details on the root cause.&amp;nbsp; It seems to only occur when new VMs are provisioned.&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 May 2018 13:29:17 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/View-crashing-hostd-on-ESXi-hosts/m-p/2737345#M91826</guid>
      <dc:creator>jwininger</dc:creator>
      <dc:date>2018-05-31T13:29:17Z</dc:date>
    </item>
    <item>
      <title>View crashing hostd on ESXi hosts</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/View-crashing-hostd-on-ESXi-hosts/m-p/2737343#M91824</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Anyone experienced View 7.1 causing hostd to crash on ESXi 6.5 hosts?&amp;nbsp;&amp;nbsp; It seems to occur when new VMs are provisioned.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 May 2018 02:49:19 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/View-crashing-hostd-on-ESXi-hosts/m-p/2737343#M91824</guid>
      <dc:creator>jwininger</dc:creator>
      <dc:date>2018-05-31T02:49:19Z</dc:date>
    </item>
    <item>
      <title>Re: Identity Manager and DUO</title>
      <link>https://communities.vmware.com/t5/Workspace-ONE-Discussions/Identity-Manager-and-DUO/m-p/2727361#M14335</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've done some limited testing with Duo, and it seems to work well.&amp;nbsp; We plan to pilot it with some of our IT staff soon.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 Apr 2018 18:01:39 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Workspace-ONE-Discussions/Identity-Manager-and-DUO/m-p/2727361#M14335</guid>
      <dc:creator>jwininger</dc:creator>
      <dc:date>2018-04-20T18:01:39Z</dc:date>
    </item>
    <item>
      <title>"Session Expired, trying to renew" message when logging on to Identity Manager</title>
      <link>https://communities.vmware.com/t5/Workspace-ONE-Discussions/quot-Session-Expired-trying-to-renew-quot-message-when-logging/m-p/2726591#M14331</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;After creating a 3 node cluster, users often receive a &lt;STRONG&gt;"Session Expired, trying to renew" &lt;/STRONG&gt;message when logging on.&amp;nbsp; The message usually disappears after a few seconds, but for some users is remaining and preventing log on.&amp;nbsp; Will setting the service.numberOfLoadBalancers option resolve this?&amp;nbsp; It's listed as optional in the documentation.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 14 Apr 2018 21:12:28 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Workspace-ONE-Discussions/quot-Session-Expired-trying-to-renew-quot-message-when-logging/m-p/2726591#M14331</guid>
      <dc:creator>jwininger</dc:creator>
      <dc:date>2018-04-14T21:12:28Z</dc:date>
    </item>
    <item>
      <title>Re: Identity Manager 3.1 slow boot</title>
      <link>https://communities.vmware.com/t5/Workspace-ONE-Discussions/Identity-Manager-3-1-slow-boot/m-p/973870#M4319</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I opened a support request and was informed that the issue is a known bug that will be resolved in the next release...3.2.&amp;nbsp; Not sure how such a bug made it past QA in the current release.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 06 Mar 2018 04:02:33 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Workspace-ONE-Discussions/Identity-Manager-3-1-slow-boot/m-p/973870#M4319</guid>
      <dc:creator>jwininger</dc:creator>
      <dc:date>2018-03-06T04:02:33Z</dc:date>
    </item>
    <item>
      <title>Re: Identity Manager 3.1 slow boot</title>
      <link>https://communities.vmware.com/t5/Workspace-ONE-Discussions/Identity-Manager-3-1-slow-boot/m-p/973868#M4317</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The file didn't exist, but creating it made no difference.&amp;nbsp; What else could be causing the issue?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Feb 2018 20:36:12 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Workspace-ONE-Discussions/Identity-Manager-3-1-slow-boot/m-p/973868#M4317</guid>
      <dc:creator>jwininger</dc:creator>
      <dc:date>2018-02-26T20:36:12Z</dc:date>
    </item>
    <item>
      <title>Identity Manager 3.1 slow boot</title>
      <link>https://communities.vmware.com/t5/Workspace-ONE-Discussions/Identity-Manager-3-1-slow-boot/m-p/973865#M4314</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I upgraded my test environement from 2.8.1 to 2.9.2...then to 3.1.&amp;nbsp; The boot process is now extremely slow, hanging on multiple "logger: updateiptables.hzn Discovering IP address" messages.&amp;nbsp; Anyone else experienced this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, on a different note, this product has always been extremely buggy.&amp;nbsp; Every upgrade has had a new major issue.&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Feb 2018 22:18:40 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Workspace-ONE-Discussions/Identity-Manager-3-1-slow-boot/m-p/973865#M4314</guid>
      <dc:creator>jwininger</dc:creator>
      <dc:date>2018-02-14T22:18:40Z</dc:date>
    </item>
    <item>
      <title>Re: vSphere 6.5 Host Profile vmk0 deleted -what gives?</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/vSphere-6-5-Host-Profile-vmk0-deleted-what-gives/m-p/970734#M12097</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We had a similar issue with our 6.5 upgrade.&amp;nbsp; In our case, we had vmk0 for managment and vmk1 for vmotion.&amp;nbsp; Applying the host profile would just end up deleting vmk0 .&amp;nbsp; We ended up just manually configuring the networking on our hosts so that we could complete the upgrade.&amp;nbsp; I tried opening a support ticket, but they were clueless on the use of host profiles...so I just gave up.&amp;nbsp; What hardware are you using?&amp;nbsp; We use Cisco M4 blades.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The following link details the issue...but no resolution.&lt;/P&gt;&lt;P&gt;&lt;A href="https://communities.vmware.com/thread/571949"&gt;vSphere 6.5 + Host Profiles + vDS Networks&lt;/A&gt; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 07 Feb 2018 16:45:17 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/vSphere-6-5-Host-Profile-vmk0-deleted-what-gives/m-p/970734#M12097</guid>
      <dc:creator>jwininger</dc:creator>
      <dc:date>2018-02-07T16:45:17Z</dc:date>
    </item>
    <item>
      <title>Re: vSphere 6.5 + Host Profiles + vDS Networks</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vSphere-6-5-Host-Profiles-vDS-Networks/m-p/1756861#M22428</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is there any more information on this?&amp;nbsp;&amp;nbsp; Anyone get a resolution??&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Dec 2017 17:55:44 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vSphere-6-5-Host-Profiles-vDS-Networks/m-p/1756861#M22428</guid>
      <dc:creator>jwininger</dc:creator>
      <dc:date>2017-12-14T17:55:44Z</dc:date>
    </item>
    <item>
      <title>Re: vSphere 6.5 + Host Profiles + vDS Networks</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vSphere-6-5-Host-Profiles-vDS-Networks/m-p/1756859#M22426</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Did you get a resolution for this issue?&amp;nbsp; I'm having the same problem.&amp;nbsp; Issue only occurs after updating vCenter and hosts to 6.5 U1.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 06 Nov 2017 18:23:54 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vSphere-6-5-Host-Profiles-vDS-Networks/m-p/1756859#M22426</guid>
      <dc:creator>jwininger</dc:creator>
      <dc:date>2017-11-06T18:23:54Z</dc:date>
    </item>
    <item>
      <title>Re: vSAN 6.6 - Online check of vSAN health fails with the general vSAN error.</title>
      <link>https://communities.vmware.com/t5/VMware-vSAN-Discussions/vSAN-6-6-Online-check-of-vSAN-health-fails-with-the-general-vSAN/m-p/932359#M2545</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Were you able to resolve this issue?&amp;nbsp; I see the same problem in my environment.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Sep 2017 03:14:39 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSAN-Discussions/vSAN-6-6-Online-check-of-vSAN-health-fails-with-the-general-vSAN/m-p/932359#M2545</guid>
      <dc:creator>jwininger</dc:creator>
      <dc:date>2017-09-01T03:14:39Z</dc:date>
    </item>
    <item>
      <title>Re: VSAN Build Recommendation Engine Proxy settings.</title>
      <link>https://communities.vmware.com/t5/VMware-vSAN-Discussions/VSAN-Build-Recommendation-Engine-Proxy-settings/m-p/489003#M1334</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Were you able to find a resolution to this issue?&amp;nbsp; I'm seeing the same in my environment.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Sep 2017 02:48:53 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSAN-Discussions/VSAN-Build-Recommendation-Engine-Proxy-settings/m-p/489003#M1334</guid>
      <dc:creator>jwininger</dc:creator>
      <dc:date>2017-09-01T02:48:53Z</dc:date>
    </item>
    <item>
      <title>vROPS and Access Point 2.8</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/vROPS-and-Access-Point-2-8/m-p/1415498#M82232</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="color: #666666; font-size: 14pt; font-family: Arial, Helvetica, sans-serif;"&gt;Testing Access Point 2.8 with View 7.0.2. In vrealize operations manager, I'm able to see stats on the security servers, but not the access point. The release notes for 2.8 of the access point state that monitoring is available in vROPS. How does it need to be configured? &lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 03 Dec 2016 07:47:19 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/vROPS-and-Access-Point-2-8/m-p/1415498#M82232</guid>
      <dc:creator>jwininger</dc:creator>
      <dc:date>2016-12-03T07:47:19Z</dc:date>
    </item>
  </channel>
</rss>

