Pending Reboot Check
KASEYAN
Product Name: Pending Reboot Check
Version: 1.0
Description : This agent procedure populates a custom field in the Audit module called Reboot Status with the result of the pending reboot check.You will need to create a custom field called Reboot Status BEFORE importing the Agent Procedure. This Agent Procedure works for Windows only and uses a PowerShell Module that it imports it from the Microsoft PowerShell Gallery automatically. The Agent Procedure will install NuGet and the PendingReboot PowerShell module by Brian Wilhite, a Microsoft Employee. You can find more information in the documentation and here: https://www.powershellgallery.com/packages/PendingReboot/0.9.0.6
IMPORTANT: THIS AGENT PROCEDURE CHECKS IF THE OS NEEDS A REBOOT, IT DOESN'T CHECK IF VSA REQUIRES THE OS TO REBOOT YET.
Instructions :
This Agent Procedure requires that you create a Custom Field in the Audit Module called Reboot Status of type String. You can create Custom Fields in the Audit module by going to:
VSA > Audit > View Individual Data > Machine Summary
After you create the field, import the Agent Procedure and execute it against your endpoints. After the Agent Procedure runs, it will populate the Custom Field with the status.
To import the Agent Procedure go to:
VSA > Agent Procedures > Schedule / Create
Next, select any folder which you have rights to add Agent Procedures to and right click on it.
Select Import Folder/Procedure and upload the extracted XML file provided in the zip file you downloaded from the Automation Exchange.
IMPORTANT: THIS AGENT PROCEDURE CHECKS IF THE OS NEEDS A REBOOT, IT DOESN'T CHECK IF VSA REQUIRES THE OS TO REBOOT YET.
Comments
-
On some servers, I was getting stuck on step 22. When manually running the command, I was getting the error "Unable to download from URI". Found possible resolution on this page:
I changed line 22 to '[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12; Install-PackageProvider -Name NuGet -MinimumVersion 2.8.5.201 -Force' and it looks like the script completed successfully after this change. Thought I would post in case someone else runs in to any problems running this script.
0 -
Getting "File was not uploaded due to incorrectly formatted XML.Please export the content to a new XML file and try again" when trying to use the Import Center as well as "Please pick a script export file or paste a script" when using the Import Folder/Procedure in Agent Procedures. Pasting the script in the Import Folder/Procedure in Agent Procedures will result in a window that says "You're trying to decode an invalid JSON String: Sorry, you have been blocked. You are unable to access kaseya.net".
0
