I need to know how to identify when the Windows logon process fini

[Luis R.]

We have some users that begin to load their applications as soon as the
desktop appears, but we know that there are many process that still are
loading, like the antivirus, group policies, network connections and so on.
We have Windows XP PRO SP 2 with Windows 2003 Server as active directory.

I like to ask you about that if there any way to identify when all the
process finished to loaded and then, instruct the users that begin to load
their own applications. For example, if we can show a message that says
something that "now you can begin to work" or something like that.

Thanks in advance for all your help.

Luis R.

 

[R. McCarty]

It's possible, with a Startup Script. I'd probably concentrate my efforts
more on streamlining or tuning the startup cycle. Just curious but why do
you boot the systems ? - couldn't you use Hibernate or Standby to avoid
frequent boots. Do you have an average boot cycle time to report >?

 

[Luis R.]

No, we don't have a boot cycle, it's about the startup process all the
mornings and the users complaint because they begin to start their
applications (like Outlook) before all the logon and OS process finish to
load. Thanks again.

 

[Twayne]

We have some users that begin to load their applications as soon as
the desktop appears, but we know that there are many process that
still are loading, like the antivirus, group policies, network
connections and so on. We have Windows XP PRO SP 2 with Windows 2003
Server as active directory.

I like to ask you about that if there any way to identify when all the
process finished to loaded and then, instruct the users that begin to
load their own applications. For example, if we can show a message
that says something that "now you can begin to work" or something
like that.

Thanks in advance for all your help.

Luis R.

There are various ways, all with differeing levels of effectiveness.

1. Instruct each user to turn on their machine and wait 10 minutes
before they start work. That will surely cover it.

2. Or watch the SystemTray on the right, make a not of how many icons
are in it, and do NOT use the machine until all those icons are present
and accounted for,

3. Or hit CTRL+ALT+Del (or however you'd like to reach the Task
Manager), and do NOT use the machine until the Performance Tab shows,
say, less than 12% cpu occupation over a full 30 second period.

4. Or tell them to use common sense and if everything is sluggish, wait
longer. Continuing to try to work may actually make the overall boot
process even longer than it needs to be.

5. OR use a boot-time Boot Monitor to monitor the bootup, and until it
says it's finished, tell them to leave the machine alone. This has the
advantage of pinpointing any problems that may be developing.

6. OR have someone go around and turn on the machines ten minutes or so
before they come to use them.

7. OR leave the machines turned on all the time. Have t hem go into
Standby or Hibernate after x hours of non use so you'll still save
electricity.

8. OR Leave the machines on all the time and Set the power schemes to
spin down the disks and turn off the monitor after x hours of non use.
To save electricity. BTW, screen savers do NOT protect the monitor, and
they do NOT save any power. In fact, they can increase power
consumption.

You know, I don't really mean to be this sarcastic, but I don't think
I've ever seen this question asked before. I just can't imagine a group
of people who are either so ignorant, phobic, or plain old egotistical
as to not quickly learn that it takes 2 to 5 minutes for their machines
to boot before they'll work at full capacity, period, end of story. I
don't envy you, assuming this is a real question/concern.

HTH,

Twayne