<?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>smackssb Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>smackssb Tracker</description>
    <pubDate>Sat, 25 Nov 2023 06:00:00 GMT</pubDate>
    <dc:date>2023-11-25T06:00:00Z</dc:date>
    <item>
      <title>Horizon on Azure POD won't deploy with NAT Gateway enabled subnet</title>
      <link>https://communities.vmware.com/t5/Horizon-Cloud/Horizon-on-Azure-POD-won-t-deploy-with-NAT-Gateway-enabled/m-p/2904507#M240</link>
      <description>&lt;P&gt;We are transitioning from an on-prem horizon environment to a cloud based environment and one of the key requirements for us is we need our VMs to have a known static IP address and on Azure this is done by using a nat gateway. When I attempt to deploy a pod into subnets that have a nat gateway the deployment fails. I can deploy the pod into the same subnets successfully if I remove the nat gateway. I am deploying the pod without HA and no gateways to save time and keep things simple. When the deployment fails I just get the unrecognized error message so no help there and the only thing I have noticed during deployment is that if the nat gateway is configured the deployment only gets as far as creating the NSGs then everything stops and eventually the deployment errors out.&lt;/P&gt;</description>
      <pubDate>Fri, 15 Apr 2022 18:38:55 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Cloud/Horizon-on-Azure-POD-won-t-deploy-with-NAT-Gateway-enabled/m-p/2904507#M240</guid>
      <dc:creator>smackssb</dc:creator>
      <dc:date>2022-04-15T18:38:55Z</dc:date>
    </item>
    <item>
      <title>Re: Fusion 7  is running VERY SLOW on the GM of Yosemite</title>
      <link>https://communities.vmware.com/t5/VMware-Fusion-Discussions/Fusion-7-is-running-VERY-SLOW-on-the-GM-of-Yosemite/m-p/2701551#M166776</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have an iMac12,1 and am seeing the slow Fusion performance and also getting the 0x49 interrupt storm on CPU 0&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Oct 2014 17:04:38 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Fusion-Discussions/Fusion-7-is-running-VERY-SLOW-on-the-GM-of-Yosemite/m-p/2701551#M166776</guid>
      <dc:creator>smackssb</dc:creator>
      <dc:date>2014-10-21T17:04:38Z</dc:date>
    </item>
    <item>
      <title>Fusion 6.0.2 Full-screen VM bug</title>
      <link>https://communities.vmware.com/t5/VMware-Fusion-Discussions/Fusion-6-0-2-Full-screen-VM-bug/m-p/969398#M53921</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have a iMac with 2 displays running Mavericks and Fusion 6.0.2 - ever since upgrading to Mavericks I've experienced various issues with full screen VMs some of which have already been discussed here. My current issues with Fusion 6.0.2 are:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- When I start a VM it always goes to a space on my first display (in my setup the primary display is on the right and my secondary display is on the left) even though the fusion UI is on the secondary display and VMWare's menu bar is focused on the secondary display. This is a new issue in 6.0.2. I can move the vm to the second display by returning it to a single window dragging the window onto the second display and going full screen again but once I close the vm and open it again it goes back to the primary display.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- If I use the Window menu to cause a vm to be displayed the space taken by the menu bar is left blank and the vm is no longer fully full screen. The menu bar is functional as well as clicking in the space will open the pull down menu. If I use the four finger swipe to switch spaces the menu bar is not shown and the vm takes the entire screen. To clear the invisible menu bar I have to drop to window mode and back to full screen.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I currently have "Displays have separate spaces" checked&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Nov 2013 19:38:30 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Fusion-Discussions/Fusion-6-0-2-Full-screen-VM-bug/m-p/969398#M53921</guid>
      <dc:creator>smackssb</dc:creator>
      <dc:date>2013-11-08T19:38:30Z</dc:date>
    </item>
    <item>
      <title>Host shutdown does not shut down linux guests</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Host-shutdown-does-not-shut-down-linux-guests/m-p/903656#M74243</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am running a vSphere Essentials installation with 3 hosts and am working on automatic shutdown in the event of a power failure. The one issue I have discovered is that running linux guests don't shutdown gracefully when I issue a host shutdown command via the hostops command or even using the vSphere client to shut the system down. I do not want to go into maintenance mode as I need to have my vMA running until the last possible moment and I need vms to come back online after power is restored. Windows guests shut down gracefully when a host shutdown is started but linux guests just sit there until the host itself goes down. This even happens with the most current tools installed. The wierd part is if I explicitly ask for a graceful shutdown of the linux vm either via the command line or the vsphere client the linux os shuts down gracefully. Is this a known issue? Without a fix I am going to have to manually issue shutdown commands to all vms before I shut down the host, not a big deal but more messy than I would have liked.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 Jan 2013 19:08:27 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Host-shutdown-does-not-shut-down-linux-guests/m-p/903656#M74243</guid>
      <dc:creator>smackssb</dc:creator>
      <dc:date>2013-01-23T19:08:27Z</dc:date>
    </item>
    <item>
      <title>vCenter 5.1 SSO can see users but not groups</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/vCenter-5-1-SSO-can-see-users-but-not-groups/m-p/438827#M13262</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have finally managed to upgrade to 5.1 and gotten SSO to talk to our LDAP server but I am not getting any groups back only users. We have a samba implementation using LDAP for the backend and since SSO returns nothing when we attempt to use it with the Active Directory setting we are using OpenLDAP which works fine but only returns users and we don't get any groups. Any ideas? Here's what ldapsearch shows for one of our groups with names changed to protect the guilty &lt;img id="smileyhappy" class="emoticon emoticon-smileyhappy" src="https://communities.vmware.com/i/smilies/16x16_smiley-happy.png" alt="Smiley Happy" title="Smiley Happy" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;DIV id="_mcePaste"&gt;# test, Groups, ssbbartgroup.com&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;dn: cn=test,ou=Groups,dc=ssbbartgroup,dc=com&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;objectClass: top&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;objectClass: posixGroup&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;objectClass: sambaGroupMapping&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;cn: sales&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;gidNumber: &amp;lt;deleted&amp;gt;&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;sambaSID: &amp;lt;deleted&amp;gt;&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;sambaGroupType: 2&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;displayName: Test Group&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;description: Domain Unix group&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;memberUid: testuser&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Nov 2012 19:12:28 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/vCenter-5-1-SSO-can-see-users-but-not-groups/m-p/438827#M13262</guid>
      <dc:creator>smackssb</dc:creator>
      <dc:date>2012-11-29T19:12:28Z</dc:date>
    </item>
  </channel>
</rss>

