<?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: Is EPM LCD module work for endpoints that are present On-Premise, can it work for devices that are using Entra ID in Endpoint Privilege Manager (EPM) Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/is-epm-lcd-module-work-for-endpoints-that-are-present-on-premise/m-p/1417532#M8322</link>
    <description>&lt;P&gt;Hi Mudit.  Short answer is LCD is supported/functions fine regardless if AD, workgroups, or EntraID is being used.  A couple of considerations to think about are as follows:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;When AD-joined, EPM sends the fully-qualified domain name (ex: computername.domain.suffix) to PAM when attempting to rotate a credential.  If the move to EntraID is first moving to a hybrid model (meaning AD joined AND EntraID joined) then you'll keep the same address in PAM.&lt;/LI&gt;&lt;LI&gt;When exclusively EntraID joined (not AD joined) - the FQDN domain that existed previously in the form of domain.suffix no longer applies since AD is no longer used.  You'll need to adjust your address field(s) in PAM to reflect the hostname of the machine as it matches in EPM.  Most likely you should just need to remove the domain.suffix from the computername.domain.suffix notation in PAM, leaving just the hostname of computername in the address in PAM.  I'd recommend scripting this with EPM's APIs once the move is completed or done in batches to ensure LCD still continues to function as expected.  If you're also using client certificate validation, you'll also need to probably plan on re-issuing those certificates to reflect the hostname changes as well.&lt;/LI&gt;&lt;/OL&gt;</description>
    <pubDate>Fri, 28 Feb 2025 20:06:31 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2025-02-28T20:06:31Z</dc:date>
    <item>
      <title>Is EPM LCD module work for endpoints that are present On-Premise, can it work for devices that are using Entra ID</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/is-epm-lcd-module-work-for-endpoints-that-are-present-on-premise/m-p/1417531#M8321</link>
      <description>&lt;P&gt;Hi Team,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Currently we are using the LCD module for EPM and the workstation that are being onboarded over On-premise (using LDAP/AD), however going forward our organization is going to move all the endpoints over Cloud (Entra ID), so I wanted to know if the EPM LCD module will be supporting that as well.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please suggest, incase if anyone has been engaged in the same.&lt;/P&gt;</description>
      <pubDate>Tue, 04 Feb 2025 06:44:02 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/is-epm-lcd-module-work-for-endpoints-that-are-present-on-premise/m-p/1417531#M8321</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-02-04T06:44:02Z</dc:date>
    </item>
    <item>
      <title>Re: Is EPM LCD module work for endpoints that are present On-Premise, can it work for devices that are using Entra ID</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/is-epm-lcd-module-work-for-endpoints-that-are-present-on-premise/m-p/1417532#M8322</link>
      <description>&lt;P&gt;Hi Mudit.  Short answer is LCD is supported/functions fine regardless if AD, workgroups, or EntraID is being used.  A couple of considerations to think about are as follows:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;When AD-joined, EPM sends the fully-qualified domain name (ex: computername.domain.suffix) to PAM when attempting to rotate a credential.  If the move to EntraID is first moving to a hybrid model (meaning AD joined AND EntraID joined) then you'll keep the same address in PAM.&lt;/LI&gt;&lt;LI&gt;When exclusively EntraID joined (not AD joined) - the FQDN domain that existed previously in the form of domain.suffix no longer applies since AD is no longer used.  You'll need to adjust your address field(s) in PAM to reflect the hostname of the machine as it matches in EPM.  Most likely you should just need to remove the domain.suffix from the computername.domain.suffix notation in PAM, leaving just the hostname of computername in the address in PAM.  I'd recommend scripting this with EPM's APIs once the move is completed or done in batches to ensure LCD still continues to function as expected.  If you're also using client certificate validation, you'll also need to probably plan on re-issuing those certificates to reflect the hostname changes as well.&lt;/LI&gt;&lt;/OL&gt;</description>
      <pubDate>Fri, 28 Feb 2025 20:06:31 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/is-epm-lcd-module-work-for-endpoints-that-are-present-on-premise/m-p/1417532#M8322</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-02-28T20:06:31Z</dc:date>
    </item>
  </channel>
</rss>

