I attempted to prevent mouclass.sys, mouhid.sys, kbdclass.sys and kbdhid.sys from starting under HKLM\SYSTEM\CurrentControlSet\Services but it doesn't seem to work very well.

Do you perform workstation installations on users place? How you prevent users logging on to their computer during image deployment?

If this is to stop users from logging in when the workstation is being deployed, why not try a different approach. In all your base images set the login background to display a warning that the workstation is currently being deployed. This can be configured with the following registry key:

HKEY USERS\ .DEFAULT\Control Panel\Desktop

Then when the deployment is complete, you can reset and on your final reboot all will be well.

Its a softer approach than a full device lock, but its less likely to cause grief and further it won't prevent you from troubleshooting.... ;-)

Kind Regards,
Ian./
 

Hi Ian,

Thanks for your reply.

Actually, I have implemented that registry value and warning background image on image. I also have Run Script task, which will disable that wallpaper in the end of deployment job.

You're right, that's softer approach but there are many knucklehead users in our environment who will ignore that warning text :)

That's why I would like to block all keyboard & mouse input via registry, script or executable until deployment job is completed.

What about changing the Ctrl + Alt + Del window instead of the background?

http://windowsitpro.com/article/articleid/26848/change-the-windows-logon-screen.html

Hi bhawver,

That's very cool feature, but it was not what I was looking for.

I'm trying to prevent user from logging on to system, not make Windows Logon window look cool

Try to simply lock the live session sending a script as described in the following post:
Lock Workstation During Installation and Deployment

In any case could be interesting add in this script a command to disable also keyboard / mouse.

regards,
Paolo

Hi riva11,

I don't need to lock workstations, because computers are already in Windows Logon screen, while they're running software installations, which belong to deployment job. Good idea, though.

Thank you Ian.

Your solution was simply the best and easiest way to accomplish this.

Thank you all.