Remove Kaseya Agent Manually

Posted on  by

Manually uninstall Kaseya agent. October 15, 2009 by Robert Masterson. If you need to remove Kaseya and it won’t uninstall from Add/Remove programs, try this.

  1. Once installed on a machine, the agent displays it icon in the computer's system tray. This icon is the user's only interface to the agent. The icon may be disabled at the discretion of the Administrator in the Agent Menu function. When the agent is running and successfully checking into the VSA, the agent icon's background is blue.
  2. The previous consulting firm used Kaseya and has the Kaseya agent installed on all network workstations - looks like it was deployed. How can I remove this agent and service, can't find any way to uninstall it from add remove and there isn't an obvious uninstall file for it.

If you need to remove Kaseya and it won’t uninstall from Add/Remove programs, try this:

First try the uninstall string

“C:Program FilesInstallShield Installation Information{48C76121-4F90-11D5-9884-0050BA85A903}Setup.exe” UNINSTALL

or

“C:Program Files(x86)InstallShield Installation Information{48C76121-4F90-11D5-9884-0050BA85A903}Setup.exe” UNINSTALL

If this fails,

1. Stop the Kaseya Agent service
2. Set the Kaseya Agent service to “disabled”
3. Delete HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/KAPFA
4. Delete HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/KaseyaAgent
5. Reboot the machine (so that we can be sure that windows knows the service is disabled)
6. Delete c:program fileskaseya
7. Delete c:program FilesInstallShield Installation Information{48C76121-4F90-11D5-9884-0050BA85A903}

When finished delete the machine entry in Virtual Administrator using the “Delete account now without uninstalling the agent” function.

Install/Remove: Backup

The page installs or uninstalls Acronis backup and disaster recovery (BUDR) software on selected machine IDs. Each BUDR installation on a managed machine uses up one BUDR license. The number of licenses available depends on the total number of licenses purchased and allocated to each group ID using System > License Manager. BUDR licenses are purchased and allocated separately for workstations and servers.

  • Backups require additional agent capability so you may be prompted to update the agent prior to installing backup.
  • Backup installation requires Windows Installer v3 and up. Your system checks the results from the last audit for v3. Your system will not recognize you have installed the latest Windows Installer until after the next audit runs on that machine.

    Note: BUDR does not support new installs of 9x and NT.

Installing BU-DR Client 9.5

Customers are not required to install the new BU-DR client to keep using backup. BU-DR will work with a mix of BU-DR client versions 9.1 and 9.5 (the new client version). However, in order for the endpoint to take advantage of the new features including encryption, synthetic backup and image conversion, the endpoint must be updated to the new version of the BU-DR client software.

Customers need to update the Kaseya agent to 5.1.0.1 to cancel a backup with the new 9.5 client. Kaseya recommends deploying the new agent to all systems that have the new backup client software. Use the 'Force update even if agent is at…' option to force the agent to update to 5.1.0.1.

Installation Requires a Reboot

can backup all volumes, including the boot volume, while in use. accomplishes this through the use of a low level driver. As such, backup require a reboot to complete its installation.

  • After installation completes, if a user is logged in, the systems asks the user to Reboot Now or Continue Working. If the dialog is not answered within 5 minutes, Continue Working is assumed. If no one is logged in, the system reboots immediately.
  • You can avoid displaying this dialog box by clicking the checkbox.
  • A button displays in the column next to a machine ID if was checked or the Reboot Now/Continue Working dialog box on the target machine timed out.
  • Installing backup on a server when no one is logged in reboots the server when backup installation completes.

If Installation Fails on Windows 2003 Server

By default, Windows 2003 Server warns before installing any low level drivers. To date, Microsoft only signs their own low level drivers. Acronis can only deliver an unsigned driver as part of their backup system. To successfully install on a 2003 server, you must do one of the following:

  • Click Yes when asked if it is OK to install the unsigned driver. If this dialog box gets no response in two minutes, then Windows assumes No and blocks the installation.
  • Prior to installation, set the Local Group Policy to Silently Succeed for Devices: Unsigned driver installation (see below).

Install/Reinstall

Remove

Click to install or reinstall backup software on selected machine IDs using the options previously selected.

Date/Time

Enter the year, month, day, hour, and minute to schedule this task.

Cancel

Click to cancel execution of this task on selected managed machines.

Verify Install

Click to confirm the backup software is installed on selected machine IDs. Use this if you suspect someone removed the backup software on managed machines.

Copy backup settings from select machine ID

Click this link to copy the backup configuration and schedules from an existing machine to all selected machines.

Warn if installer pushes from server

If checked, a warning message displays if the backup file is installed from the KServer. The backup install file is over 100MB. Avoid file transfer from the KServer to each machine in a LAN using Patch Management > File Source. Select the option. Once set, the KServer writes a single copy to the LAN file share. The backup installation runs from that location for all managed machines on that LAN.

Remove

Click to uninstall the backup software from selected machine IDs. A reboot on the machine is required to remove the low level driver and complete the uninstall.

Stagger by

You can distribute the load on your network by staggering this task. If you set this parameter to 5 minutes, then the task on each machine ID is staggered by 5 minutes. For example, machine 1 runs at 10:00, machine 2 runs at 10:05, machine 3 runs at 10:10, ...

Skip if Machine Offline

Check to perform this task only at the scheduled time, within a 15 minute window. If the machine is offline, skip and run the next scheduled period and time. Uncheck to perform this task as soon as the machine connects after the scheduled time.

Do not reboot after install

If checked, selected machine IDs are not rebooted after the backup software is installed.

Select All/Unselect All

Click the link to check all rows on the page. Click the link to uncheck all rows on the page.

Check-in status

These icons indicate the agent check-in status of each managed machine:

Online but waiting for first audit to complete

Agent online

Agent online and user currently logged on. Icon displays a tool tip showing the logon name.

Agent online and user currently logged on, but user not active for 10 minutes

Agent is currently offline

Agent has never checked in

Agent is online but remote control has been disabled

The agent has been suspended

Note: Different icon images display when this addon module is installed in a 5.x VSA. The Remote Control > page displays a legend of the specific icons your VSA system is using.

Machine.Group ID

The list of Machine ID.Group IDs.Organization IDs displayed is based on the Machine ID / Group ID / Organization ID filter and the machine groups the user is authorized to see using System > User Security > Scopes.

Installed

This column displays the status of installed software on selected machines:

  • Awaiting reboot. A button displays in the column next to a machine ID if was checked or the dialog box on the target machine timed out.
  • Backup does not support Vista at this time.
  • Failed to install – unsigned driver installation policy may have blocked install
  • Failed to install
  • Install pending
  • Remove pending
  • Remove pending
  • Reset Policy pending
  • The date and time the backup software successfully installed
  • Unsigned driver policy reset
  • Update Agent required to support backup
  • Verify failed
  • Window v3 installer and up required

Version

Displays the version of Acronis backup software installed on the managed machine. If a new version is available, also displays Update Available. at the top of the column displays the latest version of backup software available.

Verify

Displays one of the following:

Remove Kaseya Agent Manually

  • The date and time the backup software was verified as installed on the machine ID.
  • Verify pending - Displays with a button.
  • Not Verified - Displays with a button.

Remove Kaseya Agent Manually Windows 10

Type

Kaseya Agent Install

The type of machine the backup software is installed on:

Remove Kaseya Agent Manually Email

  • Workstation
  • Server