Removing K1000 Agent- any traces left behind?
Hey guys-
One of our sysadmins here wants to install the K1000 on the parent image for our virtual machines, install windows updates, and delete the k1000 agent off of it before deploying that new parent image to all of our user's VMs. We only use Kace on our physical desktops, and not our virtual machines (VMware).
Our main concern with this is this: If we remove the agent from the parent image and something gets left behind, then when we deploy that parent image to the masses, roughly 300 virtual machines, then all 300 machines would check-in with Kace therefore maxing our Kace licensing.
So once the agent is removed from the VM via Kace, is anything left behind? Is it a clean uninstall?
Answers (2)
When you uninstall it does not have any of the exe's left to talk to the server so it will not consume a license, some registry entries are left but they are harmless for what you are doing. I had the client on my master and removed it and now push post sysprep and have not run into any problems at all.
Comments:
-
If want to play it safe after the uninstall delete reg key HKLM\software\kace
I am assuming windows 7 here: and if any of these directories still exist
program data\dell\kace, program files\dell\kace or program files\kace - SMal.tmcc 11 years ago-
http://www.kace.com/support/resources/kb/article/including-the-k1000-agent-in-an-image - dugullett 11 years ago
The KUID is left in the registry and if you want to use that image as a master image to capture and then deploy you need to remove this KUID from the registry as well after uninstalling the agent.
For 64 bit OS the key is HKLM\SOFTWARE\Wow6432Node\Dell\KACE\
For 32 bit OS they key is HKLM\SOFTWARE\Dell\KACE\
For Linux OS the key is stored in the file /var/dell/kace/kuid.txt
Regards,
StockTrader
Comments:
-
Thanks for the extra detail, helps make this a good reference for others - SMal.tmcc 11 years ago
