I have a number of machines that other people have accidentally install the kbox client on. I could care less about these machines and don't need them hogging a license. I'd like to easily and quickly remove the client from these machines, preferably using a smart label. I'd like to apply the smart label and move on with my day. I'm not a huge user of the k1000 (I'm just the k2000 expert) so its probably something painfully easy.

Is there a way I can do this?

Thanks in advance.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
A smart label would be the way to go.

How can you tell the "good" machines from the "bad"?
Answered 10/31/2011 by: dchristian
Red Belt

Please log in to comment
0
I have student machine labs running Fartronic's Deep Freeze. Needing/using the kbox for these machines is not necessary or practical. We have a special naming convention for these machines so they stick out like a sore thumb in the inventory list.

I just tried created a script that runs kinstaller.exe -display_mode=silent -uninstall and applied that script to a label I made. The script should run at any event, I checked all the boxes.

I tested it out by applying the label to one of the machines and forced it to update its inventory. However it still has the client installed. The machine shows it still has the label assigned and shows a script log for having run the script. No idea what I'm doing wrong.
Answered 10/31/2011 by: Tentacle Master
Fourth Degree Black Belt

Please log in to comment
0
Just did a run now and forced it to my test machine. Log shows it completed successfully in about 2 mins. It still shows up in inventory as connected.

ummm.....
Answered 10/31/2011 by: Tentacle Master
Fourth Degree Black Belt

Please log in to comment
0
If you go to inventory-> software -> kbox client software entry you can find the uninstall string.

Change the /i to a /x and add a /qn at the end.

Command line Ex:
msiexec.exe /qn /i {0000-0000-0000-00000}
Try running that as a script, it should work.
Answered 10/31/2011 by: dchristian
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity