How to uninstall Opsi client agent

[ttblum]

Hello,

We are currently using Opsi to deploy operating systems, we're not using it to install applications or manage OS's.

What's the best way to uninstall the Opsi client agent in Windows?

Should we run the uninstaller script in c:\program files (x86)\opsi.org\uninst, or remove it from Programs and Features, etc.?

[uncle_scrooge]

No difference.
The uninstall string used by deinstall.cmd and from within Programs and Features are the same.
You can find the latter in HKLM\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\opsi-client-agent.
So it's up to you.
As with every uninstaller there will be remnants. You might check c:\program files (x86)\opsi.org and c:\opsi.org.

[wolfbardo]

mmh, do you remember "Prevent opsi-agent from being installed"

viewtopic.php?t=9498

regards,
bardo wolf

[ttblum]

In version 4.1, I'm finding that if I rename

50_opsi-client-agent.cmd

to

50_opsi-client-agent.txt

every script higher than 50 does not run, including necessary cleanup scripts. This worked fine in version 4.0.

[n.wenselowski]

Hi,

In version 4.1, I'm finding that if I rename

50_opsi-client-agent.cmd

to

50_opsi-client-agent.txt

every script higher than 50 does not run, including necessary cleanup scripts. This worked fine in version 4.0.

Looks like a bug to me.
What netboot product in what version are you currently using?
Does updating - if update available - the netboot product help?

Kind regards

Niko

[ttblum]

I'm using:

Opsi version: 4.1.1.65

Netboot product: win10-x64, Windows 10 x64, Version 4.1.0.1-1 .

All the scripts run correctly until I rename:

Code: Alles auswählen

/var/lib/depot/opsi-client-agent/files/opsi/postinst.d/50_opsi-client-agent.cmd 

to 

/var/lib//depot/opsi-client-agent/files/opsi/postinst.d/50_opsi-client-agent.txt

[wolfbardo]

In version 4.1, I'm finding that if I rename

50_opsi-client-agent.cmd

to

50_opsi-client-agent.txt

every script higher than 50 does not run, including necessary cleanup scripts. This worked fine in version 4.0.

Properly most of the older

Code: Alles auswählen

postinst.d

scripts have been really

Code: Alles auswählen

cmd

Batches

For instance the new

Code: Alles auswählen

80_repartition.cmd

need a working opsi-winst / opsi-script.

So for me this change in behaviour is more a feature than a bug.

Coming back to your Question

Hello,

What's the best way to uninstall the Opsi client agent in Windows?

Should we run the uninstaller script in c:\program files (x86)\opsi.org\uninst, or remove it from Programs and Features, etc.?

you can run

a) opsi-client-agent = uninstall

via opsi

or

b) have a deeper look in the postinst.d mechanism described in the getting started to get what you need (perhaps working only with opsi-script/opsi-winst without installing opsi-client-agent)

kind regards,
bardo wolf

[ttblum]

Neither removing the agent in Add Remove Programs or running the uninst script works, the Opsi agent still appears at bootup anyways.

I uninstalled via Opsi, and that does appear to have removed it cleanly.

We already deployed a computer with opsi-agent to a user that's not connected to our LAN. I disabled both Opsi Windows services, and now the opsi agent no longer launches at bootup.