<?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: Windows 10 Users facing Issues even with ISE 2.0 ( patch 3) in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/windows-10-users-facing-issues-even-with-ise-2-0-patch-3/m-p/3534538#M537993</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;IMHO that is the reverse of the bug so UNLIKELY the same bug. &lt;SPAN style="font-size: 10pt;"&gt;Please suggest TAC to try recreating it in TAC lab.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Windows 10.0.10240 is the first release of Windows 10 and using TLS 1.0 by default but not TLS 1.2.&lt;/P&gt;&lt;P&gt;Windows 10.0.10586 is the first major update of Windows 10 and using TLS 1.2 by default so this is what CSCuw88770 to address for.&lt;/P&gt;&lt;P&gt;Windows 10.0.14393 is the second major update of Windows 10, just released recently.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The customer should be upgrading 10.0.10240 to 10.0.10586 or 10.0.14393. It may as well be a Windows bug.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 11 Aug 2016 03:58:44 GMT</pubDate>
    <dc:creator>hslai</dc:creator>
    <dc:date>2016-08-11T03:58:44Z</dc:date>
    <item>
      <title>Windows 10 Users facing Issues even with ISE 2.0 ( patch 3)</title>
      <link>https://community.cisco.com/t5/network-access-control/windows-10-users-facing-issues-even-with-ise-2-0-patch-3/m-p/3534537#M537989</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are working on a large Wireless deployment with Windows 10 clients and see issues.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 11.0pt; font-family: 'Calibri',sans-serif; color: #1f497d;"&gt;We observed that machines with (build version- 10586 494) were connected &amp;amp; were stable for the whole day.&amp;nbsp; But there were systems which had (build version- of 10240) are facing issue. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 11.0pt; font-family: 'Calibri',sans-serif; color: #1f497d;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 11.0pt; font-family: 'Calibri',sans-serif; color: #1f497d;"&gt;TAC&amp;nbsp; SR # 680752623 is raised , while TAC is suspecting that the &lt;SPAN style="font-size: 11.0pt; font-family: 'Calibri',sans-serif; color: #1f497d;"&gt;CSCuw88770&amp;nbsp; might have regressed.&amp;nbsp; Can anyone from BU confirm on this asap.&lt;/SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Aug 2016 03:08:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/windows-10-users-facing-issues-even-with-ise-2-0-patch-3/m-p/3534537#M537989</guid>
      <dc:creator>Hemant Bharati</dc:creator>
      <dc:date>2016-08-11T03:08:12Z</dc:date>
    </item>
    <item>
      <title>Re: Windows 10 Users facing Issues even with ISE 2.0 ( patch 3)</title>
      <link>https://community.cisco.com/t5/network-access-control/windows-10-users-facing-issues-even-with-ise-2-0-patch-3/m-p/3534538#M537993</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;IMHO that is the reverse of the bug so UNLIKELY the same bug. &lt;SPAN style="font-size: 10pt;"&gt;Please suggest TAC to try recreating it in TAC lab.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Windows 10.0.10240 is the first release of Windows 10 and using TLS 1.0 by default but not TLS 1.2.&lt;/P&gt;&lt;P&gt;Windows 10.0.10586 is the first major update of Windows 10 and using TLS 1.2 by default so this is what CSCuw88770 to address for.&lt;/P&gt;&lt;P&gt;Windows 10.0.14393 is the second major update of Windows 10, just released recently.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The customer should be upgrading 10.0.10240 to 10.0.10586 or 10.0.14393. It may as well be a Windows bug.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Aug 2016 03:58:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/windows-10-users-facing-issues-even-with-ise-2-0-patch-3/m-p/3534538#M537993</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2016-08-11T03:58:44Z</dc:date>
    </item>
  </channel>
</rss>

