/build/static/layout/Breadcrumb_cap_w.png

How long should DA run at login?

How long should it take Desktop Authority to run during the login process.  We are using DA version 8.  The trace log starts about thirty seconds after I click "OK" to log in.  The trace log shows about 20-30+ seconds of activity.  Are these numbers normal?


2 Comments   [ + ] Show comments
  • My sltrace.htm files vary from 8 seconds to 2 minutes. The 2 minute ones are on wireless laptops that have just been booted and are downloading patches and installing apps as part of the computer elements - the students call it the "black screen of death" where it sits at a blank black screen for a minute or two.

    I'm not so sure the trace log times are accurate. I have trouble believing that dozens of actions can happen in the same second on some of our older computers but it is hard to differentiate the normal windows stuff from the DA "Computer management" stuff from the DA "login" stuff.

    You should definitely look in the log for large delays (shown as red text) - we recently had a problem where our 2003 print server couldn't offer x64 print drivers and the laptops were attempting to go out to Windows Update to find them, causing a multi-minute delay.

    If you have Computer management items enabled that will slow down the login process also as they are still running unless the computer has been sitting for a long period of time. - mbutler522010 10 years ago
  • Don't forget about duplicate Group Policies you might be applying. Ones from GPMC, and also any you have running in DA. Any roaming profiles? Any copying of large amounts of files using DA? Also, I know this sounds like a canned response, I would update to the latest version. We constantly add fixes to newer versions. Also in the future explain in detail all the systems and OS's in detail. - JMorano 10 years ago

Answers (1)

Posted by: scriptlogic.de 10 years ago
Yellow Belt
0

Hi,

 

we have experience with more than 100 installition in Germany, Austria and Switzerland. The benchmark is:

- less than 15 seconds on a fat client (better is less than 10 seconds)

- less than 10 seconds on a WTS- or Citrix-Client

Check the Trace-file to find the time consuming part of the prozedure.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ