Can i lock keyboard and mouse after userlogin for a timeperiod?

[Darkness]

Can i lock keyboard and mouse after userlogin for a timeperiod?
For example for 10 second, so the scripts can pass, before user can
start programms?
Any idea would be nice

 

[Herb Martin]

Can i lock keyboard and mouse after userlogin for a timeperiod?
For example for 10 second, so the scripts can pass, before user can
start programms?
Any idea would be nice

What are you running? Normally the computer startup
GPO and scripts, as well as the User logon and scripts
complete before logon is allowed.

 

[Darkness]

Well, they need so long. There are still running scriptswhile the user
is already logged on.
Maybe because the comps are so slow partially or its the network.
Anyways sometimes the user cna see them on some machines. Is there any
posibility to pass them before user can touch them? Nope they cant be
made smaller On faster machines its no prob on slower ones it
sometime is.

 

[Herb Martin]

Well, they need so long. There are still running scriptswhile the user
is already logged on.
Maybe because the comps are so slow partially or its the network.
Anyways sometimes the user cna see them on some machines. Is there any
posibility to pass them before user can touch them? Nope they cant be
made smaller On faster machines its no prob on slower ones it
sometime is.

The default per GPO is supposed to be 10 minutes
(600 seconds) so if they are being allowed to logon
perhaps that setting has been changed AND/OR
the processing has been changed from Synchronous
(should be SEQUENTIAL) to ASynchronous (should
be called PARALLEL or CONCURRENT) processing.

 

[Darkness]

600 sec for login? It is going much faster than that. here must be some
sort of misunderstanding.

 

[Herb Martin]

600 sec for login? It is going much faster than that. here must be some
sort of misunderstanding.

Perhaps.

At Startup of a COMPUTER, the computer finishes
most services and gets on the network authenticating
itself before it downloads it's own Group Policy
Objects (GPOs). These can include scripts.

By default each GPO and script must complete within
600 seconds.

Once the Computer finishes logon, the user may logon
and (again) the GPOs for the user are downloaded and
each can run up to 600 seconds.

These numbers, and the sequential nature can be changed.

What are you referencing when you referred to delaying
logon for scripts?

 

[Darkness]

yes, the problem is that the user can shutdown the window with running
scripts or start applications before the scripts run through, what
cause errors. What i am asking for is to make it impossible for teh
user do act before the scripts are over. There are scripts when
computer enters the domain and some special for each group of users
when they log on.
The special ones for each group tends to run too long, so users can
interfere with them with too early clicks on applications. Hope thsi
describe it better.

 

[Darkness]

yes, the problem is that the user can shutdown the window with running
scripts or start applications before the scripts run through, what
cause errors. What i am asking for is to make it impossible for teh
user do act before the scripts are over. There are scripts when
computer enters the domain and some special for each group of users
when they log on.
The special ones for each group tends to run too long, so users can
interfere with them with too early clicks on applications. Hope thsi
describe it better.

 

[Tim.Olsen]

Darkness,

I suppose you could, at the beginning of your script, use devcon.exe to
disable the keyboard/mouse devices, then at the end of the script, use
devcon to re-enable it.
Of course if the script fails anywhere inbetween your user is ...um...
not in a good place.
Perhaps as a fail safe, have a startup script re-enable the devices. So
worst case the user can fix it with a reboot --fixed of course, until
the logon script runs again.

Forgive me for not testing it first.

Regards
Tim.Olsen

 

[Herb Martin]

In addition to Tim's idea you might also spawn
some of this off in hidden windows or run them
in some other background or hidden manner.

 

[Jerold Schulman]

yes, the problem is that the user can shutdown the window with running
scripts or start applications before the scripts run through, what
cause errors. What i am asking for is to make it impossible for teh
user do act before the scripts are over. There are scripts when
computer enters the domain and some special for each group of users
when they log on.
The special ones for each group tends to run too long, so users can
interfere with them with too early clicks on applications. Hope thsi
describe it better.

See tip 4133 » The 'Run logon scripts synchronously' policy does NOT work in Windows XP?
and link in the 'Tips & Tricks' at http://www.jsifaq.com

Jerold Schulman
Windows Server MVP
JSI, Inc.
http://www.jsiinc.com
http://www.jsifaq.com

 

[Darkness]

will check this