<?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>topic Stacks not attaching after upgrade to 2.18 in App Volumes</title>
    <link>https://communities.vmware.com/t5/App-Volumes/Stacks-not-attaching-after-upgrade-to-2-18/m-p/516855#M5196</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This week I upgraded our two managers from 2.15 to 2.18.&amp;nbsp; They upgraded normally without issues or errors.&amp;nbsp; Afterwards I noticed that app stacks were not attaching for new logins.&amp;nbsp; Thinking that it may be something with the 2.18 managers and the 2.15 agent I pushed a new clone out with the 2.18 agent and that didn't resolve the issue.&amp;nbsp; We assign all stacks to security groups normally.&amp;nbsp; Assigning them to my user account or computer object made them attach fine.&amp;nbsp; Turning on the advanced setting option for "Disable Token AD query" also made them attach normally.&amp;nbsp; This option was previously off in 2.15 and worked just fine.&amp;nbsp; I would like to be able to turn that back off if someone has any ideas for what I might be missing. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Nothing immediately jumped out at me in the client side log or the server log.&amp;nbsp; Some additional information is below -&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Horizon 7.5.1&lt;/P&gt;&lt;P&gt;ESXi 6.0 U3&lt;/P&gt;&lt;P&gt;UEM/DEM 9.6&lt;/P&gt;&lt;P&gt;AppVol 2.18&lt;/P&gt;&lt;P&gt;Windows 10 1803 instant clones&lt;/P&gt;&lt;P&gt;Three domain forest, groups are in the top domain in the forest, user accounts in the groups are in the two child domains&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 10 Oct 2019 12:59:59 GMT</pubDate>
    <dc:creator>CoreyN</dc:creator>
    <dc:date>2019-10-10T12:59:59Z</dc:date>
    <item>
      <title>Stacks not attaching after upgrade to 2.18</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Stacks-not-attaching-after-upgrade-to-2-18/m-p/516855#M5196</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This week I upgraded our two managers from 2.15 to 2.18.&amp;nbsp; They upgraded normally without issues or errors.&amp;nbsp; Afterwards I noticed that app stacks were not attaching for new logins.&amp;nbsp; Thinking that it may be something with the 2.18 managers and the 2.15 agent I pushed a new clone out with the 2.18 agent and that didn't resolve the issue.&amp;nbsp; We assign all stacks to security groups normally.&amp;nbsp; Assigning them to my user account or computer object made them attach fine.&amp;nbsp; Turning on the advanced setting option for "Disable Token AD query" also made them attach normally.&amp;nbsp; This option was previously off in 2.15 and worked just fine.&amp;nbsp; I would like to be able to turn that back off if someone has any ideas for what I might be missing. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Nothing immediately jumped out at me in the client side log or the server log.&amp;nbsp; Some additional information is below -&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Horizon 7.5.1&lt;/P&gt;&lt;P&gt;ESXi 6.0 U3&lt;/P&gt;&lt;P&gt;UEM/DEM 9.6&lt;/P&gt;&lt;P&gt;AppVol 2.18&lt;/P&gt;&lt;P&gt;Windows 10 1803 instant clones&lt;/P&gt;&lt;P&gt;Three domain forest, groups are in the top domain in the forest, user accounts in the groups are in the two child domains&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Oct 2019 12:59:59 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Stacks-not-attaching-after-upgrade-to-2-18/m-p/516855#M5196</guid>
      <dc:creator>CoreyN</dc:creator>
      <dc:date>2019-10-10T12:59:59Z</dc:date>
    </item>
  </channel>
</rss>

