Core.4 Other Tools and Utility Procedures

Core.4 Other Tools and Utility Procedures.AntiVirus

• EICAR Virus Test
  • Creates a file in the Agent Working Directory that contains the EICAR test virus pattern. This agent procedure can be used to verify that any antivirus software is working on a machine. NOTE: This is not a real virus and poses no potential risk. For more information, see http://eicar.org.
• Run a Malicious Software Removal Tool Full Scan-Clean
  • Uses MRT (Microsoft Malicious Software Removal Tool) to perform a full scan and clean. Results of the operation are logged to an MRT.LOG file and to the agent procedure log. The log file is retrieved to the systems GetFile folder.

Core.4 Other Tools and Utility Procedures.AntiVirus.Defender

• Windows Defender - Full System Scan
  • Run a Windows Defender Full System Scan
• Windows Defender - Quick System Scan
  • Run a Windows Defender Quick System Scan
• Windows Defender - Signature Update
  • Run a Windows Defender Signature Update

Core.4 Other Tools and Utility Procedures.AutoAdminLogon

• Disable AutoAdminLogon
  • Disables any previously enabled AutoAdminLogon configuration on a Windows machine.
• Enable AutoAdminLogon with AUTOLOGON
  • Enables AutoAdminLogon with secure password encryption using SysInternals AutoLogon utility. This Agent Procedure only works on 32bit versions of Windows.XP or later.
• Enable AutoAdminLogon with Cleat Text Method
  • Prompts for the username and password to be used for AutoAdminLogin and then enables the clear text AutoAdminLogon configuration on a Windows machine using those supplied credentials.

Core.4 Other Tools and Utility Procedures.Kaseya Agent Management

• Agent - Force Check-in
  • This is the world's shortest procedure. This procedure has no steps at all. Its sole job is to force the agent to check in with the KServer. Use Force Check-in to determine if an agent is online or not.
• Agent - Remove Kaseya from Start Menu and Add-Remove Programs
  • Remove the Agent folder from the Start Menu. Hide the System Tray Icon (blue K) by disabling the Agent Menu (Agent Tab - Agent Menu). Run this script on machines you do not want to give anyone the ability to uninstall, exit, or stop the Agent.
• Agent - Reset Audit Cache
  • Deletes the cached audit results file saved by the agent. Run this procedure to reset all application results from an audit and start over.
• Agent - Terminate Remote Control Sessions
  • This script Terminates all Remote Control sessions that Kaseya Supports within the Remote Control function of The VSA (K-VNC, WinVNC, Terminal Services, FTP, RAdmin and pcAnyWhere).
• VNC - Hide System Tray Icon
  • Disables the VNC system tray icon on Windows machines when the VNC service is running.
• VNC - Set Idle Timeout to 0 (Never Timeout)
  • Sets the VNC Idle Timeout to 0 so that an idle VNC RC session is not disconnected. Useful when performing remote operations on machines that take a long time to complete and where you do not want the VNC session to automatically time out after 1 hour (default) of inactivity.
• VNC - Enable Wallpaper when Remoting
  • Enable Wallpaper when remote controlling a system. Couple with Disable VNC Icon for completely silent remote control of an agent.
• VNC - Remove RealVNC from Start Menu
  • Remove the RealVNC entry from the Start Menu.

Core.4 Other Tools and Utility Procedures.Managed Services.Monitoring.Ping Check

• Ping IP Address 1
  • This procedure pings an IP address to get results you can use in another procedure. This could also be a port or any other device.
• Ping IP Address 2
  • This procedure tests the variable from Ping IP Address to see if the address can be pinged without packet loss. If there is packet loss, the system sends an e-mail with the results of the ping. If there is no packet loss, it logs an All OK result.

Core.4 Other Tools and Utility Procedures.Managed Services.Monitoring.Port Check

• Port Monitor 1
  • Part 1 of 2: Monitor a port on a host or IP address and send out an email when the port fails to respond. Edit step 1 with the hostname or IP address, edit step 2 to enter the port number you wish to monitor, and edit step 3 to specify the email addresses (comma separate multiple addresses) to send an alert to when the port fails to respond. Edit the procedure Port Monitor 2 to modify the email subject and body.
• Port Monitor 2
  • Do NOT schedule this procedure. It is a child procedure called by Port Monitor 1. Schedule Port Monitor 1 to run on a machine to monitor a port on a host or IP Address.

Core.4 Other Tools and Utility Procedures.Managed Services.Monitoring.Web Check

• Check Web 1
  • Procedure pulls the output of the webpage configured as the siteURL variable. The Check Web 2 script will verify that expected content exists in the output. You must configure the siteURL variable and Test File search string in Check Web 2 in order to customize this procedure. This Sample checks www.google.com/index.html for the word "google".
• Check Web 2
  • Check Web 2 verifies that expected content exists in the output from the URL request. You must change the Test File command for content that would be found when the URL tested is functional. In this Sample, we check for the word "google" on the google homepage.

Core.4 Other Tools and Utility Procedures.Managed Services.Policy Management

• Windows Group Policy Update (GPUPDATE /FORCE)
  • Reloads the Group Policy on Windows Machines.

Core.4 Other Tools and Utility Procedures.Managed Services.Server Management.Services Remediation

• Start Service (W32Time)
  • This procedure restarts the windows time service. This is a sample procedure demonstrating how to start a service using Kaseya Agent procedures.
• Stop Service (W32Time)
  • This procedure stops the windows time service. This is a sample procedure demonstrating how to stop a service using Kaseya Agent procedures.

Core.4 Other Tools and Utility Procedures.Managed Services.Server Management.Terminal Services

• Change Terminal Services RDP Listening Port
  • This procedure changes the default Terminal Services RDP port from 3389 to a new port of your choosing.

Core.4 Other Tools and Utility Procedures.Managed Services.System Management

• Download SysInternals Process Explorer
  • This sample demonstrates how to download files from remote sources using the Get URL agent procedure command. Simply specify the URL to download and the target location. In this sample we are downloading directly from the vender website, however a popular method of distributing your files is to store them in a public accessible ftp or website (cloud storage) using this method to download them to your endpoints. This sample simply downloads the file, however you can extend the functionality to install or execute files using the execute shell command in agent procedures. Also note that in this script we are using a variable for the agent temp directory of the agent. See Agent Working Directory Path in Using Variables in the VSA online help.
• Send Message if Logged On
  • This procedure sends a message to all your users if you need to do maintenance. On a system, you can use the remote control tab to send a message but there is no a way to send a message if they are logged on.

Core.4 Other Tools and Utility Procedures.Operational Communications

• Copy OpComm Messages
  • Copies down all the latest OpComm message files from the Server to the target machine.
• Get User name - Then Welcome
  • Retrieves the currently logged in user from a SQL View and then sends a "Welcome to our IT Support service" message to that user. If no user is logged on, the agent procedure reschedules itself to run again in 10 minutes.
• OpComm-ActionRequired
  • Displays the ActionRequired OpComm message to the logged on user. OpComm messages are for communication of standard operational activities, notifications and reminders. The folder of OpComm messages can be customized and extended to support other forms of end user communications. These files are located in the Kaseya\WebPages\ManagedFiles\VSASharedFiles\OpComm folder on the Kaseya server.
• OpComm-Backup
  • Displays the Backup OpComm message to the logged on user. OpComm messages are for communication of standard operational activities, notifications and reminders. The folder of OpComm messages can be customized and extended to support other forms of end user communications. These files are located in the Kaseya\WebPages\ManagedFiles\VSASharedFiles\OpComm folder on the Kaseya server.
• OpComm-Emergency
  • Displays the Emergency OpComm message to the logged on user. OpComm messages are for communication of standard operational activities, notifications and reminders. The folder of OpComm messages can be customized and extended to support other forms of end user communications. These files are located in the Kaseya\WebPages\ManagedFiles\VSASharedFiles\OpComm folder on the Kaseya server.
• OpComm-MachineAudit
  • Displays the MachineAudit OpComm message to the logged on user. OpComm messages are for communication of standard operational activities, notifications and reminders. The folder of OpComm messages can be customized and extended to support other forms of end user communications. These files are located in the Kaseya\WebPages\ManagedFiles\VSASharedFiles\OpComm folder on the Kaseya server.
• OpComm-MaintSchedule
  • Displays the MaintSchedule OpComm message to the logged on user. OpComm messages are for communication of standard operational activities, notifications and reminders. The folder of OpComm messages can be customized and extended to support other forms of end user communications. These files are located in the Kaseya\WebPages\ManagedFiles\VSASharedFiles\OpComm folder on the Kaseya server.
• OpComm-NetworkDowntime
  • Displays the NetworkDowntime OpComm message to the logged on user. OpComm messages are for communication of standard operational activities, notifications and reminders. The folder of OpComm messages can be customized and extended to support other forms of end user communications. These files are located in the Kaseya\WebPages\ManagedFiles\VSASharedFiles\OpComm folder on the Kaseya server.
• OpComm-PatchUpdate
  • Displays the PatchUpdate OpComm message to the logged on user. OpComm messages are for communication of standard operational activities, notifications and reminders. The folder of OpComm messages can be customized and extended to support other forms of end user communications. These files are located in the Kaseya\WebPages\ManagedFiles\VSASharedFiles\OpComm folder on the Kaseya server.
• OpComm-RegularMaintenance
  • Displays the RegularMaintenance OpComm message to the logged on user. OpComm messages are for communication of standard operational activities, notifications and reminders. The folder of OpComm messages can be customized and extended to support other forms of end user communications. These files are located in the Kaseya\WebPages\ManagedFiles\VSASharedFiles\OpComm folder on the Kaseya server.
• OpComm-VirusScan
  • Displays the VirusScan OpComm message to the logged on user. OpComm messages are for communication of standard operational activities, notifications and reminders. The folder of OpComm messages can be customized and extended to support other forms of end user communications. These files are located in the Kaseya\WebPages\ManagedFiles\VSASharedFiles\OpComm folder on the Kaseya server.
• OpComm-VirusThreat
  • Displays the VirusThreat OpComm message to the logged on user. OpComm messages are for communication of standard operational activities, notifications and reminders. The folder of OpComm messages can be customized and extended to support other forms of end user communications. These files are located in the Kaseya\WebPages\ManagedFiles\VSASharedFiles\OpComm folder on the Kaseya server."
• OpComm-Welcome
  • Displays the Welcome OpComm message to the logged on user. OpComm messages are for communication of standard operational activities, notifications and reminders. The folder of OpComm messages can be customized and extended to support other forms of end user communications. These files are located in the Kaseya\WebPages\ManagedFiles\VSASharedFiles\OpComm folder on the Kaseya server."

Core.4 Other Tools and Utility Procedures.Patch Management

• WinAutoUpdate Status Check
  • Checks the last known status of Windows Automatic Update based on the most recent Patch Scan and runs "WinAutoUpdate Enabled" if it is enabled, or "WinAutoUpdate Disabled" if it is disabled. Used to create Views showing machines with Windows Automatic Update enabled or disabled.
• WinAutoUpdate Disabled
  • DO NOT RUN/SCHEDULE THIS PROCEDURE. It is called by "WinAutoUpdate Status Check" if Windows Automatic Update is disabled on a machine.
• WinAutoUpdate Enabled
  • DO NOT RUN/SCHEDULE THIS PROCEDURE. It is called by "WinAutoUpdate Status Check" if Windows Automatic Update is enabled on a machine.
• Create Repository Share
  • Creates the File Source Local folder and Network Share to act as the repository for Windows patches downloaded from the Internet via Patch Management.
• Patch Pre-Warning
  • Sends a message to the logged on user that Patches and Security Updates abe about to be installed on the machine. Designed to be used as a Pre-Procedure for Patch Automatic Updates.
• Patch Reboot
  • On Windows Workstations the procedure prompts a logged on user to reboot due to Security patches/updates having been installed. If user responds Yes, then it notifies them that their system will be rebooted in one minute, and to save work and close their applications. If user responds No, then it schedules again to run in 60 minutes. If no user is logged on to the workstation, then the system is rebooted. If the machine is a server, and the Patch Reboot E-Mail address is configured, then the procedure sends an email to that email address indicating that the machine needs attention (a reboot).

Core.4 Other Tools and Utility Procedures.Patch Management.Suspend Alarms After Patch

• Patch Post-Unsuspend Alarms
  • Resumes Monitoring related Alarming. Designed to be used as a Post-Procedure for Patch Automatic Updates when the machine is rebooted immediately after patching.
• Suspend Alarms for 10mins
  • Suspends Monitoring related Alarms for 10 minutes. Designed to run as a Post-Procedure for Patch Automatic Updates when reboot takes place automatically after patching.
• Suspend Alarms for 10mins - Recurring
  • Suspends Monitoring related Alarms for 10 minutes and then schedules itself again to run in 5 minutes so that there are no possible gaps in the suspended alarm interval. Designed to run as a Post-Procedure for Patch Automatic Updates when a reboot may not take place immediately.
• Suspend Alarms for 120mins
  • Suspends Monitoring related Alarms for 120 minutes. Designed to run as a Post-Procedure for Patch Automatic Updates when reboot does not take place automatically after patching.

Core.4 Other Tools and Utility Procedures.Run Now System Scripts

• Run Now Baseline Audit
  • Executes the System Agent Procedure "Baseline Audit".
• Run Now Disable Windows Automatic Update
  • Executes the System Agent Procedure "Disable Windows Automatic Update".
• Run Now Latest Audit
  • Executes the System Agent Procedure "Latest Audit".
• Run Now Patch Scan
  • Executes the System Agent Procedure "Patch Scan".
• Run Now Server Roles Audit
  • Executes the client side LUA system script to perform a Server Roles Audit.
• Run Now System Info
  • Executes the System Agent Procedure "System Info".
• Run Now Update Lists By Scan
  • Executes the System Agent Procedure "Update Lists By Scan".
• Run Now Uninstall Agent (Retains Agent Data)
  • Executes the System Agent Procedure "Uninstall Agent". After the Agent is uninstalled the system retains that Agents data in the system until it is manually deleted.
• Run Now Reset Windows Automatic Update
  • Executes the System Agent Procedure "Reset Windows Automatic Update".