So, I've recently received the Kace 1000 & 2000 appliances, so still new at all this.

My question is, I'm wanting to setup all the systems that are considered faculty/staff into a group so when we have to install/upgrade software I can point it to the group and install.

Any suggestions would be very helpful. Reading through documentation still. Thank you!

0 Comments   [ - ] Hide Comments


Please log in to comment

Community Chosen Answer



At my last job I lucked out and all the faculty/staff shared a range of subnets, and a particular machine. I created a smart label to look for that range of IPs AND "System Model" contains Optiplex 330. 

At my new job I didn't get so lucky. I've included a reg key in the faculty/staff image the Kace inventories using a custom inventory. I then created a smart label to inventory that reg key, and depending on the number (random 4 digit number) it puts it in the appropriate label.

Custom Inventory: Department Location

RegistryValueReturn(HKEY_LOCAL_MACHINE\SYSTEM\Department, Dept, TEXT)


Smart Label:

Custom Inventory: Department Location = 1000

Answered 12/19/2012 by: dugullett
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity



I work at a college and have acad and staff machines.  We created two orgs on the k1000 and created machine placement rules to put them into the correct org. 

Answered 12/19/2012 by: SMal.tmcc
Red Belt

Please log in to comment

At my institution we have all computers in an OU depending on their department. I have LDAP labels setup to assign labels based on OU membership and use those to deploy software. All of these labels are in a label group called "Departments" and there is a smart label applied to machines with a department label, so campus wide deployments are targetted to that smart label for the most part.

Answered 12/20/2012 by: chucksteel
Red Belt

  • Chuck, another option for what you are doing, since LDAP labels can be onerous to setup, is a Custom Inventory Field. Believe it or not, the Windows Registry knows about the OU membership of the machine account in AD. I've got that very CIF in my Inventory. Here it is:

    Display Name (Title):
    AD - Distinguished Name - CIF
    Publisher (Vendor):
    Display Version:
    This will list the complete AD path to the machine account, allowing you to build Machine Smart Labels, instead of LDAP Labels.
    Custom Inventory Rule:
    RegistryValueReturn(HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy\State\Machine, Distinguished-Name, TEXT)

    See what you think. r2

    Ron Colson
    KACE Koach
Please log in to comment

Thank you all for your help... I will look into it some more... Been out of the office.

Answered 02/11/2013 by: akilpatrick
Fourth Degree Green Belt

Please log in to comment

It may be better to perform a more granular approach as opposed to focusing solely on faculty/staff. You can create very refined smart labels that will automatically group workstations based on defined search criteria for example, a business that has a 4 year rotation cycle will typically have a myriad of different workstations. Using Dells, you could sort them by models (optiplex 740, 745, 750, etc.) and apply updates to those groups individually using smart labels. This is an extremely broad range, however, it could be refined to a greater extent using additional search criteria. Using this method allows all workstations to be targeted and updated as needed.


If it is still in your interest to soley target faculty workstations, it would be best to group them using smart labels using any data that only their workstations have in common. As an example, if they're all grouped via subnet, use that as a target for your smart labels (groups). If they're not separated via subnets or VLANs, look for something unique to their workstations such as models, software, etc.


When you've determined the best method for structuring your update strategies and have smart labels in place, you can start performing patch scans and Dell updates that only targets the smart labels (groups) you want to be involved with the updates.

Answered 12/20/2012 by: rrjustin
Yellow Belt

Please log in to comment

Here's an article I wrote on labels and another that includes setting up LDAP, with examples from my own setup.



Hope that helps!


Answered 12/21/2012 by: jverbosk
Red Belt

Please log in to comment