/build/static/layout/Breadcrumb_cap_w.png
06/11/2019 153 views

Hi

Sorry if this is a dumb question, but I just started with this and I can't figure out what I would use as an inventory rule when all I'm doing is launching a batch file that launches an exe.  I have a program that I created a pack for.  The issue with it is that it requires the user to enter all of their information in the license manager before they will get a license.  I wanted to make sure the license manager launches after everything is installed so the users can just enter it right away.  The issue is that I have no idea what to use as an inventory rule. Any ideas? Or is there a better way to do this?

Thanks

2 Comments   [ + ] Show comments

Comments

  • I'm not entirely sure what you are trying to accomplish. You want to launch a license manager after software installation is complete? How is the software being installed? Via a managed install or a script?

    Generally, custom inventory rules are used to detect software or other settings which KACE doesn't natively support. They also run as system, so interacting with the logged in user is less than ideal (plus they will run at every inventory). So you could use an inventory rule to capture data from the computer, but not to prompt the user for information.
  • I understand that part of it. Basically, the problem I have is the way this software is licensed. Once the software is installed the user or someone needs to launch the license manager, enter all of there information and it will then send an email to the admin that will then either approve or deny their license.

    I have a managed install that installs LabVIEW and then drops the .ini. I'm just trying to make it a little easier for PCSupport, if possible. I made another "pack" to attach to the same label that launches the license manager after it's installed, but it will continue to launch it every time the inventory updates unless the label is removed from that PC. I guess I could have a "decoy" text file drop with the batch file that it will then look for. I was just curious if someone knew of a better way of doing this or if there was a way to get this portion of the pack to stop launching over and over again every time it updates.
    • Instead of using a custom inventory rule, create a KACE script that launches the license manager. You could then use a task chain that installs the app with the managed install and then launches then runs the script.
      • Thanks for the feedback. I hadn't thought about that. I have only been using Kace for a couple of months and have had next to nothing as far as training goes. I've been simply trying to find old packs that look like something similar to what I want to do and altering them to work. I will have to play around with the scripting side and see what I can figure out there. Thanks again for the help.

There are no answers at this time