KACE Product Support Question
K1000 as Virtual Appliance - Tasks not running as expected
We recently migrated our K1000 (6.2) from a hardware K1100 appliance to Virtual running within VMware ESXi/vSphere on a Dell PowerEdge 2950.
All "appears" to be functioning correctly and we've been running with this setup for a few months without any real issues. However, after we started looking closer at some things we've noticed that all is not quite 100%.
At least once a week the K1000 clock suddenly loses sync. We’ll arrive in the office at 8am only to find the K1000 thinks its 4am which really messes up a lot of things. From the KB I’ve seen this is due to ESXi not being man enough for the job, but at the moment I don’t have another option.
Also...under Communication Settings we have our Inventory set to 2 hours (7.66 connections per minute). If I look at the Inventory though there are machines in the list that have active AMP connections but have a Last Inventory time of “3 hours, 25 minutes”. I don’t recall this being the case when we were on hardware. The machines would inventory every 2 hours as instructed and no machine with an active AMP connection would go over 2 hours without performing an Inventory. If I check Agent Tasks under troubleshooting I can see that as far as the K1000 is concerned these machines were due to check-in after 2 hours as planned, but haven’t. They will eventually check-in.
We have the same problem with Patching, if I set a Detect task to run at 9am it won’t actually start at 9am. I’ll see machines that have been on all day running their Detect job at 2pm! The same happens with Deploy tasks. Save and Run Now doesn’t work at all with Patching.
As you can imagine, this is makes scheduling downtime and maintenance impossible.
Under Communication Settings I can see that our Load Average bounces between 0.8-1.8. I haven’t seen it go much higher.
All clients are also using the latest KACE Agent, however this problem existed on the older Agent too.
I plan to raise a support ticket for these issues, but I thought I’d reach out for ideas here too.