Document Actions
remove the agent
That's it man, game over man, game over!
If you're in a pilot, you really want to think about removing the agent before you delete the core server. It's less fun to do this after the fact.
From Windows machines, you can call \\CORE\LDMAIN\UNINSTALLWINCLIENT.EXE, as documented in KB Article 3972
. This will require authentication as a member of the LANDesk Management Suite group on the core... but you can copy that binary to a thumbdrive or a public share and go to town.
However, uninstallwinclient.exe doesn't do a full removal... for one thing, it leaves the Device ID in place so this machine will use the same unique identifier if you put the agent back on. If you want to completely nuke the installation, you'll need to make a script.
@ECHO OFF uninstallwinclient.exe /noreboot IF NOT "%ERRORLEVEL%"=="0" GOTO :end reg delete HKLM\Software\Intel\LANDesk /va /f IF NOT "%ERRORLEVEL%"=="0" GOTO :end reg delete HKLM\Software\LANDesk /va /f IF NOT "%ERRORLEVEL%"=="0" GOTO :end :end exit /b 0
If you installed via GPO, backing out the GPO is also required. Be aware though that uninstalling the GPO just removes the Advance Agent stub, not the actual agent. You want to remove the Advance Agent for cleanup purposes, but removing it doesn't remove anything important.
On a Macintosh, Use Connect to Server to mount SMB://CORE/ldmain and run /ldmacclientuninstall.sh. This will require authentication as a member of the LANDesk Management Suite group on the core.
Forgot your password?
New user?
