Whether your logs have been uploaded and are visible on the K1000 appliance depend on these things:
- Type of script that you are running (online or offline)
- The last time that an agent updated their scripts
- Your agent log retention settings
- Whether or not the script ran on the PC
If you look at the inventory detail of a machine record in the K1000 UI, there is a section called "Logs". Here you may see question marks or checkmarks beside the name of the script like this:
TIP: If you hover over the icon of the log upload then you will get bubble text describing what the error or message is like this:
Things to check:
Check Script Settings
If you do not see any of the above evidence then make sure that:
- You selected the correct target PCs in the deployment details of your script.
- Check that the correct operating systems were selected
- Check that the script is "enabled"
- Schedule settings are correct
Check if the script ran on the PC
Offline scripts are stored in a subfolder of the KACE program directory. Specificially
c:\program files\kace\kbox\kbots_cache on a PC and
/var/kace/kagentd/kbot_cache. Check if the script XML for your script is there. The scripts are named based on the Kbot ID so you might need to open the files to be sure.
TIP: If you are looking at the script list in the webUI, The KBOT ID is embedded in the URL for the script
If the script is downloaded then you can check if it ran by looking at KBOT_LOG.txt file and looking for a line similar to the following: kbot[0:0] @ 2008-12-30T13:28:14 (activity) Running kbot: runkbot.exe 31 1230668578 LOGON -noLogUpload
If you see the flag -noLogUpload this is normal. All offline scheduled scripts run with -nologupload. It does not mean that logs will never be uploaded. It means to defer uploading the logs until the next scripting update interval.
Note: Offline scripts are only supported on Windows Operating System
(Optional) Force the Script to Run
If your PC is currently connected to the K1000 appliance via AMP (ie you have the greenlight icon in inventory) then you can force a kbot from the command line like this:
"c:\program files\kbox\kace\runkbot.exe" Xwhere X is the number of the K1000 script.
The exception to all of this are "online scripts", including the system scripts that control inventory and script update (ie kbots 2 and 3), and any run now operation upload their log results immediately.
You cannot force script/kbot #2 and #3 from the PC side. However, you can force them to run on the server side and thus force the logs to upload by running the script "force script update" against that PC (make sure to edit the script to target only your test PC.
Check Your Agent Log Retention Settings
Additionally, you need to make sure that your agent setting for "Agent Log Retention" is set to "Save All Agent Logs" like this:
On a K1200 appliance each organization can have separate agent log retention settings.
If you need help
Be sure to include all of the information above and these addtiional files: From the PC:
.