Hi, I am new to "trying" to administer our K1000. All of my systems reside in OU's based on system name/IP Address, "default" OU is for any system that pops in that doesn't fit the criteria/label to automatically go into one of those specified OU's. When I am logged in through the admin account, the only OU that has the "Scripting" option is the "Default" OU, but I have no devices in this OU. I am trying to a force check-in from the scripts folder and there are no devices to choose from, and if I type the device name "No matches found" - 1) is the "scripting" option only supposed to be available in 1 Organization? 2) if yes to question 1 - how do I look up the machines I want to force inventory on? 3) if no to question 1 - why is it not showing up under the other organizations?
0 Comments   [ - ] Hide Comments


Please log in to comment

Answer this question or Comment on this question for clarity


scripting should be in all orgs and independent of content from all other orgs.  Think of each org as a mini kbox, all the features should be available in all the orgs.

Most likely is a rights/role issue  Insure the user is an administrator in the orgs, that the "administrator" roles are setup and assigned properly in each org

Answered 04/06/2016 by: SMal.tmcc
Red Belt

  • I am signed in under the admin account - and looking at the Roles for Administrator, like your screen shot above shows, when I am in the default OU, under scripting I see the option to All Write, All Read, All Hide, or Custom. But when I look at the roles under any of my other OU's my options for Scripting change to All Hide, or Custom. But when selecting Custom, Hide is the only drop down option. The write option is not even available.

    The write option is available on those other permissions: Security, Distribution, Assets, etc...but for some reason not the "Scripting" permission

    How do I get that write option to appear? I don't see any different settings in place that make it different from my default OU.
    • you need to login as your system admin (the one you created when you setup the kbox) go to those other orgs and modify the admin roles.
Please log in to comment