Task sequence to install software while machine is in logged off state
Hi Guys ,
I have a requirement to set up a solution that prevents users from logging in to a workstation while it is logged off and installing software. Not all software we install like this , this is just for a few that can only be installed in log off state. The issue we have is currently some users are logging in and interrupting installations. I am putting together a task sequence that runs (once machine is logged off) as follows
1. Replaces the standard log on screen with a background message that mentions sotware is installing.
2.Lock keyboard and mouse
3. Run installation
4.Restore standard logon screen
5.Restore keyboard and mouse functionality
6.Restore the standard logon screen once installation ends.
I have background , installation commands but I cannot seem to figure out how to hide the the standard log on screen? . Can anyone assist/advice or point me to a script that can address this? Many thanks in advance
Please log in to answer
Posted by: sparky86 4 years ago
the login screen can be handled by setting the OEM background
and drop the image into
you can have the task sequence rename the existing one (if used) copy in the new wallpaper then once finished delete the replacement wallpaper and rename the old one back
however this wallpaper is only refreshed during a log off/lock cycle
regarding the keyboard and mouse you can install the driver toolkit and acquire devcon and use that to disable the keyboard and mouse, and re-enable it that way.
Posted by: rileyz 4 years ago
This is going to be ugly, but it will probably work. What you need to do is find the key that corresponds to this GPO setting.
I take the install will only run when no one is logged on, so that's good. As part of that process write the registry key which will disable interactive logon, this should stop people..logging on. Once its all done, remove the key. Watch out GPO dosent blast the key out if its set at Domain level.
Use a tool like RegShot to find the Registry Policy key, or you can just do a compare with a registry export with Notepad++ etc.