Workstation Uptime Reboot
Product Name: Workstation Uptime Reboot
Description : This monitor set reads the “System Up time” performance counter – once the counter goes above 604800 seconds(7 days), a procedure is triggered as a response. This procedure has a simple workflow of checking user status, if logged in they will be notified and asked to reboot, if not logged in a reboot will be automatically performed. Whichever workflow occurs the step will be logged for reporting purposes. If the user delays or selects no, the procedure will run itself every 30 minutes until the reboot has occurred. Additional alarms will be ignored for 7 days as a cool down to avoid double scheduling from the monitor set.
Instructions :
please see attached PDF for install instructions
Comments
-
Not importing into my VSA for some reason.
0 -
Same, I am unable to import this script.
0 -
You need to do it from System>>Server Management>>Import Center.
1 -
Do you have the monitor set included on the zip file?
0 -
Could you elaborate a bit further on what you mean?
0 -
After unzipping the files and reading the instructions inside, it says to upload the xml file for monitor set. It is not included on the zip file
0 -
Hi @Adrian Vicencio I am the creator of this procedure, I checked the ZIP contents in the download and the XML appears to be there, I am not sure whats happening when you are downloading and opening the file, can you try re-downloading. If it doesn't show up in the zip it is possible some other solution perhaps doesn't like the XML and is quarantining it?
Thanks
0 -
Hey Brian
Like the others have commented. I import and it doesn't error or anything, just doesn't show in the list.
0 -
Hello @Brian Honeycutt,
I can extract the zip file and can see the PDF and XML file and even after a successful import, the agent procedure doesn't show up in the list.
Best,
Averill
0 -
@Averill Singh you cannot import this procedure directly under agent procedures. As mentioned in an earlier comment, you must import the script under System->Server Management->Import Center. The reason why is because it uploads a monitor set and a procedure.
Thanks
0 -
When trying to do this, it still fails. It imports as a report and does not split into 2 separate things as you state.
0 -
This procedure is awesome and well designed. for those that cannot import please follow these instructions on your kaseya portal go to System->Server Management->Import Center its the only way it will work
regarding the script itself I found a flaw to it as windows fastboot reports wrong data, as not all the shutdowns are counted.
looking to get around this by tracking an eventid on eventvwr
apart from this awesome idea
0 -
This procedure is awesome and well designed. for those that cannot import please follow these instructions on your kaseya portal go to System->Server Management->Import Center its the only way it will work
regarding the script itself I found a flaw to it as windows fastboot reports wrong data, as not all the shutdowns are counted.
looking to get around this by tracking an eventid on eventvwr
apart from this awesome idea
0 -
Are you talking about fast startup ✔️ under the power options systems settings?
0
