<?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: Automating imaging using ISE profiling in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/automating-imaging-using-ise-profiling/m-p/3896657#M474285</link>
    <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/158532"&gt;@Arne Bier&lt;/a&gt;&amp;nbsp;nothing different from what you mentioned.&amp;nbsp; The current process leverages mab.&amp;nbsp; However, I am in the process of exploring ISE REST APIs, and my current environment is getting Ansible in a couple of months.&amp;nbsp; The hope is to potentially use Ansible and the ISE APIs to create a more automated workflow.&amp;nbsp; I can definitely let you know how that all plays out, but it will be a little bit of time.&amp;nbsp; Cheers&lt;/P&gt;</description>
    <pubDate>Wed, 24 Jul 2019 12:40:01 GMT</pubDate>
    <dc:creator>Mike.Cifelli</dc:creator>
    <dc:date>2019-07-24T12:40:01Z</dc:date>
    <item>
      <title>Automating imaging using ISE profiling</title>
      <link>https://community.cisco.com/t5/network-access-control/automating-imaging-using-ise-profiling/m-p/3830146#M474283</link>
      <description>&lt;P&gt;I am attempting to automate the imaging process in an environment by utilizing ISE profiling.&lt;BR /&gt;I have the following pieces working as expected:&lt;BR /&gt;Using the DHCP probe with the dhcp-class-identifier STARTSWITH PXEClient:Arch:.&amp;nbsp; The endpoint MACs move to a profiled endpoint group.&lt;/P&gt;&lt;P&gt;I have coa set to reauth which is where my issues are. Upon reauth the device gets re-profiled and removed from the endpoint group in ISE. Therefore the device hits a different policy upon reauth.&amp;nbsp; I would like to have hosts get profiled, added to a group, re-authenticate and get restricted authorization upon reauth to complete pxe boot process.&amp;nbsp; Then finally purge endpoints after 1-2 days, which I have setup now.&lt;/P&gt;&lt;P&gt;Does anyone have a better/easier way of utilizing device profiling to automate an imaging process?&lt;/P&gt;</description>
      <pubDate>Mon, 01 Apr 2019 18:23:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/automating-imaging-using-ise-profiling/m-p/3830146#M474283</guid>
      <dc:creator>Mike.Cifelli</dc:creator>
      <dc:date>2019-04-01T18:23:13Z</dc:date>
    </item>
    <item>
      <title>Re: Automating imaging using ISE profiling</title>
      <link>https://community.cisco.com/t5/network-access-control/automating-imaging-using-ise-profiling/m-p/3896633#M474284</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/833210"&gt;@Mike.Cifelli&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Did you ever find a solution to this question offline?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have to say I didn't know you could solve this via profiling, and in the past we used to tell customers to use MAB as a temporary workaround until the machine has been re-imaged (PXE Boot).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 24 Jul 2019 12:06:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/automating-imaging-using-ise-profiling/m-p/3896633#M474284</guid>
      <dc:creator>Arne Bier</dc:creator>
      <dc:date>2019-07-24T12:06:06Z</dc:date>
    </item>
    <item>
      <title>Re: Automating imaging using ISE profiling</title>
      <link>https://community.cisco.com/t5/network-access-control/automating-imaging-using-ise-profiling/m-p/3896657#M474285</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/158532"&gt;@Arne Bier&lt;/a&gt;&amp;nbsp;nothing different from what you mentioned.&amp;nbsp; The current process leverages mab.&amp;nbsp; However, I am in the process of exploring ISE REST APIs, and my current environment is getting Ansible in a couple of months.&amp;nbsp; The hope is to potentially use Ansible and the ISE APIs to create a more automated workflow.&amp;nbsp; I can definitely let you know how that all plays out, but it will be a little bit of time.&amp;nbsp; Cheers&lt;/P&gt;</description>
      <pubDate>Wed, 24 Jul 2019 12:40:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/automating-imaging-using-ise-profiling/m-p/3896657#M474285</guid>
      <dc:creator>Mike.Cifelli</dc:creator>
      <dc:date>2019-07-24T12:40:01Z</dc:date>
    </item>
    <item>
      <title>Re: Automating imaging using ISE profiling</title>
      <link>https://community.cisco.com/t5/network-access-control/automating-imaging-using-ise-profiling/m-p/5542635#M600182</link>
      <description>&lt;P&gt;Since this was in 2019&lt;/P&gt;
&lt;P&gt;now we are in 2026&lt;/P&gt;
&lt;P&gt;did you find an automated solution&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":beaming_face_with_smiling_eyes:"&gt;😁&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 03 Apr 2026 04:49:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/automating-imaging-using-ise-profiling/m-p/5542635#M600182</guid>
      <dc:creator>aysarmohamed</dc:creator>
      <dc:date>2026-04-03T04:49:35Z</dc:date>
    </item>
    <item>
      <title>Re: Automating imaging using ISE profiling</title>
      <link>https://community.cisco.com/t5/network-access-control/automating-imaging-using-ise-profiling/m-p/5543499#M600194</link>
      <description>&lt;P&gt;This legacy build process is still dependent on SCCM, which has had no significant enhancements to improve this flow.&lt;/P&gt;
&lt;P&gt;Many customers are moving to Autopilot, for which I built this solution:&lt;BR /&gt;&lt;A href="https://community.cisco.com/t5/security-knowledge-base/cisco-ise-and-microsoft-windows-autopilot/ta-p/5256754" target="_blank"&gt;https://community.cisco.com/t5/security-knowledge-base/cisco-ise-and-microsoft-windows-autopilot/ta-p/5256754&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 06 Apr 2026 23:36:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/automating-imaging-using-ise-profiling/m-p/5543499#M600194</guid>
      <dc:creator>Greg Gibbs</dc:creator>
      <dc:date>2026-04-06T23:36:11Z</dc:date>
    </item>
    <item>
      <title>Re: Automating imaging using ISE profiling</title>
      <link>https://community.cisco.com/t5/network-access-control/automating-imaging-using-ise-profiling/m-p/5551921#M600400</link>
      <description>&lt;P&gt;Thank you sir&lt;/P&gt;</description>
      <pubDate>Mon, 11 May 2026 03:19:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/automating-imaging-using-ise-profiling/m-p/5551921#M600400</guid>
      <dc:creator>aysarmohamed</dc:creator>
      <dc:date>2026-05-11T03:19:10Z</dc:date>
    </item>
  </channel>
</rss>

