Did you try to disable the l3 swiss delay and reduce some the timers...httpa discovery etc.
Also there is a bug in the current compliance modulr where the current wsc.dat files causes long posture time. You can delete this file from the nac agent directory and see if these suggestions help.
Sent from Cisco Technical Support Android App
I have disabled the l3 swiss delay, reduced timers & removed the compliance module from client provisiong policy but no luck still it is taking time. Any other suggestion please.
Usually how much time nac agent takes to come up?
You maybe hitting bug CSCub80143
Please rate if it helps
That is what i initially suggested, doesnt look like that fixed their issue.
*Please rate helpful posts*
I'm facing the same issue with ISE 1.1.1 (268) with Agent 188.8.131.52 for Windows XP clients. I have already configured "yes" to disabled the l3 swiss delay and reduced the httpa discovery timer from 30 to 05 sec but still clients get aprox 2.30 minutes to popup and finished the posture discovery.
Can you please advise if this is the minimum time or what is the minimum time and what are the parameters to set to a minimum time to complete agent popup and posture discovery..?
Is there any option that we can run this on backgroup..?
thanks in advance..
Can you please provide the acl configuration for the "agent redirect" scenario as well. Also when you use wireshark do you see communication to the ISE PSN during the delay?
I have verified that the nac agent service will not start till the netlogon process completes, you most likely will see this when a machine is locked and unlocked. You many need to consider opening AD ports and that will speed up the communication.
Sent from Cisco Technical Support iPad App
Please I have the same problem
what are the parameters to set to a minimum time to complete agent popup and posture discovery.