Jump to content

Recommended Posts

Posted

Hi,

 

Our external provider made a shutdown script and it reboots after 10 mins of logging on but only once in the morning.

 

They have removed the script yet it still does it (script cant be found anywhere on the pc)

 

Do any of you lot know what may be causing it?

Posted
Disconnect a PC from network after startup and see if it does it. If it does then disconnect from network before you start it up and see what happens. Does it specifically reboot after log in or jus PC starting up, if it only does it when logged on not sure why it would be set up like that.
Posted (edited)

Is the reason for the removal of the task the 10 minute reboot? I'm not sure a shutdown task would do that (reboot).... what makes you think it is the culprit (no other changes and started doing it directly after the task was applied etc.)?

 

Probably not much help (possibly not even the issue you have), but for future reference the only reason I've known a shutdown scheduled task to do something similar (although it was actually shutdown, not reboot) is because 'Run task as soon as possible after a scheduled start is missed' was ticked...

 

If the computer is not on when the scheduled task is supposed to run (and you don't have it set to wake before the task runs), it will run 'as soon as possible' after it is turned on again.

 

Ask me how I know...

 

EDIT: Just as an extra thing to look at, I just ran the Powershell command 'Get-ScheduledTask' on my server and it didn't even list all the manually/GPO added tasks, only the Windows/Microsoft ones.

Edited by Koldov
Posted

What i did, i logged onto a pc that was off and looked at running tasks in task scheduler and we have a CSP Reboot one and then it rebooted

 

but no one knows where it came from :D

 

so i've asked for it to be removed

 

Is the reason for the removal of the task the 10 minute reboot? I'm not sure a shutdown task would do that (reboot).... what makes you think it is the culprit (no other changes and started doing it directly after the task was applied etc.)?

 

Probably not much help (possibly not even the issue you have), but for future reference the only reason I've known a shutdown scheduled task to do something similar (although it was actually shutdown, not reboot) is because 'Run task as soon as possible after a scheduled start is missed' was ticked...

 

If the computer is not on when the scheduled task is supposed to run (and you don't have it set to wake before the task runs), it will run 'as soon as possible' after it is turned on again.

 

Ask me how I know...

 

EDIT: Just as an extra thing to look at, I just ran the Powershell command 'Get-ScheduledTask' on my server and it didn't even list all the manually/GPO added tasks, only the Windows/Microsoft ones.

 

- - - Updated - - -

 

What i did, i logged onto a pc that was off and looked at running tasks in task scheduler and we have a CSP Reboot one and then it rebooted

 

but no one knows where it came from :D

 

so i've asked for it to be removed

 

Is the reason for the removal of the task the 10 minute reboot? I'm not sure a shutdown task would do that (reboot).... what makes you think it is the culprit (no other changes and started doing it directly after the task was applied etc.)?

 

Probably not much help (possibly not even the issue you have), but for future reference the only reason I've known a shutdown scheduled task to do something similar (although it was actually shutdown, not reboot) is because 'Run task as soon as possible after a scheduled start is missed' was ticked...

 

If the computer is not on when the scheduled task is supposed to run (and you don't have it set to wake before the task runs), it will run 'as soon as possible' after it is turned on again.

 

Ask me how I know...

 

EDIT: Just as an extra thing to look at, I just ran the Powershell command 'Get-ScheduledTask' on my server and it didn't even list all the manually/GPO added tasks, only the Windows/Microsoft ones.

Posted
It might be worth checking where the file it ran (if it ran one). We set up something similar but the file would be replaced nightly for those users that did not want their PCs rebooted and removed the schedule.
Posted

I can't remember top of my head where it ran

 

but our IT Support company is looking into removing it but its weird as it says it hasn't run when i saw it running :confused:

 

i've posted a screenshot below

GetAttachmentThumbnail?id=AAMkADU4YzlhNWViLTUxNmYtNDAzNi1iNTY5LTRhZDZhMDQxN2FhMQBGAAAAAACOsVMQvQfbT78KwXH0B6FFBwDKimATY8hETYrWPQbo8eTRAAAAAAEJAADKimATY8hETYrWPQbo8eTRAAEVLimSAAABEgAQAEHDHNX9gOpGvSA3EjiKqwU%3D&thumbnailType=2&token=eyJhbGciOiJSUzI1NiIsImtpZCI6IjczRkI5QkJFRjYzNjc4RDRGN0U4NEI0NDBCQUJCMTJBMzM5RDlGOTgiLCJ0eXAiOiJKV1QiLCJ4NXQiOiJjX3VidnZZMmVOVDM2RXRFQzZ1eEtqT2RuNWcifQ.eyJvcmlnaW4iOiJodHRwczovL291dGxvb2sub2ZmaWNlLmNvbSIsInVjIjoiOWY2ZmZkNGUxMGI0NGRjNGI4Y2VlZTczZGJmNjM5MjkiLCJ2ZXIiOiJFeGNoYW5nZS5DYWxsYmFjay5WMSIsImFwcGN0eHNlbmRlciI6Ik93YURvd25sb2FkQDkyOTljNmUzLTQ1NGItNDAxNC05MTkzLTViZDc4OGM2YmNmYSIsImlzc3JpbmciOiJXVyIsImFwcGN0eCI6IntcIm1zZXhjaHByb3RcIjpcIm93YVwiLFwicHVpZFwiOlwiMTE1MzgwMTEyMjg1NTM5NTIyN1wiLFwic2NvcGVcIjpcIk93YURvd25sb2FkXCIsXCJvaWRcIjpcImVlODdjOTYxLWRjNmQtNGI5YS05ZTMyLWZmNDFmNWU5ZDBlYVwiLFwicHJpbWFyeXNpZFwiOlwiUy0xLTUtMjEtMzUyMTUxNDc3Mi0zMDg4NzU5OTAxLTEzMzk3ODU4NTktMzAwMzE0NTBcIn0iLCJuYmYiOjE3MDA1ODM5NTIsImV4cCI6MTcwMDU4NDU1MiwiaXNzIjoiMDAwMDAwMDItMDAwMC0wZmYxLWNlMDAtMDAwMDAwMDAwMDAwQDkyOTljNmUzLTQ1NGItNDAxNC05MTkzLTViZDc4OGM2YmNmYSIsImF1ZCI6IjAwMDAwMDAyLTAwMDAtMGZmMS1jZTAwLTAwMDAwMDAwMDAwMC9hdHRhY2htZW50cy5vZmZpY2UubmV0QDkyOTljNmUzLTQ1NGItNDAxNC05MTkzLTViZDc4OGM2YmNmYSIsImhhcHAiOiJvd2EifQ.TFqCp-C80GWWtYrl9ufphZew293rZGMRIbwQMb3mUT2Pi58mJ0f6zGs0vB0JmeOMH3sh_DzDMbTiyABVuS3aUDulxRDFI4YxGvwvdF95xxz2Dz4A74ImSRjP0eu7Dcrt0cLCWd10ELwQ2D7b3Of8Z1xcaWcauW9gROASZ3doxXrXF12VmgTj_bh8Gkp6lMqHp9jL8L2dPWHCRGk6y0nCrvZUzvHQ2itpqE6s72zOKMKQM8wpmKQUu6LBMieUq-s144lGhFhmtM0wTA5bUy1vYpkpErk9Q_w3FXSDNCVvJuFKj4sGDCHO-lG1V3Y8h6SdlYoO5QYAJ-6ImgWGJRFOHQ&X-OWA-CANARY=X-OWA-CANARY_cookie_is_null_or_empty&owa=outlook.office.com&scriptVer=20231110003.11&animation=true&persistenceId=b2cbd414-1184-4e8d-9970-6ea046537cc7

  • 3 weeks later...
Posted
You can check the Task Scheduler for any scheduled tasks related to the reboot. You can also review Group Policy settings that might affect system reboots. Additionally, ensure that there are no lingering remnants of the shutdown script in the registry or other system files.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...