Hello, I recently cloned a server using VMware that we already had the KACE agent installed and operating. (Lets call it SERVER A)
On the new clone I uninstalled the KACE agent (5.2) and reinstalled a fresh copy. (SERVER B)

Now in my KACE appliance it shows the inventory as SERVER B however it flip flops IP addresses between SERVER A and B.
Its like the appliance is only seeing them as one server. I figured this may be to due to some hardware ID buried in the agent?
How can I fix this issue and get both servers to show up in my appliance?

I even went back and uninstalled/reinstalled the agent on both machines. No luck.

Servers are Windows 2008 R2
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
I guess, deleting the record of both servers from the Asset module of Kbox will solve your problem. However history information will be lost [8|]

following information from the KACE Knowledge Base might help you.

This is caused by a new default setting in the K1000 appliance since version 5.1 called Duplicate Machine Detection. This feature prevents the K1000 from allowing machines to share the same KUID. Each inventory record is unique as identified by a KUID (a GUID that we store on the agent). When this setting is enabled Kbox only allow one AMP connection per KUID

How to Fix and Clean it up
The setting mentioned above is In Settings->Control Panel->Agent Message Protocol Settings ( http://k1000/systemui/settings_smmp.php ) there is an option called Disable Duplicate Machine Detection and by default it is unchecked -- which means it is enabled ( yes, that is confusing).
Answered 05/12/2011 by: afzal
Fourth Degree Green Belt

Please log in to comment
0
Awesome thanks, I will get with our KACE appliance admins and have the give that a shot.
Answered 05/12/2011 by: Cyberfed
Senior Yellow Belt

Please log in to comment
0
Resetting the KUID on both machines would also sove the problem.
Answered 05/12/2011 by: cblake
Red Belt

Please log in to comment
0
Can you reset the KUID on the servers or is that done in the appliance?
Answered 05/12/2011 by: Cyberfed
Senior Yellow Belt

Please log in to comment
0
Changing the KUID's worked on the servers.
Thanks guys. I used the following steps:

1. On the client machine shutdown the KBox Management Service 2. Go to the Registry using regedit and remove the two following keys: HKEY_LOCAL_MACHINE -> Software -> Kace Remove:
A. InstallID entry
B. MachineID entry Restart the machine and check in again. The Kbox Server will generate a new keys for client machine.
Answered 05/12/2011 by: Cyberfed
Senior Yellow Belt

Please log in to comment
0
What happens in this scenario:

1. Computer A has Kace installed and needs reimaging
2. Computer A has been reimaged w/ a Image that doesn’t have Kace installed
3. Kace is now installed on Computer A

How does the newly imaged machine show up in Kace?
Answered 05/17/2011 by: bschwartz@veros.com
Yellow Belt

Please log in to comment
0
I think you would be fine. It will end up having the same KUID since its a clone (aka reimage).
For me the KUID didnt change even after uninstalling/reinstalling the agent.
You will have 1 entry in your appliance. At least that's been my expirence from this whole thing.
Answered 05/17/2011 by: Cyberfed
Senior Yellow Belt

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