<?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: ISE 2.2 Reprofiling After Adding New Profile Policies in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-2-2-reprofiling-after-adding-new-profile-policies/m-p/3591388#M535603</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So what would cause the deployment to not do that?  I couldn’t find any settings the customer may have mistakenly turned off.  I was sure in the other deployments I had done with 2.2 it still worked as well.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Paul Haferman&lt;/P&gt;&lt;P&gt;Office- 920.996.3011&lt;/P&gt;&lt;P&gt;Cell- 920.284.9250&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 14 Jun 2017 21:21:22 GMT</pubDate>
    <dc:creator>paul</dc:creator>
    <dc:date>2017-06-14T21:21:22Z</dc:date>
    <item>
      <title>ISE 2.2 Reprofiling After Adding New Profile Policies</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-2-reprofiling-after-adding-new-profile-policies/m-p/3591386#M535601</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am working on an install at a customer and I am showing them how to build out their profile policies as we learn stuff in monitoring mode.&amp;nbsp; We are running 2.2 patch 1.&amp;nbsp; Usually when I add new profile policies that have higher minimum certainty factors than the current matched profiles, ISE will run my new policies against the endpoints and reprofile them within minutes.&amp;nbsp; In this customer's case we have waited hours and they haven't reprofiled.&amp;nbsp; If I delete the MAC address from the Endpoint database and have it reauthenticate it will profile correctly into my new policies.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Has this behavior changed in 2.2?&amp;nbsp; I am going to test it in my lab today if I have time, but wanted to send out the question to the group.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Jun 2017 21:06:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-2-reprofiling-after-adding-new-profile-policies/m-p/3591386#M535601</guid>
      <dc:creator>paul</dc:creator>
      <dc:date>2017-06-14T21:06:47Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.2 Reprofiling After Adding New Profile Policies</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-2-reprofiling-after-adding-new-profile-policies/m-p/3591387#M535602</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That is still the behavior or ISE 2.2 when you modify profiling policy.&amp;nbsp; I just recently tested this in my lab and can confirm that is the case.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;-Tim&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Jun 2017 21:10:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-2-reprofiling-after-adding-new-profile-policies/m-p/3591387#M535602</guid>
      <dc:creator>Timothy Abbott</dc:creator>
      <dc:date>2017-06-14T21:10:51Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.2 Reprofiling After Adding New Profile Policies</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-2-reprofiling-after-adding-new-profile-policies/m-p/3591388#M535603</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So what would cause the deployment to not do that?  I couldn’t find any settings the customer may have mistakenly turned off.  I was sure in the other deployments I had done with 2.2 it still worked as well.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Paul Haferman&lt;/P&gt;&lt;P&gt;Office- 920.996.3011&lt;/P&gt;&lt;P&gt;Cell- 920.284.9250&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Jun 2017 21:21:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-2-reprofiling-after-adding-new-profile-policies/m-p/3591388#M535603</guid>
      <dc:creator>paul</dc:creator>
      <dc:date>2017-06-14T21:21:22Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.2 Reprofiling After Adding New Profile Policies</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-2-reprofiling-after-adding-new-profile-policies/m-p/3591389#M535604</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Honestly, I'm not 100% sure since I know that if any of the profile policies are modified, ISE attempts to reprofile all endpoints it knows about.&amp;nbsp; If the behavior continues, I suggest reaching out to the TAC.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;-Tim&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Jun 2017 14:43:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-2-reprofiling-after-adding-new-profile-policies/m-p/3591389#M535604</guid>
      <dc:creator>Timothy Abbott</dc:creator>
      <dc:date>2017-06-15T14:43:07Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.2 Reprofiling After Adding New Profile Policies</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-2-reprofiling-after-adding-new-profile-policies/m-p/3591390#M535605</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Paul,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am seeing this same behaviour with my deployment with a customer and I have not yet contacted TAC about the issue but will soon be submitting a case with them.&amp;nbsp; My deployment is 3 physical appliances that we upgraded from ISE 2.0 to 2.2 Patch 1.&amp;nbsp; If you find any more information out about the issue, could you please update this post so I know as well.&amp;nbsp; I will also update once we have had a chance for TAC to investigate.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Alex Martin&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 Jun 2017 03:59:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-2-reprofiling-after-adding-new-profile-policies/m-p/3591390#M535605</guid>
      <dc:creator>Alex Martin</dc:creator>
      <dc:date>2017-06-20T03:59:48Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.2 Reprofiling After Adding New Profile Policies</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-2-reprofiling-after-adding-new-profile-policies/m-p/3591391#M535606</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I haven’t done more research on this yet.  The devices eventually reprofiled, but it took some time.  I know at least a half hour after I added the new profile rules they hadn’t changed, but when I worked with the customer the next day things had reprofiled.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I will let you know if I find anything else out.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Paul Haferman&lt;/P&gt;&lt;P&gt;Office- 920.996.3011&lt;/P&gt;&lt;P&gt;Cell- 920.284.9250&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 Jun 2017 13:58:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-2-reprofiling-after-adding-new-profile-policies/m-p/3591391#M535606</guid>
      <dc:creator>paul</dc:creator>
      <dc:date>2017-06-20T13:58:10Z</dc:date>
    </item>
  </channel>
</rss>

