How to remove old sysaid agent

 
Author
Message
SysAider
38
 
I have sysaid agent 9.0.53 deployed on some machines for which the server is gone for good. There is no uninstall in add/remove programs and the service is running. What is the best clean way to remove it?
SysAid Customer Support Engineer
41
 
Hello MichalUVT,



Thank you for your post.

Regarding this topic , if the service it's still running it means that the manually performed un-install did not remove the Service as well (and in some of the situations the registry keys are still there as well).

What you can do it's eider use this text and create a batch file which has to be run with administrator rights on the device, or perform the operation from a Command Prompt opened with administrator rights.

This is the "text" :

sc stop SysAidAgent

ping 192.0.2.2 -n 1 -w 5000 > nul

sc delete SysAidAgent

REG DELETE HKLM\SOFTWARE\Ilient /f
REG DELETE HKLM\SOFTWARE\Wow6432Node\Ilient /f

taskkill /F /IM SysAidSM.exe
taskkill /F /IM SysAidWorker.exe

rd /S /Q "C:\Program Files\SysAid"
rd /S /Q "C:\Program Files (x86)\SysAid"


The second method would be to open, as i mentioned, a command prompt with admin rights and just delete the service:

sc stop SysAidAgent

sc delete SysAidAgent

Please test if this will work for you and let me know if i can assist you further.



Best regards,

Ionut.
SysAider
38
 
OK, thank you. I already copied unins000 exe and dat from another computer and then run it. These files are not there if the installation was performed by deploying using the network discovery.
It is there if it was installed by SysAidAgent.exe
SysAider
2
 
Is this method still valid for version 14?


--- update ---
It seems yes.

sc stop SysAidAgent
sc delete SysAidAgent
taskkill /F /IM SysAidSM.exe
taskkill /F /IM SysAidWorker.exe
rd /S /Q "C:\Program Files\SysAid"
rd /S /Q "C:\Program Files (x86)\SysAid"

This message was edited 3 times. Last update was at Mar. 28, 2017 10:42 AM

SysAider
12
 
Necroing this.

I went back and forth with SysAid several times trying to get them to provide proper uninstallation methods.

In the end, I had to figure it out by myself.

In case anyone else out there needs a reliable way to nuke installed versions of SysAid so you can properly install a new client, you can run the following powershell script from an admin ps console. The only thing I didn't get around to was code to find and remove start menu entries. (you can find it in the code by #stub and add it yourself, if you'd like)

I'm also still not 100% sure this gets everything, but it removes enough to allow a reinstall in cases where SysAid refuses to run properly. While this did work on over 150 systems in my environment without issue, I do not guarantee this won't break your computers since it is deleting registry keys, though I did add some logic to avoid that. Try it on something controlled before deploying to a large group of computers.

This message was edited 1 time. Last update was at Jan. 12, 2018 06:53 PM

SysAider
10
 
Hey Pinecones,
Did you get to try that script on XP machines by chance? I'm trying to downgrade agent versions on workstations with that OS since 17.4 (as I've painfully found out) no longer supports it.
SysAider
12
 
there is a fix for that... it's called windows 10. =oP

seriously though, i think windows xp only supports up to version 2 of powershell. i'm not sure if this script will work with it as-is with ps v2. if i find out, i'll let you know, otherwise if you have a safe environment to test in, i would just try it out. (making a hyper-v xp vm is what i would suggest)
SysAider
12
 
i just tested it by loading powershell in version 2 mode. you can do this by loading powershell with the version switch from cmd:
powershell.exe -version 2

this seemed to remove my installed copy of SysAid without issue. (requires reboot)

that's a pretty good indicator that it should work with windows xp... but i would still test it in a vm first.

i believe with xp you have to choose to install powershell / upgrade to v2. so if you're targeting a large group, you'll likely need to make powershell 2 part of the deployment.

This message was edited 1 time. Last update was at Feb. 02, 2018 11:54 AM

SysAider
10
 
there is a fix for that... it's called windows 10. =oP


Oh trust me, they would be gone if I had a "purge" button. Still have 800 to deal with...

Good point on powershell version though. If not powershell, working into some sort of vbs might be an option maybe?

This message was edited 1 time. Last update was at Feb. 02, 2018 12:12 PM

SysAider
10
 
Just saw your last post. Greatly helpful. Thank you! I'll give it a try and see where things pan out.
SysAider
12
 
Yea... I'm not too hip on the vbs scripting though, so you'd have to dig into that.

all the logic is there though.

AWESOME! let me know how it goes. also if you need help with any powershell stuff, i'd recommend joining the #PowerShell slack channel.

This message was edited 1 time. Last update was at Feb. 02, 2018 12:15 PM

SysAider
12
 
i DID just realize that the user folders are in a different spot... so you might have to manually adjust that. same with program folders.
SysAider
10
 
Yeah. Its only added on to the XP hot mess. Also, there's a powershell slack channel? Which slack space?
SysAider
12
 
http://slack.poshcode.org/ <-- you can sign up there.

there is also an IRC channel you can use to access it somewhere.
SysAider
10
 
This is great. Thanks again.