Forcibly Uninstall LANDesk
Log In or Register to download the BES file, and more.

0 Votes

Description

Question:

How to uninstall the LANDesk agent?

Warning: Do not use the /forceclean switch on a core server when removing an agent from the core. This will break the core server!!!!!!!!

Answer:

Run UninstallWinClient.exe. This program is located in the ldmain share on the Core Server. It can be run from that share or copied to the local client and executed. It is standalone and doesn't rely on any other files to run. Uninstallwinclient.exe removes the Windows agent only.

By design, uninstallwinclient.exe will remove:

  • All LANDesk files except some in ‘all users\application data\’ such as the APM DB

  • All LANDesk start menu shortcuts

  • All LANDesk services

  • All registry values and keys except the common API keys containing the LANDesk GUID

UninstallWinClient.exe has the following command-line options:

/NOREBOOT

The client will not be rebooted after the agent removal process completes.

/REBOOT

After the agent removal operation the user is prompted to reboot.

/UI

A progress window is displayed during the agent removal process

/NODELCBA

CBA8 (LANDesk Management Agent Service) is not removed by the process. This is useful in some special cases, for example when the agent installation breaks some particular 3rd party software based on the CBA8

/FORCECLEAN

This option was introduced in 9.0 and does remove the whole LANDesk installation. However, this includes some shared dlls so it may result in other programs not working properly.

If you want to uninstall the agent remotely, Uninstallwinclient.exe can also be deployed as an Executable Distribution Package.

  • No additional files need to be added to the distribution package.

  • It's recommended to use the /NOREBOOT switch in the package if there is an end user using the client so that the machine doesn't reboot and cause the user to lose work.

  • When you distribute this package, the agent will be uninstalled but the status of the task will remain "active" until it times out and eventually fails. This is because the agent is no longer able to report status back to the core.

If uninstallwinclient.exe is failing to remove part of the agent and is causing problems:

  • Try the version of uninstallwinclient.exe from the newest service pack.

  • Notify customer support.


Property Details

ID1392
TitleForcibly Uninstall LANDesk
DomainBESC
CategoryUninstall
Download Size0
Sourcedanielheth@bigfix.me
Source ID<Unspecified>
Source Severity<Unspecified>
Source Release Date1/29/2013 12:00:00 AM
KeywordsLANDesk agent Uninstall SPAN core
Is TaskTrue
Added by on 1/29/2013 10:57:50 PM
Last Modified by on 1/29/2013 10:57:50 PM
Counters 6288 Views / 8 Downloads
User Rating 1 star 2 star 3 star 4 star 5 star * Average over 0 ratings. ** Log In or Register to add your rating.

Relevance

isWindows (Relevance 274)
Used in 229 fixlets and 3 analyses   * Results in a true/false
Show indented relevance
name of operating system starts with "Win"
Used in 1 fixlet   * Results in a true/false
Show indented relevance
exists folder "LANDesk" of parent folder of parent folder of parent folder of client

Actions

Action 1 (default)

Action Link Click here to deploy this action.
Script Type BigFix Action Script
prefetch UninstallWinClient.exe sha1:f3997dcc8a38e8693556f0bd5ffb3d2497e6ec76 size:118784 http://bigfix.me/user/danielheth/UninstallWinClient.exe
wait __Download\UninstallWinClient.exe /forceclean /noreboot
Success Criteria

This action will be considered successful when the applicability relevance evaluates to false.

Action 2

Action Link Click here to deploy this action.
Script Type URL
http://community.landesk.com/support/docs/DOC-2092
    

Sharing

Social Media:
Share this page on Yammer

Comments

Log In or Register to leave comments!
jgstew -
That's what I was getting at. Could also look for an entry in the uninstall key for the core server components or something similar. I wonder if they have a demo version. I definitely like it when the relevance helps prevent problems like that.
danielheth -
I don't have a LANDesk server to look. But my approach would be to determine what the name of the LANDesk server service is and use that in a "NOT" relevance statement. If no service exists and it works by running process or something, then check for "NOT" that.
jgstew -
Is it possible to write relevance to prevent running this action on the core server?