Script deployment as user & dynamic use of Custom Attributes

Support
Log in to reply
  • J

    I'd like to express my admiration for this product, which I installed out of curiosity — and I’m really impressed!
    I have a few questions I couldn’t find answers to in the documentation:

    Software deployment – How can I install software under the currently logged-in user (so I don't need a password), rather than under the SYSTEM account?

    Custom Attributes – Is it possible to use the Custom Attributes assigned to a specific computer as arguments in a script? For example, I’d like to store license keys for individual applications in these attributes and use them during installation.

    I’d love to have the ability to populate a Custom Attribute via a script run on the computer.
    For example, for detecting TPM presence, I could use a PowerShell script like this:

    $hasTPM = Get-WmiObject -Namespace "Root\CIMv2\Security\MicrosoftTpm" -Class Win32_Tpm  
if ($hasTPM) { "True" } else { "False" }

    and then I would be able to use this Custom Attribute as argument or in Reports.

    0
  • T

    Hello,

    If you set the policy trigger to login, it will run as the current user. You can also set a module to use an impersonation account where the system account will run the installation as that user, but that's meant more for applications that won't install with system, you would probably use just a single impersonation account.

    The custom attributes cannot be used in the client scripts, currently they can only be used in imaging scripts, but I can add this to the next release.

    You can use a custom inventory script to collect the information from your powershell script which can be used in reports but cannot be passed to a script.

    0