/bundles/itninjaweb/img/Breadcrumb_cap_w.png
Hi all-

I'm trying to put together an SQL Report to display the Phase for each machine for specific Scheduled Tasks (Detect/Deploy) but I can't find where this information is located in the database tables (there doesn't seem to be a table referencing Machine ID's and Patchlink_Schedule ID's along with a status or phase).

Has anyone had any luck with this type of report?
0 Comments   [ - ] Hide 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.
Answer this question or Comment on this question for clarity

Answers

0
Can you define a bit more clearly what you mean? A great way to do this would be a sample report with a few lines.

In general though, the generic patch information is stored in various PATCHLINK_* tables in the KBSYS database. The machine and org specific info is stored in PATCHLINK_* in the ORGX database. ORGX.PATCHLINK_MACHINE_STATUS is probably the key table you are looking for.
Answered 06/30/2011 by: GillySpy
Seventh Degree Black Belt

Please log in to comment
0
Hi Gerald- Thanks for your reply.

Sadly, I can't give a sample report, as I can't find the tables/columns to reference or link. The information I'm looking for is what you would find in a Detect/Deploy task such as this:

---------------------------------------------------------------------------------------------------
Scheduled Task Status
# Machine Name Address Phase Task Date
1 DC-SV-HPSIM 142.239.220.40 completed 2011-06-21 20:15:37
2 HITSNS-CACTI 142.239.0.90 suspended 2011-06-22 01:25:29
3 DC-SV-GHOST 142.239.0.60 suspended 2011-06-22 01:25:29
4 DC-SV-ADM 142.239.218.13 suspended 2011-06-22 01:25:00
5 HITSNS-USERS 142.239.218.50 suspended 2011-06-22 01:25:00
6 DC-SV-RptsEng1 142.239.218.17 suspended 2011-06-22 01:25:01
7 dc-sv-ocs1 142.239.220.236 suspended 2011-06-22 01:18:29
8 DC-SV-WEBVID1 172.16.20.12 suspended 2011-06-22 03:41:25
9 DC-SV-WEBVID2 172.16.10.60 completed 2011-06-21 20:10:18
10 DC-SV-OCS2 142.239.0.36 completed 2011-06-21 20:10:18
11 DC-SV-OCSWEB1 142.239.0.35 error (Signature Download Failed) 2011-06-21 20:12:15
12 DC-SV-OCSEDGE1 142.239.255.31 completed 2011-06-21 20:10:19
13 DC-SV-OCSEDGE2 142.239.255.33 completed 2011-06-21 20:10:19
14 DC-SV-OCSWEB2 142.239.255.42 suspended 2011-06-22 01:25:00
----------------------------------------------------------------------------------------------------

However, we have 20-30 Detect schedules and 20-30 Deploy schedules, and looking at all the Deploy Schedules to see that each machine is in the 'completed' or 'pending reboot' Phase is time consuming and prone to human error. I was wanting to find out how the KBox get's the PHASE information and do a report for ALL the schedules that would show what machines were not in 'completed' or 'pending reboot'.

I've checked in ORGX.PATCHLINK_MACHINE_STATUS, but this gives a patched/not patched status for EACH patch for each machine, rather than the per-machine scheduled task phase.
Answered 06/30/2011 by: clairobc
Senior Yellow Belt

Please log in to comment
1
Information about the task itself (patching is one of the systems in the appliance that uses tasks) is in KBSYS.KONDUCTOR_TASK. An example would be this
http://www.kace.com/support/kb/index.php?action=artikel&cat=6&id=989&artlang=en

A colleague of mine suggested this, but i have not tested this:
Select Distinct M.NAME, M.IP, M.USER_NAME, KT.PHASE As PATCHING_PHASE From KBSYS.KONDUCTOR_TASK KT Left Join MACHINE M On M.KUID = KT.KUID Where KT.TYPE Like 'patch%' Order By M.NAME
Answered 07/11/2011 by: GillySpy
Seventh Degree Black Belt

Please log in to comment