I have a couple static labels that I use to collect machines needing JRE; one global Java7 Targets and one per region of the Java7 Targets such as Java7East Targets and Java7NW Targets.

My smart labels look for labels that begin with Java7East Targets and Java7-to-install which is a smart label that targets machines in the
Java7 Targets and Software Version Number != 7.0.130. From this the machnes get the smart label JRE7East2Install or JRENW2Install.

In my fiddling, I created the one smart label JRE7East2Install working possibly after squeezing the spaces out of the other labels and choosing alternative names to the batch of others, but, if I use the smart lable creator from the computer inventory tab, modifying for each region, they produce no results after checkin; unlike they tested.

A new test smart label will, but, if I copy the sql syntax to the other smart labels... still nothing.

I have K1000 server ver. 5.3.53053 and agents ver. 5.3.53177.  Is there a known issue with these versions or flaw in my nesting?

This in an example of a regional smart lable:

                  from ORG1.MACHINE
                 where (((  (1  in (select 1 from ORG1.LABEL, ORG1.MACHINE_LABEL_JT where MACHINE.ID = MACHINE_LABEL_JT.MACHINE_ID and MACHINE_LABEL_JT.LABEL_ID = LABEL.ID and LABEL.TYPE != 'hidden' and LABEL.NAME like 'Java7East Targets%')) ) AND (1  in (select 1 from ORG1.LABEL, ORG1.MACHINE_LABEL_JT where MACHINE.ID = MACHINE_LABEL_JT.MACHINE_ID and MACHINE_LABEL_JT.LABEL_ID = LABEL.ID and LABEL.TYPE != 'hidden' and LABEL.NAME like 'Java7-to-install%')) ))
1 Comment   [ + ] Show Comment


  • I am having the same issue except trying to narrow the machines for patch deployments to machines on the to LAN based subnets and exclude VPN clients.

    Have you had any success since your post?
Please log in to comment


Old post but I've been struggling with a similar issue and finally got it working so adding it here for anyone else in search of answers.  Everything would show up in the smart label test just fine, but the nested labels were never applied correctly no matter what I did.  Finally after a couple days with tech support found a solution:

On K1000 v6 in Label Management -> Smart Labels -> Choose Action go to Order Labels and your label type. Instead of having all labels with an order of 100 order them from 1 to whatever (1 being the first label it checks/applies) with the higher number going to the more nested labels.  So you end up with:
Machine-Specific-Label1 = Order 1
Machine-Specific-Label2 = Order 2
Generic-Nested-Label2 = Order 10
Very-Generic-Nested-Label3 = Order 40

This fixed the issue for me both on device and patch smart labels.
Answered 12/08/2015 by: pultsch
White Belt

  • Thanks for this input pultsch! I don't really have anything to test this with any longer. I may have been dealing with a system bug or data corruption at the time. It more than likely was more to do with my own learning curve however.

    I continue to have smart label which incorporate other (nested) smart labels and work just fine today in 6.3.113399.

    What I have learned since is that when dealing with software versions, they do not necessarily refer to the software title in question; they only need to find another title that matches this version to be considered a match unfortunately. This is a sad reality of using the SQL wizard. There are better ways to form a proper SQL statement manually to get the intended result. So until Dell KACE gets a better wizard that can actually... not sure I'm using the proper syntax but... merge tables or group queries, doing a manual SQL query is all we can use; and luckily the provide this ability.
Please log in to comment
Answer this question or Comment on this question for clarity