<?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.3 support for Microsoft SQL 2016 in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-2-3-support-for-microsoft-sql-2016/m-p/3539458#M517382</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I believe the MSSQL JDBC driver version in ISE 2.3 supporting SQL server 2016, but I will investigate and get back.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 29 Mar 2018 15:50:15 GMT</pubDate>
    <dc:creator>hslai</dc:creator>
    <dc:date>2018-03-29T15:50:15Z</dc:date>
    <item>
      <title>ISE 2.3 support for Microsoft SQL 2016</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-3-support-for-microsoft-sql-2016/m-p/3539457#M517381</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;Could someone please confirm when will ISE 2.3 start supporting Microsoft SQL 2016 as an external identity source?&lt;/P&gt;&lt;P&gt;Thanks and Regards&lt;/P&gt;&lt;P&gt;V Vinodh.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Mar 2018 15:19:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-3-support-for-microsoft-sql-2016/m-p/3539457#M517381</guid>
      <dc:creator>junk1</dc:creator>
      <dc:date>2018-03-29T15:19:01Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.3 support for Microsoft SQL 2016</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-3-support-for-microsoft-sql-2016/m-p/3539458#M517382</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I believe the MSSQL JDBC driver version in ISE 2.3 supporting SQL server 2016, but I will investigate and get back.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Mar 2018 15:50:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-3-support-for-microsoft-sql-2016/m-p/3539458#M517382</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2018-03-29T15:50:15Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.3 support for Microsoft SQL 2016</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-3-support-for-microsoft-sql-2016/m-p/3539459#M517383</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Assuming you are referring to it as an ODBC ID source under [Administration &amp;gt; Identity Management &amp;gt; External Identity Sources &amp;gt; ODBC], please go ahead and try it. If any issue, please turn DEBUG on odbc-id-store, then recreate, and report the errors in the debug log file.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ref: &lt;A href="https://www.cisco.com/c/en/us/support/docs/security/identity-services-engine-21/200544-Configure-ISE-2-1-with-MS-SQL-using-ODBC.html?referring_site=RE&amp;amp;pos=1&amp;amp;page=https://www.cisco.com/c/en/us/support/docs/security/identity-services-engine/211581-Configure-ODBC-on-ISE-2-3-with-Oracle-Da.html" title="https://www.cisco.com/c/en/us/support/docs/security/identity-services-engine-21/200544-Configure-ISE-2-1-with-MS-SQL-using-ODBC.html?referring_site=RE&amp;amp;pos=1&amp;amp;page=https://www.cisco.com/c/en/us/support/docs/security/identity-services-engine/211581-Configure-ODBC-on-ISE-2-3-with-Oracle-Da.html"&gt;Configure ISE 2.1 with MS SQL using ODBC - Cisco&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 Apr 2018 13:09:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-3-support-for-microsoft-sql-2016/m-p/3539459#M517383</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2018-04-02T13:09:40Z</dc:date>
    </item>
  </channel>
</rss>

