<?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 Allow dynamic CAL assignment Inadvertently Toggled On in Management &amp; Governance</title>
    <link>https://community.qlik.com/t5/Management-Governance/Allow-dynamic-CAL-assignment-Inadvertently-Toggled-On/m-p/2455850#M27287</link>
    <description>&lt;P&gt;&lt;SPAN&gt;"Allow dynamic CAL assignment" was inadvertently toggled on in QlikView May 2023 SR2. We now have users with named CALs that do not need them. What would be the best strategy to remove them and add users that do need them - including developers? Should "Allow dynamic CAL assignment" be toggled off, mark the users for removal and just wait out the quarantine period? Is there a way to override the quarantine period as 7 days seems like a long time to wait and may prevent reconciling the named licenses. We have 5 session CALs and 35 named CALs.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 24 May 2024 00:09:32 GMT</pubDate>
    <dc:creator>mpressey</dc:creator>
    <dc:date>2024-05-24T00:09:32Z</dc:date>
    <item>
      <title>Allow dynamic CAL assignment Inadvertently Toggled On</title>
      <link>https://community.qlik.com/t5/Management-Governance/Allow-dynamic-CAL-assignment-Inadvertently-Toggled-On/m-p/2455850#M27287</link>
      <description>&lt;P&gt;&lt;SPAN&gt;"Allow dynamic CAL assignment" was inadvertently toggled on in QlikView May 2023 SR2. We now have users with named CALs that do not need them. What would be the best strategy to remove them and add users that do need them - including developers? Should "Allow dynamic CAL assignment" be toggled off, mark the users for removal and just wait out the quarantine period? Is there a way to override the quarantine period as 7 days seems like a long time to wait and may prevent reconciling the named licenses. We have 5 session CALs and 35 named CALs.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 24 May 2024 00:09:32 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Allow-dynamic-CAL-assignment-Inadvertently-Toggled-On/m-p/2455850#M27287</guid>
      <dc:creator>mpressey</dc:creator>
      <dc:date>2024-05-24T00:09:32Z</dc:date>
    </item>
    <item>
      <title>Re: Allow dynamic CAL assignment Inadvertently Toggled On</title>
      <link>https://community.qlik.com/t5/Management-Governance/Allow-dynamic-CAL-assignment-Inadvertently-Toggled-On/m-p/2455965#M27291</link>
      <description>&lt;P&gt;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/42517"&gt;@mpressey&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Since you don't have many CALs you can delete the license assignment a redo it.&lt;/P&gt;
&lt;P&gt;The information is stored in .pgo files. All license assignments will be lost if you do this.&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Remove the old PGO files from your Qlikview installation.&lt;BR /&gt;Be sure to do these steps for all nodes in the QVS cluster, if your installation is clustered.
&lt;OL class="lia-list-style-type-lower-alpha"&gt;
&lt;LI&gt;Stop QVS and QMS (all nodes) as when you remove files it might still remain in the memory&lt;/LI&gt;
&lt;LI&gt;Delete the caldata.pgo and all other PGO files under the path configured for "user documents" in the QMC&amp;nbsp;and also "ProgramData\QlikTech\QlikViewServer" locally on all nodes&lt;/LI&gt;
&lt;LI&gt;Restart the services'&lt;/LI&gt;
&lt;/OL&gt;
&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;Be sure to make backups of the files before doing this.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 24 May 2024 07:52:10 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Allow-dynamic-CAL-assignment-Inadvertently-Toggled-On/m-p/2455965#M27291</guid>
      <dc:creator>Maria_Halley</dc:creator>
      <dc:date>2024-05-24T07:52:10Z</dc:date>
    </item>
  </channel>
</rss>

