I'm using MDT 2013 to deploy a Windows 8.1 Update 1 image, and I have a step that runs for a long time, particularly on older hardware. Prior to the long step running I'm using a Powershell script to modify the following reg keys to disable the screen saver for the logged on user (Administrator, as that's what LiteTouch runs under):
Set-ItemProperty -Path "HKCU:\Control Panel\Desktop" -Name ScreenSaveActive -Value "0" Set-ItemProperty -Path "HKCU:\Control Panel\Desktop" -Name ScreenSaverIsSecure -Value "0" Remove-ItemProperty -Path "HKCU:\Control Panel\Desktop" -name SCRNSAVE.EXE So, Disable Screensaver with Powershell-->TS step to reboot system-->Run Long Step. I've confirmed that the registry keys are set/deleted as per above, and the system GUI also reports that no screensaver is set during the long step. Yet, when the long task sequence step runs, the screensaver engages and requires a password to unlock. Any thoughts on how to prevent that or what I'm possibly missing? Thanks! --Dave ________________________________ This e-mail may contain Sprint proprietary information intended for the sole use of the recipient(s). Any use by others is prohibited. If you are not the intended recipient, please contact the sender and delete all copies of the message.
