Is it not possible to combine both a Smart Label and LDAP label?  I am trying to deploy software based on a Security Group, but to get the script to automatically stop applying once the software is installed.  An LDAP label can look at group membership..  A Smart label can look at installed software status.  Too hard to put them under one label and combine the logic?
1 Comment   [ + ] Show Comment


  • Well, it did look promising. Unfortunately creating multiple “Smart Labels” and “LDAP Labels”, then trying to join them together with a final Smart label does not work on my K1000 box running 6.3.113399.. When creating the final label using the filter option “Label Name” the preview test area seems to work as expected, but the actual results once the machines start to check in and inventory is incorrect. I have opened a ticket with Kace support. Based on their responsiveness thus far I should have an answer some time before Christmas 2019. Just sit tight.. ;)
    Dell Service Request # 2966326
Please log in to comment


I would do 3 labels for this but you can get away with 2.

1. LDAP Security Group label (I'm assuming your security group has computers in it and not users)
2. Smart Label to looks for computers that does not have that software installed
3. Smart Label that has Computers in both groups

Answered 09/16/2015 by: h2opolo25
Red Belt

  • Hi there. I am familiar with the process of creating labels. My question is how to get the script or distribution to take into account the result of all 3 labels. For example the script deployment would need to see that the computer is a member of a particular LDAP group, but that the software is already installed. Therefore the script would no longer apply. Based on my tinkering thus far I have not found a way to combine labels like this.
    • Oops.. Never mind. I just realized you could query label names from within a smart label. I get it now. Create two different labels querying both software and LDAP info. Then use a 3rd label to pull the results of each and create the logic I want. Use that label to deploy software. Fun.
Please log in to comment
If you use a managed install to deploy the software then you only need the LDAP label. Managed installs will only try to install the software if it is not present, so you just need to assign the LDAP label to the managed install and KACE will take care of detecting whether or not the software is installed and will install it as necessary.
Answered 09/17/2015 by: chucksteel
Red Belt

  • Thanks, good to know. In this case unfortunately it is a script. I had to write a batch file to perform tasks before and after the install. Too bad this functionality isn't in the deployment option. Or is it?
    • Yes, you can do that with a managed install. Create your script and include it in a zip archive with the installer. Upload the zip archive to the software title and then for the managed install choose Override default installation and enter the name of your script. KACE will extract the zip and then execute the script you specified. Remember to check the box for "Don't prepend msiexec.exe".
      • Hmm.. That's a little mind twisting. So let me see if I can regurgitate:

        1. Create batch script (ps1 isn't supported as of yet with Kace I have found). This batch script will complete initial required tasks (like closing running instances of the previous software version) and execute the install (which in my case is an EXE with a quiet/unattended switch option). This script will also perform some final tasks required for this particular app.

        2. Take the batch file and the EXE file and zip them.

        3. Go into software section of Kace and create a new Software title and upload this ZIP.

        4. Use this software item when creating the Distribution.

        Does that sound about right? If so I am confused how the software distribution will know what file to run... Normally when creating software distribution with EXE files I configure as follows:

        Select "Only display records with an associated file"
        Click "Override Default Installation" radio button, then fill in the full command.. For example "Setup.exe" -q

        How does this config change when using a zip and batch file?
      • For step 3 the title should already be in the software section, unless KACE doesn't detect the software correctly for some reason. My practice is to install the software on one machine manually and then check the inventory record for that machine to locate the appropriate software title.

        As for the managed install you specify the name of the batch script you created in step 1 instead of the setup.exe -q. That is how KACE knows to use the batch file instead of the executable.
Please log in to comment
Answer this question or Comment on this question for clarity