Managed Installs not running unless manual Inventory run
I have approximately 60 PC's that don't appear to even begin to install Managed Install applications when their auto-inventory is run every 6 hours as scheduled, or if I run the Force Check-in script across them. I find though, that if I manually run an inventory via the k1000 web interface for each one individually, the MI begins and completes successfully.
When it doesn't start, there are no logs that appear to contain any reference to the MI or the related software product (in this case a SQL 2008 R2 Express upgrade from SQL 2005). I would at least expect to see the install begin but fail due to perhaps an incorrect command line option on the install command, however I don't get anything logged relating to the MI. All affected PC's are running Windows XP SP3.
Any ideas?
EDIT: I've found that running C:\Program Files\Dell\KACE\runkbot.exe 6 0 manually on the PC's installs the applicable MI as well.
Something else to note, ALL machines are in remote locations with local replication shares setup. Many sites are still replicating patch data, but MI information has completed. Other machines at the same sites, have applied the MI during the applicable install window with no problems.
Answers (3)
I ran into that on machines that .net 1.1 was not installed on. What version is your kbox?
Comments:
-
K1000 - 5.3.53053. Agents are all on 5.3.53177.
I've checked a couple of the affected machines and they have .Net 1.1 installed, as well as .Net 2.0, 3.5 and 4.0. - robert.angell 12 years ago -
Yours would not be affected by .net, Windows firewall could also cause problems if it not set up right. the kbox could be blocked from communicating with the machine till you initiate the session from the machine itself. - SMal.tmcc 12 years ago
5.3.53177 Agent doesn't have dependency on .Net framework.
Are you saying that on the machine's where you have enabled MI, it doesn't get trigerred during normal checkin interval but gets triggered when you do "Force Inventory" from web interface or run "runkbot 6 0"?
Comments:
-
Yes, that is exactly right. - robert.angell 12 years ago
-
In you orignal question, you mentioned that MIs don't get triggered when you run "Force Checkin" script. That's expected, because Force checkin script only forces inventory , not MI's
However, if MIs are working with "Force Inventory Update" from Machine detail page and not working during regular checkin interval only for few computers then this is weird.
Can you please enable debugging in one of those client machines by following command
C:\Program Files\Dell\Kace\AMPTools set debug=true
and check in runkbot.log if "runkbot 6 " command is called when the scheduled checkin happens on those machines - AbhayR 12 years ago