Linux

Option 1 - Use Connector CLI

Log in to the endpoint using SSH and have an elevated shell.

Run the following command

/usr/local/intigua/Intigua-Utils/intigua rmc

The connector should make self-removal.

To check if Connector is installed see the instruction below.

Option 2 - Manual removal

If Option 1 could not remove the Connector:

1. Stop all running processes
   1. ps aux | grep connector64
   2. kill -9 <process ID>
2. Stop and disable the “vAgent” processes
   1. ps aux | <process name>
   2. kill -9 <process ID>
3. Delete the “Intigua” folder a. rm –rf /usr/local/intigua

Check if Connector exists

Check running processes using (Process should not exist)

ps aux | grep connector64

 Check if Connector folder exists (folder should not exist)

ls /usr/local/intigua

If both process and folder of the Connector does not exist - Connector is not installed on the endpoint

Windows

Option 1 - Use Connector CLI

Log in to the endpoint using RDP (or having remote execution privileges) and have an elevated shell.

"C:\Program Files\Intigua\Intigua-Utils\intigua.exe" rmc

The connector should make self-removal.

To check if Connector is installed see the instruction below.

Option 2 - Manual removal

If Option 1 could not remove the Connector:

1. Stop and delete the "Intigua vAgentManager" service via command prompt in Administrator mode.

sc stop vagentmanager

sc delete vagentmanager

2. Then, run the following two commands to remove the connector from the endpoint

reg unload hklm\vmi

REGSVR32 /U "C:\Program Files\Intigua\vAgentManager\PackageM
anager\vlink\vlink_3.9.4.226\bin\IntCore64.dll"

rmdir "C:\Program Files\Intigua\"

Notes:

1. You cannot be in the Intigua folder while running this command.  
2. change vlink_3.9.4.226 with the proper connector version (based on observed folder path)

Check if Connector exists

Check running processes using (Process should not exist)

tasklist | findstr vlinkprocess

 Check if Connector folder exists (folder should not exist)

dir 'C:\Program Files\Intigua'

If both process and folder of the Connector does not exist - Connector is not installed on the endpoint