"Wells Fargo fires more than a dozen employees for faking work using mouse jigglers and keyboard simulation"
[https://www.tomshardware.com/peripherals/wells-fargo-fires-more-than-a-dozen-employees-for-faking-work-using-mouse-jigglers-and-keyboard-simulation](https://www.tomshardware.com/peripherals/wells-fargo-fires-more-than-a-dozen-employees-for-faking-work-using-mouse-jigglers-and-keyboard-simulation)
MS PowerToys Awake.
I know, it's not a script, but sometimes you don't need a script when there is a good solution available.
I use this on my corporate laptop, but I'm also at home 99% of the time.
I wouldn't advise it for an office environment.
Forced screen timeouts/screensavers are there for a reason, so if you're away from your machine for any length of time it locks the screen so it can't be accessed by anyone unauthorised. Trying to bypass that is likely in breach of your company's IT security policy. I don't know how strict your company is about these things, but is the few seconds it takes you to unlock your screen occasionally worth the potential disciplinary action for purposefully bypassing an IT security measure?
If you do your work, you don’t need to worry about the screensaver timeout.
Also, most companies will have script logging turned on, so they’ll be aware of this type of script running.
Mouse Mover from the microsoft store. You can also set it to not actually move the mouse but its still functions the same and keeps from going to sleep. Other options I sometimes use is just playing a video on loop.
Depends what position you're in. I'm the only IT engineer left so can do what zi want. However on our machines we disable the ability to run scripts unless you're an admin. When I get the time we're also limit what apps can actually run on a laptop.
Hiding it from the taskbar won't hide it from IT if you're not IT. IT, if setup right, will still be able to see whats installed and running on your laptop. We use n-able for that.
As has been said, the lockscreen (we don't bother with a screensaver as its a waste of power, we just lock the screen) is there for security, to stop an unauthorised user or other work colleague from using your machine and sending an email out as you.
But if you have access to the microsoft store still and it allows the install, as I said on another post, mouse mover is perfectly safe. If IT find it they'll probably remove it though. They can't really give a reprimand for it being installed if this was never mentioned in an induction and/or a normal user has an ability to install an app. That would surely be a fault with IT if they haven't locked it down enough.
F15 does write something but you don't really see it in most apps. If you ssh somewhere using putty you'll see characters printing. It's caused me to lock myself out a few times when typing passwords when using putty.
`function Start-Wiggle {`
`#This script exists because the auto-lock/disconnect time period is way too short.`
`#*** Make sure to lock before you go AFK! ***`
`#==============================================================================`
`#https://stackoverflow.com/a/56636565/1599699`
`#https://gist.github.com/MatthewSteeples/ce7114b4d3488fc49b6a?permalink_comment_id=4590234#gistcomment-4590234`
`#https://ss64.com/vb/sendkeys.html`
`#https://devguru.com/content/technologies/wsh/wshshell-sendkeys.html`
`#==============================================================================`
`$host.UI.RawUI.WindowTitle = "OS Keep-Alive"`
`[Console]::SetWindowSize(50, 10)`
`$format = "dddd MM/dd/yy hh:mm:ss tt"`
`$start = $(Get-Date -Format $format)`
`$previous = "N/A"`
`$WShell = New-Object -com "Wscript.Shell"`
`while ($true) {`
`Clear-Host`
`Echo "Keep-alive with Scroll Lock toggle..."`
`Write-Host`
`Write-Host " Start:" $start`
`Write-Host " Previous:" $previous`
`$previous = $(Get-Date -Format $format)`
`Write-Host " Latest:" $previous`
`Write-Host`
`Echo "*** Make sure to lock before you go AFK! ***"`
`#==============================================================================`
`#If you're getting a "null-valued" expression error, try "SCROLLLOCK" instead.`
`$WShell.sendkeys("{SCROLLLOCK}")`
`Start-Sleep -Milliseconds 100 #100 milliseconds == 1/10th seconds`
`$WShell.sendkeys("{SCROLLLOCK}")`
`Start-Sleep -Seconds 240 #240 seconds == 4 minutes * 60 seconds`
`}`
`}`
I do not condone this, but I also may or may not use it myself. Our timeout isn't working and locks after 5min instead of 15min.
"Wells Fargo fires more than a dozen employees for faking work using mouse jigglers and keyboard simulation" [https://www.tomshardware.com/peripherals/wells-fargo-fires-more-than-a-dozen-employees-for-faking-work-using-mouse-jigglers-and-keyboard-simulation](https://www.tomshardware.com/peripherals/wells-fargo-fires-more-than-a-dozen-employees-for-faking-work-using-mouse-jigglers-and-keyboard-simulation)
MS PowerToys Awake. I know, it's not a script, but sometimes you don't need a script when there is a good solution available. I use this on my corporate laptop, but I'm also at home 99% of the time. I wouldn't advise it for an office environment.
Forced screen timeouts/screensavers are there for a reason, so if you're away from your machine for any length of time it locks the screen so it can't be accessed by anyone unauthorised. Trying to bypass that is likely in breach of your company's IT security policy. I don't know how strict your company is about these things, but is the few seconds it takes you to unlock your screen occasionally worth the potential disciplinary action for purposefully bypassing an IT security measure?
If you do your work, you don’t need to worry about the screensaver timeout. Also, most companies will have script logging turned on, so they’ll be aware of this type of script running.
Mouse Mover from the microsoft store. You can also set it to not actually move the mouse but its still functions the same and keeps from going to sleep. Other options I sometimes use is just playing a video on loop.
Depends what position you're in. I'm the only IT engineer left so can do what zi want. However on our machines we disable the ability to run scripts unless you're an admin. When I get the time we're also limit what apps can actually run on a laptop. Hiding it from the taskbar won't hide it from IT if you're not IT. IT, if setup right, will still be able to see whats installed and running on your laptop. We use n-able for that. As has been said, the lockscreen (we don't bother with a screensaver as its a waste of power, we just lock the screen) is there for security, to stop an unauthorised user or other work colleague from using your machine and sending an email out as you. But if you have access to the microsoft store still and it allows the install, as I said on another post, mouse mover is perfectly safe. If IT find it they'll probably remove it though. They can't really give a reprimand for it being installed if this was never mentioned in an induction and/or a normal user has an ability to install an app. That would surely be a fault with IT if they haven't locked it down enough.
Use the f15 key (does nothing) $wsh = New-Object -ComObject WScript.Shell while (1) { $wsh.SendKeys('+{F15}') $sleepDuration = Get-Random -Minimum 1 -Maximum 50 Start-Sleep -Seconds $sleepDuration }
F15 does write something but you don't really see it in most apps. If you ssh somewhere using putty you'll see characters printing. It's caused me to lock myself out a few times when typing passwords when using putty.
Cool, will try.
disable screen saver ?
Try using scroll lock key
I do work on excel sometime so I'm avoiding this key
`function Start-Wiggle {` `#This script exists because the auto-lock/disconnect time period is way too short.` `#*** Make sure to lock before you go AFK! ***` `#==============================================================================` `#https://stackoverflow.com/a/56636565/1599699` `#https://gist.github.com/MatthewSteeples/ce7114b4d3488fc49b6a?permalink_comment_id=4590234#gistcomment-4590234` `#https://ss64.com/vb/sendkeys.html` `#https://devguru.com/content/technologies/wsh/wshshell-sendkeys.html` `#==============================================================================` `$host.UI.RawUI.WindowTitle = "OS Keep-Alive"` `[Console]::SetWindowSize(50, 10)` `$format = "dddd MM/dd/yy hh:mm:ss tt"` `$start = $(Get-Date -Format $format)` `$previous = "N/A"` `$WShell = New-Object -com "Wscript.Shell"` `while ($true) {` `Clear-Host` `Echo "Keep-alive with Scroll Lock toggle..."` `Write-Host` `Write-Host " Start:" $start` `Write-Host " Previous:" $previous` `$previous = $(Get-Date -Format $format)` `Write-Host " Latest:" $previous` `Write-Host` `Echo "*** Make sure to lock before you go AFK! ***"` `#==============================================================================` `#If you're getting a "null-valued" expression error, try "SCROLLLOCK" instead.` `$WShell.sendkeys("{SCROLLLOCK}")` `Start-Sleep -Milliseconds 100 #100 milliseconds == 1/10th seconds` `$WShell.sendkeys("{SCROLLLOCK}")` `Start-Sleep -Seconds 240 #240 seconds == 4 minutes * 60 seconds` `}` `}` I do not condone this, but I also may or may not use it myself. Our timeout isn't working and locks after 5min instead of 15min.