KACE Product Support

We had the same problem, but we find out that before creating the image, the Registry Key for KACE was never deleted so, at the time of install the agent, it the computers will have two different MachineID's.

Check your Registry Key:
HKEY_Local_Machine\Software\Dell\Kace
and
HKEY_Local_Machine\Software\KACE\

If you have both and the MachineID's are diffrent, then:

-Uninstall the agent
-Delete both keys and KACE Folder on C:
-Restart your computer and reinstall the agent.

Good Luck!

Is your server version 5.3? If not I would recommend calling Kace support about getting up to date. They'll give you any required pre-updates. Then once your server is up to date you can use GPO to push the newest version of the client to machines which it isnt already deployed to. The KACE box itself will start updating other clients as they check in.

This may just be the version that has been provisioned to your machine by Kace. My K1100 said it was current, but was actually two releases behind prior to manually updating to the (actual) current 5.3.53053 release. I've come to learn that the support site is the best place for the current release.

John

John

What version of the agent and server are you running?

Sounds like you are trying to push the agent from the K1000 to the client, is this correct?

If you are using the 5.3 agent, .NET is not needed. Also, some of the earlier versions of the 5.3 agent had some issues collecting inventory, the locally cached inventory file contained an empty machine name and the inventory would not upload because of it. There were also some issues (can't remember which versions) where certain characters in the names of the software titles would cause problems. I believe most if not all of these issues were fixed with the latest 5.3 agent.

If the client OS is Vista or Win 7 on the new installs, UAC needs to be disabled.

What about other machines on your wireless network? It could be that there is an issue between firewall settings between network segments.

Alternately it could be that the machines have the wrong server identified while installing. How have you installed the agent? Did you use the exe/msi withthe server name specified in it? You could always use the reset conf command on a machine to ensure that it is pointing to the correct server.

So, assuming you are running 5.3 on the server side, the K1000 appliance has a way to configure agent updates for the existing clients. I believe this part is supposed to run before inventory when it tries to check in. If you are using organizations, you will have to set this under each org, otherwise make sure you are in the Admin UI and not the System UI.

On our 5.3.x K1000, it is located in: Settings -> K1000 Agent -> Agent Updates from Kace
The top section allows you to enable and configure the agent updates for existing machines, as well as limit it to specific machines or machine labels.

The loaded K1000 Agent Updates will show you what version is currently on the server, as well as a way to upload a different agent version from the .kbin file downloaded from Kace's support/download site. The latest version of the agent is 5.3.53177. The version listed here should also be the version that you are attempting to push out when you deploy it to new machines from the K1000.

If your K1000 server is still at 5.1 or 5.2, I would check with Kace support before upgrading to a 5.3 agent. I would also check with them if you need to get to the downloads for a newer version.

If you want to leave UAC enabled, you can use the client share on the KBOX to install the client from the target machine. Just be aware that you'll need to provide the KBOX share name during the client install (in my example below, I would specify - kbox):

\\kbox\client\agent_provisioning\windows_platform\ampagent-5.3.47173-x86.msi

Your agent name/version may differ, but the idea is the same. I haven't run into any issues using this method, although it's obviously not ideal for mass deployments.

You could also copy the installer to removable media, etc and install via that.

John

Also, if you are still runng the 5.1 agents, I can confirm agent check-in issues on a number of machines. I traced this down to a .Net-related file and subsequently moved to the 5.2 (and now 5.3) version. Haven't had the same issues since and I'm also using Latitude E6420 laptops here.