<?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 Re: Flex config files - local in Dynamic Environment Manager</title>
    <link>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Flex-config-files-local/m-p/2943105#M7861</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/2019063"&gt;@tschuegy&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;That's fine as far as the DEM agent is concerned. Just be aware that depending on where that folder is located (and/or how you have managed ACLs) your end user might be able to add/remove/change settings, which would allow them to run executables with elevation, circumvent application blocking and Group Policy-based restrictions, et cetera.&lt;/P&gt;</description>
    <pubDate>Fri, 09 Dec 2022 15:42:55 GMT</pubDate>
    <dc:creator>DEMdev</dc:creator>
    <dc:date>2022-12-09T15:42:55Z</dc:date>
    <item>
      <title>Flex config files - local</title>
      <link>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Flex-config-files-local/m-p/2942399#M7858</link>
      <description>&lt;P&gt;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/3228914"&gt;@DEMdev&lt;/a&gt;&lt;/P&gt;&lt;P&gt;Currently we have a relatively slow login time of 13 seconds only for VMware DEM. During the analysis, we were able to bring the login time down to 8 seconds using conditions on the respective&lt;BR /&gt;Settings.&lt;BR /&gt;As a test, we then copied the entire "Flex config files" share locally to C:\Temp\VMwareDEM\general and switched the GPO "Flex config file" to this path. Is a local Configuration directory supported by VMware DEM? This gives us a login time of 2.8 seconds for VMware DEM.&lt;/P&gt;&lt;P&gt;Is this supported?&lt;/P&gt;</description>
      <pubDate>Tue, 06 Dec 2022 06:59:15 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Flex-config-files-local/m-p/2942399#M7858</guid>
      <dc:creator>tschuegy</dc:creator>
      <dc:date>2022-12-06T06:59:15Z</dc:date>
    </item>
    <item>
      <title>Re: Flex config files - local</title>
      <link>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Flex-config-files-local/m-p/2943105#M7861</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/2019063"&gt;@tschuegy&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;That's fine as far as the DEM agent is concerned. Just be aware that depending on where that folder is located (and/or how you have managed ACLs) your end user might be able to add/remove/change settings, which would allow them to run executables with elevation, circumvent application blocking and Group Policy-based restrictions, et cetera.&lt;/P&gt;</description>
      <pubDate>Fri, 09 Dec 2022 15:42:55 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Flex-config-files-local/m-p/2943105#M7861</guid>
      <dc:creator>DEMdev</dc:creator>
      <dc:date>2022-12-09T15:42:55Z</dc:date>
    </item>
    <item>
      <title>Re: Flex config files - local</title>
      <link>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Flex-config-files-local/m-p/2943493#M7866</link>
      <description>&lt;P&gt;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/3228914"&gt;@DEMdev&lt;/a&gt;&amp;nbsp;Thx for your reply.&amp;nbsp; I be aware for the ACLs. I'm mirroring the hole directory from the central share with acls (robocopy /mir /sec).&lt;/P&gt;</description>
      <pubDate>Mon, 12 Dec 2022 19:48:17 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Flex-config-files-local/m-p/2943493#M7866</guid>
      <dc:creator>tschuegy</dc:creator>
      <dc:date>2022-12-12T19:48:17Z</dc:date>
    </item>
  </channel>
</rss>

