/build/static/layout/Breadcrumb_cap_w.png

KACE Product Support Question


Conversion of 9.1 Patching Smart Labels and patching labels to 10.x

02/11/2020 79 views

Hi,

I finally upgraded our k1000 9.1 to 10.1, but I have 27 Smart labels mostly related to patching, 2 reports, and 52 patch/detect/deploy labels that failed to convert that are deprecated.

I cannot perform any patching currently and I'm afraid this may take me forever since I didn't create any of these originally and patching changed so much.

I have looked at all of the below links but still cannot figure completely figure it out unfortunately. I manually have replaced many of the old vs new schema/tables (patchlink vs patch), etc., but can't figure out how to substitute some of them.

Like select uid is what now? I'll keep trying though.

Updating Custom SQL Queries for 10.0 (309572) https://support.quest.com/kace-systems-management-appliance/kb/309572/updating-custom-sql-queries-for-10-0

Deprecated Patching Items in the 10.0 Release (264454) https://support.quest.com/kace-systems-management-appliance/kb/264454/deprecated-patching-items-in-the-10-0-release

KACE SMA 10.0 Database Schema Changes (309180) https://support.quest.com/kb/309180/kace-sma-10-0-database-schema-changes

How to run the Patching Migration Report (309381) https://support.quest.com/kb/309381/how-to-run-the-patching-migration-report


I'm hoping since there are so many experts and helpful people on ITNinja if I post two examples of broken smart labels maybe someone can help me correct them and then I hopefully can correct the others because they are similar and then move on to the patching labels/schedules.

List_Missing_Patches_Not_Tested

SELECT UNIX_TIMESTAMP(RELEASEDATE) as DATEPOSTED_SECONDS, KBSYS.PATCHLINK_PATCH.IS_APP, KBSYS.PATCHLINK_PATCH.IMPACTID AS DESCRIPTION, KBSYS.PATCHLINK_PATCH.RELEASEDATE AS DATEPOSTED, KBSYS.PATCHLINK_PATCH.IS_SUPERCEDED, KBSYS.PATCHLINK_PATCH.DESCR, KBSYS.PATCHLINK_PATCH.ID AS BID, KBSYS.PATCHLINK_PATCH.UID AS UID, KBSYS.PATCHLINK_PATCH.IDENTIFIER AS BULLETINID, KBSYS.PATCHLINK_PATCH.STATUSID AS STATUS, KBSYS.PATCHLINK_PATCH.TYPE, KBSYS.PATCHLINK_PATCH.VENDOR, UNPATCHED, YEAR(KBSYS.PATCHLINK_PATCH.RELEASEDATE) as DATEPOSTED_YEAR, PATCHED, KBSYS.PATCHLINK_PATCH.TITLE, KBSYS.PATCHLINK_IMPACT.IMPACT_SEQ, PATCHLINK_PATCH_STATUS.STATUS AS PATCH_STATUS, CACHE_SIZE AS CACHE_SIZE, KBSYS.PATCHLINK_PATCH.ID as TOPIC_ID FROM KBSYS.PATCHLINK_PATCH left join PATCHLINK_PATCH_COUNT on PATCHLINK_PATCH_COUNT.PATCHUID = KBSYS.PATCHLINK_PATCH.UID join KBSYS.PATCHLINK_IMPACT ON KBSYS.PATCHLINK_IMPACT.IMPACT=KBSYS.PATCHLINK_PATCH.IMPACTID left join PATCHLINK_PATCH_STATUS on PATCHLINK_PATCH_STATUS.PATCHUID = KBSYS.PATCHLINK_PATCH.UID WHERE ((( exists (select 1 from PATCHLINK_PATCH_LABEL_JT, LABEL where PATCHLINK_PATCH_LABEL_JT.PATCHUID = KBSYS.PATCHLINK_PATCH.UID AND LABEL.ID = PATCHLINK_PATCH_LABEL_JT.LABEL_ID AND LABEL.TYPE != 'HIDDEN' and LABEL.NAME = 'P_Patches_Not-Tested')) ) AND (( exists (select 1 from PATCHLINK_MACHINE_STATUS MS where MS.PATCHUID = KBSYS.PATCHLINK_PATCH.UID and MS.STATUS = 'NOTPATCHED')) ))


P_OS_Critical_Testing

select UID from KBSYS.PATCHLINK_PATCH where (((( (1 in (select 1 from LABEL, PATCHLINK_PATCH_LABEL_JT where PATCHLINK_PATCH.UID = PATCHLINK_PATCH_LABEL_JT.PATCHUID and PATCHLINK_PATCH_LABEL_JT.LABEL_ID = LABEL.ID and LABEL.NAME = 'P_Patches_In-Testing')) ) AND KBSYS.PATCHLINK_PATCH.RELEASEDATE > DATE_SUB(NOW(), INTERVAL 14 DAY)) AND KBSYS.PATCHLINK_PATCH.IS_APP = '0') AND KBSYS.PATCHLINK_PATCH.IMPACTID = 'Critical')


Any help at all will be appreciated since if I can figure out these two, I think I'll be able to figure out the other 25 smart labels, then start working on the schedules, patch labels and reports.

Thanks,
Jeff

3 Comments   [ + ] Show comments

Comments

  • I'm not sure, but when I clicked submit question in IE, Chrome or Firefox, the page would come back with OOPs something went wrong so I thought it wasn't submitted. Sorry for the duplicates. Not sure why I get that error on submission.
  • Hopefully someone else will have a better answer for you, but I upgraded our Kace to v.10 a few months ago. I kept having issues with patching failing and had a long deprecated list. I tried all kinds of things. I modifying and even recreated smart labels related to patching, I tried modifying existing patch schedules. I even went so far as to delete our entire catalog of downloaded patches and let it download again.

    In the end I had to delete and create new patch schedules. Once I did that, patching started working again. This made me wonder if I really ever had an issue with my patch smart labels.
  • Ugh! I hope we don't run into that situation. We have a about 20 patch schedules.
    The smart label above for List Patches Not tested always listed any patches that are missing from any machines that have not been tested yet so then I only had to go down that smaller list of patches much smaller list of patches and add them to our patches in testing label. It makes finding relevant patches much easier so I don't see patches for software we don't even run, etc.
    Then those patches automatically would move to other more specific testing labels and after 14 days they would move to production labels if there were no problems.
    I wasn't able to recreate them with the wizard since they use options not available in the wizard. I'm having trouble finding out what the new table names are replaced with for some of them. They're not in the Updating Custom SQL Queries for 10.0 or other lists. I'm using a trial and error technique currently.
    For example, what is MS.patchuid, patchlink_patch.uid, ms.status now? And where it says select uid, what is that converted to now?

Be the first to answer this question

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ