I am using 6.5R3. Found that Host Checker took very long time, 3-4 minutes before moving to welcome page. I did evaluate 4 policies with HC. However, though I checked with only one policy but still that it took very long time to finish. Any one experienced the same?
What type of policies are you using? If you are using EES (the new malware detection) or checking patches, these will add time to the login process for Host Checker. When you did your single HC policy test, what was the one policy you used? Do the other policies show the same delay when used alone?
@zanyterp wrote:That is correct; there was a change made in 6.5 for when the JuniperSetupClient was pushed out to users; the 30-second delay was done to allow users time to see the ActiveX prompt and accept it and if they did not then push out the Java applet.
Is it possible to reduce this delay ?
Unfortunately when using IE there is not; it is built-in to the login launch sequence. If users connect from non-Windows machines or browsers that do not use ActiveX, the delay should be minimal (or not visible at all).
Thanks a lot. I did not use ESS but evaluated policies for registry keys checking, patches checking, antivirus and its virus def checking. However, when I disable the other policies and remained only one registry key value to check but still that it took 2-3 minutes to complete the HC process. Is it normal or anything else I can improve? Kindly advise.
Thanks for all the explanations. I tested all our 4500s via Firefox and we are back to normal.
You are welcome; glad to help out.
The patches checking and EES are the only ones I would expect to take that amount of time to complete; I have not yet seen a registry check require that much time. Do you mind sharing the value you are checking and I can try in my lab to see if I see the same delay on that key?
Other than the patch check, do the other policies show quick login time when used alone? Does the browser used show difference in behavior?
You are welcome; glad to hear it is working for you again successfully with Firefox.
I did test with only one policy by evaluating key HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\DefaultDomainName and found that it took long time before moving to welcome page. For other policies, still do not test it one by one yet.
Thank you for the information; I am sorry to hear that that is slow for you. I have not had any delay with testing that key; do you have many domains listed?
I think that the best option, now , will be to open a JTAC case and work with them to further investigate on slowness.
Does your debuglog.log show a delay when evaluating?