<?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: PC windows Slow logon in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/pc-windows-slow-logon/m-p/5306746#M597143</link>
    <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/199513"&gt;@ahollifield&lt;/a&gt;&amp;nbsp;There is not sure for root cause analysis, while we notice bypassing ise the time for windows logon until desktop home screen will spend around 10 sec to 1min averagely, even we have allowed common service related to AD service.&amp;nbsp;&lt;BR /&gt;This behaviour is inconsistency. That's why trying to figure out from related part as AD service, Network level and ISE level.&amp;nbsp; &amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 08 Jul 2025 01:51:18 GMT</pubDate>
    <dc:creator>oum-odom</dc:creator>
    <dc:date>2025-07-08T01:51:18Z</dc:date>
    <item>
      <title>PC windows Slow logon</title>
      <link>https://community.cisco.com/t5/network-access-control/pc-windows-slow-logon/m-p/5306366#M597118</link>
      <description>&lt;P&gt;Hello Cisco ISE lover,&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Currently, I have an inquiry refer to posture process.&amp;nbsp;&lt;BR /&gt;As we have Pending and Complaint status for DOT1x (Supplicant) wired connection.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Base on your experience, does Posture process will cause/delay/slow for window PC logon process?&lt;BR /&gt;What is the ultimate solution to proceed next?&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Thank you,&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 07 Jul 2025 08:07:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/pc-windows-slow-logon/m-p/5306366#M597118</guid>
      <dc:creator>oum-odom</dc:creator>
      <dc:date>2025-07-07T08:07:37Z</dc:date>
    </item>
    <item>
      <title>Re: PC windows Slow logon</title>
      <link>https://community.cisco.com/t5/network-access-control/pc-windows-slow-logon/m-p/5306670#M597132</link>
      <description>&lt;P&gt;Use an MDM instead of ISE Posture. How exactly do you know ISE Posture is causing the slowness though? The ISE Posture module only runs in user space.&lt;/P&gt;</description>
      <pubDate>Mon, 07 Jul 2025 19:59:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/pc-windows-slow-logon/m-p/5306670#M597132</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2025-07-07T19:59:23Z</dc:date>
    </item>
    <item>
      <title>Re: PC windows Slow logon</title>
      <link>https://community.cisco.com/t5/network-access-control/pc-windows-slow-logon/m-p/5306746#M597143</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/199513"&gt;@ahollifield&lt;/a&gt;&amp;nbsp;There is not sure for root cause analysis, while we notice bypassing ise the time for windows logon until desktop home screen will spend around 10 sec to 1min averagely, even we have allowed common service related to AD service.&amp;nbsp;&lt;BR /&gt;This behaviour is inconsistency. That's why trying to figure out from related part as AD service, Network level and ISE level.&amp;nbsp; &amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 08 Jul 2025 01:51:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/pc-windows-slow-logon/m-p/5306746#M597143</guid>
      <dc:creator>oum-odom</dc:creator>
      <dc:date>2025-07-08T01:51:18Z</dc:date>
    </item>
    <item>
      <title>Re: PC windows Slow logon</title>
      <link>https://community.cisco.com/t5/network-access-control/pc-windows-slow-logon/m-p/5306911#M597152</link>
      <description>&lt;P&gt;Yes, the posture process in a dot1x wired setup can contribute to slow Windows logon, especially if network access is delayed while posture validation is still in a &lt;EM&gt;Pending&lt;/EM&gt; state.&lt;/P&gt;&lt;P&gt;To improve this:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;Enable Fast User Logon in Windows Group Policy, so logon isn’t blocked by network readiness.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Use EAP-Chaining (machine + user authentication) to separate posture from the user login process.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Review posture conditions in ISE to ensure they aren't too strict or time-consuming during initial connection.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;These steps usually help reduce logon delays in posture-enabled environments.&lt;/P&gt;</description>
      <pubDate>Tue, 08 Jul 2025 12:19:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/pc-windows-slow-logon/m-p/5306911#M597152</guid>
      <dc:creator>wajidhassan</dc:creator>
      <dc:date>2025-07-08T12:19:48Z</dc:date>
    </item>
    <item>
      <title>Re: PC windows Slow logon</title>
      <link>https://community.cisco.com/t5/network-access-control/pc-windows-slow-logon/m-p/5306922#M597154</link>
      <description>Thanks AI, useless copy/paste response.&lt;BR /&gt;</description>
      <pubDate>Tue, 08 Jul 2025 12:33:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/pc-windows-slow-logon/m-p/5306922#M597154</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2025-07-08T12:33:00Z</dc:date>
    </item>
    <item>
      <title>Re: PC windows Slow logon</title>
      <link>https://community.cisco.com/t5/network-access-control/pc-windows-slow-logon/m-p/5307375#M597172</link>
      <description>&lt;P&gt;Based on my experience it shouldn't really add any noticeable delay because as&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/199513"&gt;@ahollifield&lt;/a&gt;&amp;nbsp;mentioned, the posture assessment will happen after the user has logged in. Now, it's true that right after the login is complete the posture check will start, however, it shouldn't really delay the login process itself, so the user should see their desktop without any delay and then will be subject to the posture check if they will have access to the network or not.&lt;/P&gt;</description>
      <pubDate>Wed, 09 Jul 2025 12:57:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/pc-windows-slow-logon/m-p/5307375#M597172</guid>
      <dc:creator>Aref Alsouqi</dc:creator>
      <dc:date>2025-07-09T12:57:45Z</dc:date>
    </item>
  </channel>
</rss>

