<?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/JAMF MDM Attributes in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-jamf-mdm-attributes/m-p/3828947#M474433</link>
    <description>&lt;P&gt;This capability was introduced as a requirement for Cisco IT wherein a script is used to add the UDID information in AD and compliant status from MDM is added to AD attribute.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;we can then create a posture condition to check for this using the UDID attribute.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;As of now UDID MDM query happens only in VPN case because Anyconnect don’t send MAC address to ISE (it sends MAC as Unknown or empty string), so in that case query happens based on UDID.&lt;/P&gt;
&lt;P&gt;In Normal Wireless/Wired MDM flow, ISE will use MAC address only to query.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Nidhi&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 29 Mar 2019 15:33:42 GMT</pubDate>
    <dc:creator>Nidhi</dc:creator>
    <dc:date>2019-03-29T15:33:42Z</dc:date>
    <item>
      <title>ISE/JAMF MDM Attributes</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-jamf-mdm-attributes/m-p/3827344#M474421</link>
      <description>&lt;P&gt;Hello team,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Could anyone shed light on the expected behavior for JAMF MDM on Ethernet? My customer has been unable to get any attributes to show up for Ethernet and the MDMEnrolled shows false. Thanks!&lt;/P&gt;</description>
      <pubDate>Wed, 27 Mar 2019 17:56:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-jamf-mdm-attributes/m-p/3827344#M474421</guid>
      <dc:creator>caroolso</dc:creator>
      <dc:date>2019-03-27T17:56:32Z</dc:date>
    </item>
    <item>
      <title>Re: ISE/JAMF MDM Attributes</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-jamf-mdm-attributes/m-p/3827385#M474422</link>
      <description>&lt;P&gt;I have not tried Ethernet, but from what we have seen on JAMF, it needs to load the enrollment web page before ISE will see it as compliant. You may need to set up a redirect to force this.&lt;/P&gt;</description>
      <pubDate>Wed, 27 Mar 2019 18:23:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-jamf-mdm-attributes/m-p/3827385#M474422</guid>
      <dc:creator>Dustin Anderson</dc:creator>
      <dc:date>2019-03-27T18:23:04Z</dc:date>
    </item>
    <item>
      <title>Re: ISE/JAMF MDM Attributes</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-jamf-mdm-attributes/m-p/3827396#M474423</link>
      <description>&lt;P&gt;From what I have experienced, JAMF only keeps the wifi mac address of the device as an identifier. In the case of Ethernet connection, ISE would send the ethernet adapter/dongle mac address which usually does not match that identifier. I do recall that there were plans for JAMF to add more identifiers so that it ISE can match against those. Don't know if they have done that yet. Furthermore, dongles are usually hard to maintain as users could bring their own dongles to connect their laptops. Probably a endpoint group of approved dongles on ISE + the ability for users to add their own dongle mac addresses (using mydevices portal) might be a way to go.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 27 Mar 2019 18:35:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-jamf-mdm-attributes/m-p/3827396#M474423</guid>
      <dc:creator>Rahul Govindan</dc:creator>
      <dc:date>2019-03-27T18:35:25Z</dc:date>
    </item>
    <item>
      <title>Re: ISE/JAMF MDM Attributes</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-jamf-mdm-attributes/m-p/3827407#M474424</link>
      <description>&lt;P&gt;JAMF can have 2 identifiers, but yes, the dongles are annoying as we have 1 user that bounces through 3 of them.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;OP may be talking about iMacs or Mac Pro's so may not worry about wireless nic.&lt;/P&gt;</description>
      <pubDate>Wed, 27 Mar 2019 18:52:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-jamf-mdm-attributes/m-p/3827407#M474424</guid>
      <dc:creator>Dustin Anderson</dc:creator>
      <dc:date>2019-03-27T18:52:06Z</dc:date>
    </item>
    <item>
      <title>Re: ISE/JAMF MDM Attributes</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-jamf-mdm-attributes/m-p/3827410#M474425</link>
      <description>In 2.6 we do more with anyconnect and shared dongles as well&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/ise/2-6/release_notes/b_ise_26_RN.html#id_87508" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/ise/2-6/release_notes/b_ise_26_RN.html#id_87508&lt;/A&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 27 Mar 2019 18:55:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-jamf-mdm-attributes/m-p/3827410#M474425</guid>
      <dc:creator>Jason Kunst</dc:creator>
      <dc:date>2019-03-27T18:55:33Z</dc:date>
    </item>
    <item>
      <title>Re: ISE/JAMF MDM Attributes</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-jamf-mdm-attributes/m-p/3827419#M474427</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/199790"&gt;@Jason Kunst&lt;/a&gt;: Great to hear. I am assuming that only the AnyConnect 4.7 ISE posture module is required for this to work. Any examples of this in action? Also, how does the an administrator get this UDID to be added to MDM beforehand?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This does not solve the Dongle use case but at least captures use cases with static docks and ethernet ports.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 27 Mar 2019 19:18:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-jamf-mdm-attributes/m-p/3827419#M474427</guid>
      <dc:creator>Rahul Govindan</dc:creator>
      <dc:date>2019-03-27T19:18:57Z</dc:date>
    </item>
    <item>
      <title>Re: ISE/JAMF MDM Attributes</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-jamf-mdm-attributes/m-p/3827431#M474429</link>
      <description>&lt;P&gt;I reached out to the SMEs to take a look&lt;/P&gt;</description>
      <pubDate>Wed, 27 Mar 2019 19:28:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-jamf-mdm-attributes/m-p/3827431#M474429</guid>
      <dc:creator>Jason Kunst</dc:creator>
      <dc:date>2019-03-27T19:28:56Z</dc:date>
    </item>
    <item>
      <title>Re: ISE/JAMF MDM Attributes</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-jamf-mdm-attributes/m-p/3827569#M474430</link>
      <description>&lt;P&gt;Thanks Jason, please keep us posted.&lt;/P&gt;</description>
      <pubDate>Wed, 27 Mar 2019 22:12:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-jamf-mdm-attributes/m-p/3827569#M474430</guid>
      <dc:creator>caroolso</dc:creator>
      <dc:date>2019-03-27T22:12:41Z</dc:date>
    </item>
    <item>
      <title>Re: ISE/JAMF MDM Attributes</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-jamf-mdm-attributes/m-p/3828287#M474431</link>
      <description>&lt;P&gt;Hello,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;AC 4.7 is the minimum version needed for the UDID support. The UDID for the endpoint is sent to ISE via Anyconnect agent. you can view this in endpoint attribute list.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The MDM vendor fetches the UDID during the enrollment as its another endpoint attribute.&lt;/P&gt;
&lt;P&gt;With the MDM flow in ISE, ISE makes an API call to MDM using this UDID to get the compliance information !&lt;/P&gt;
&lt;P&gt;hope this helps.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Nidhi&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 28 Mar 2019 17:08:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-jamf-mdm-attributes/m-p/3828287#M474431</guid>
      <dc:creator>Nidhi</dc:creator>
      <dc:date>2019-03-28T17:08:56Z</dc:date>
    </item>
    <item>
      <title>Re: ISE/JAMF MDM Attributes</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-jamf-mdm-attributes/m-p/3828377#M474432</link>
      <description>Hi Nidhi,&lt;BR /&gt;&lt;BR /&gt;Thanks for the information here. So is the only way for my customer to see the attributes for JAMF MDM Ethernet to use the AnyConnect 4.7 integration?&lt;BR /&gt;&lt;BR /&gt;Also, could you confirm that seeing no attributes and "False" MDMEnrolled is expected behavior without the AC integration?&lt;BR /&gt;&lt;BR /&gt;Thanks!</description>
      <pubDate>Thu, 28 Mar 2019 18:02:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-jamf-mdm-attributes/m-p/3828377#M474432</guid>
      <dc:creator>caroolso</dc:creator>
      <dc:date>2019-03-28T18:02:57Z</dc:date>
    </item>
    <item>
      <title>Re: ISE/JAMF MDM Attributes</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-jamf-mdm-attributes/m-p/3828947#M474433</link>
      <description>&lt;P&gt;This capability was introduced as a requirement for Cisco IT wherein a script is used to add the UDID information in AD and compliant status from MDM is added to AD attribute.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;we can then create a posture condition to check for this using the UDID attribute.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;As of now UDID MDM query happens only in VPN case because Anyconnect don’t send MAC address to ISE (it sends MAC as Unknown or empty string), so in that case query happens based on UDID.&lt;/P&gt;
&lt;P&gt;In Normal Wireless/Wired MDM flow, ISE will use MAC address only to query.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Nidhi&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 29 Mar 2019 15:33:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-jamf-mdm-attributes/m-p/3828947#M474433</guid>
      <dc:creator>Nidhi</dc:creator>
      <dc:date>2019-03-29T15:33:42Z</dc:date>
    </item>
    <item>
      <title>Re: ISE/JAMF MDM Attributes</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-jamf-mdm-attributes/m-p/3839569#M474434</link>
      <description>&lt;P&gt;Hey&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/359830"&gt;@Nidhi&lt;/a&gt;&amp;nbsp; -&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I understand that 2.6 + AC 4.7 supports sending the UDID via the posture flow, but is this would only cover customers using ISE posture. In the past, Jamf would get the MAC addresses of whatever NICs (I believe up to two of them) when it registers initially or when sudo jamf recon is run.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is there some way to get Jamf to reconfigure via an AuthZ policy/DACL so that it (with the right access to the server, of course) can update the MAC addresses for the Mac OS device? We had not planned to use posture and this customer does not have the license required as far as I know.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 16 Apr 2019 15:06:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-jamf-mdm-attributes/m-p/3839569#M474434</guid>
      <dc:creator>ruhearn</dc:creator>
      <dc:date>2019-04-16T15:06:03Z</dc:date>
    </item>
    <item>
      <title>Re: ISE/JAMF MDM Attributes</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-jamf-mdm-attributes/m-p/4150475#M562821</link>
      <description>&lt;P&gt;Hi Nidhi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Do you happen to know if this is already supported for non-VPN solutions?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Jayson&lt;/P&gt;</description>
      <pubDate>Mon, 14 Sep 2020 02:33:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-jamf-mdm-attributes/m-p/4150475#M562821</guid>
      <dc:creator>pagosojayson</dc:creator>
      <dc:date>2020-09-14T02:33:38Z</dc:date>
    </item>
  </channel>
</rss>

