Scripting Question


10/07/2014 1736 views
Hello all,

I hope that you can answer a quick question.

I am trying to figure out if the API will allow us to just update the "USER_FULLNAME" of a computer system buy using the computer name not the KUID.

The system would have the Agent installed on it already.  We would like to trigger this update when we setup\remove users in our AD and are hoping that we can do this via the API and PowerShell.

Thanks for the help.
0 Comments   [ + ] Show comments


All Answers

If you force an update on a machines inventory it will pull the current logged on users name into kace.  Otherwise wait for the cycle to run on its own.
Answered 10/07/2014 by: SMal.tmcc
Red Belt

  • Then this will also update the Owner of the computer as well? From the documentation it states:

    User Logged - The user currently logged in to the device. This entry includes the user name and the domain to which the user belongs.

    User Fullname - The full name of the user who owns the device.

    Last User - The name of the most recent user who logged in to the device. Some devices might have multiple users.
    • yes

      If you want to set some static info about this machine you can enforce registry settings to populate what shows in the system description. We place the owning department there on our machines by using scripts to enforce registry settings
      • Well is KACE is going to update the owners of the computers based on the logged in user then I guess there is not point in reinventing the wheel.
        Thanks for the help.
      • it will based on your inventory cycle.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

View more:


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ