How to Fix KACE labels have unwanted machines as members

Where I work we use labels with associated LDAP labels to choose machines and users on which to perform actions.  During testing of various LDAP lookups, and the fact that when we obsolete computers we don't let them check in one final time, over time the labels end up acquiring machines that shouldn't be there.  For example, while attempting to learn how to make an LDAP lookup for computers and users I ended up with 442 computers in labels that should have had 10 or less.  Not good!

The problem comes because we have a lot of machines that aren't on all the time, or are permanently offline.  Even if I correct the LDAP label the machines that aren't on will not get removed from the label because they never check in.  There are two ways I've found, with the help of Support, to deal with this.  The first, which they gave me, is to delete machines individually from the group.  You can do this by the following procedure:

  1. Go to Inventory, look up the machine, and click it to open its details.
  2. Scroll down to Activities, and then open Labels, then click the Manage Associated Labels button.
  3. Remove the label and save.
  4. Wait until the page refreshes (30-60 seconds).

If there are a LOT of computers you have to remove from a label then this is not a time-efficient task.  The solution is to delete and recreate the label.  Ready?  Here we go.

How to Rebuild a Kace Label

  1. Open four tabs or four web browser pages, log in to the K1000 on each tab/page, and go to the following locations (one per tab/page):  Labels, LDAP Labels, Inventory, and Scripts
  2. Create a Test label.
  3. Examine the label and note any scripts that are assigned to it and whether an LDAP label is assigned to it.
  4. Assign the associated LDAP label to the Test label.

  5. Go to Inventory, Devices, and use the View By, Label, and choose the label.

  6. Select all the devices, then click the Choose Action drop-down and click on “Remove Labels”.

  7. Select the label (there may be more than one, only remove this one) you wish to remove, then click the Remove Labels button.

  8. If any scripts are assigned to the label, go to scripts, find the script associated with the label and remove the label from it – then wait a minute for the database to catch up.

  9. Delete the label.

  10. Recreate the label.

  11. Go to the Test LDAP label and assign it to the recreated label.

  12. Re-assign the label to the script.

Comments and questions welcome.

Be the first to comment

Redshift Renderer for 3dsMax

I am adding this for two reasons:
1) Redshift's installer is complete shite.
2) There appears to be NO information out there on how to install Redshift silently.

This is for version 2.5.51.

Specifically I run a render farm where this product is being used within 3dsMax 2018.
We use floating licenses.

The installation itself is simple enough:
installer_name.exe /S
xcopy "\\server\share\Redshift Renderer\redshift-licenseFile.lic" C:\ProgramData\Redshift\* /Q /Y /C /R

However this does not actually install any of the needed files with 3dsMax 2018.

copy /Y C:\ProgramData\Redshift\Plugins\3dsMax\2018\nt-x86-64\redshift4max.dlr "c:\Program Files\Autodesk\3ds Max 2018\Plugins\"
copy /Y C:\ProgramData\Redshift\Plugins\3dsMax\scripts\startup\* "C:\Program Files\Autodesk\3ds Max 2018\scripts\startup\"
copy /Y C:\ProgramData\Redshift\bin\redshift-core-vc100.dll "C:\Program Files\Autodesk\3ds Max 2018\"
copy /Y C:\ProgramData\Redshift\bin\OpenImageIO-1.6.17-vc100.dll "C:\Program Files\Autodesk\3ds Max 2018\"

This copies the required files into the proper locations.

Note that Redshift is only compatible with nVidia cards, so you need to limit your deployment to them.
Also if the nvidia driver is not new enough, this does not figure that out for you.
The jobs will fail.
And on those the only way I have found to figure that out if via running the install manually.

Tested on Windows 7 x64 machines exclusively.

Mike Kirda

View comments (1)

Basic Software Distribution Example

I've had a lot of positive feedback on my example of how I do a managed software distribution, so I thought I would share my instructions.  Feel free to contact me if you have any questions.

KACE Software Distribution

First Step is to creating a Software Distribution package is to gather up all the installation files required and zip them up into a since zip file.  Be careful the files are at the root of the zip and not in a folder at the root of the zip file (This could cause failures).

Save the zipped file to a location accessible when uploading to the KACE web interface.

Now, log into your KACE environment and pull up a current inventoried PC that already has that software installed.  Expand the Installed Programs field under Device Inventory.  Find the software and click on the hyperlink for it.  Please note that this must be the exact same version of the zipped package.

Under the Manage Operating Systems, ensure all OS versions you plan to distribute this to are selected (Note that with version 8 release of KACE, you can select entire OS Versions instead of individual versions as an option.)

Click on the Browse button, browse to and select the zipped file you have saved.

After selecting the file, change the Category and Threat Level as needed.  Click Save button when finished.

Navigate to Home>Label Management, then click Labels

Under Labels, click Choose Action and select New Manual Label.

Complete Name, Description and selections for Restrict Label Usage To.  Click Save when finished. Note: I start Software Installation Labels with SIL (Software Installation Label) for Best Practices

Navigate to Distribution>Managed Installations.  Under File, click New.

Configure Name, Execution; choose the software from the drop down options (Choose the one you uploaded earlier)

Note that with Version 8 you can choose Cataloged Software or Software from the Software list.  Your uploaded zip file will be associated under Software.

Now choose the installation commands.  Most often you will choose Override Default Installation to include switches such as silent installation.

Under Deploy, click Manage Associated Labels and select the label you created for this distribution and apply it.

Configure Notifications to give the user warnings and completion messages.

Configure Schedules as needed (What times it is permitted to install and how many attempts until it reports failed, etc.)  Click Save when complete.

Now, to have software install apply to devices, you will need to Apply the new Label to any device you wish to install it on.  After the device inventories next, it will install per configured settings.

NOTE: If device has a local KACE Repository, this may not work until the repository has obtained a local copy of this distrubtion (sometimes up to 24 hours)

View comments (1)

KACE MDM updates available

The Quest KACE team is happy to announce the public release of the Q4FY18 updates to KACE Cloud Mobile Device Manager (MDM). New features added to KACE MDM in Q4 include:

·       Personal vs. company devices: treat devices differently while still maintaining control over whatever bring-your-own-device (BYOD) policy you may have.

·       Improved role management: restrict enrollment and protect preset configurations.

·       Device policies and restrictions: set passcode and device restrictions to improve security while maintaining effective management and control.

·       Application management for iOS: deploy and remove managed applications on iOS devices.

·       Device configuration: allow for centralized configurations for corporate email and Wi-Fi access.


     Need additional information

KACE Cloud MDM product page.

KACE Cloud MDM datasheet.

Information on each product update can be found in the MDM Release Notes from the Support Portal or directly from the MDM product.

View comments (1)

KACE UserKon 2018 - Register before 1/31 and get $300 off

Click the link below to get more information on the promo, registration, and the conference:
KACE UserKon, 2018
Be the first to comment
Showing 6 - 10 of 3160 results