/build/static/layout/Breadcrumb_cap_w.png

How do we create a KACE 1000 login script that runs as the current user?

Background:
    We are a Windows shop. Windows 7 Pro 64-bit and Windows 10 Enterprise 64-bit.
    We currently use Symantec Management Console [formerly Altiris] to run two batch scripts at every login. Each script makes changes to the system (one running elevated) and the current user's profile (one running as current user) after their very first login. Changes are various, but include registry edits and application launches (for context menu setups). We have these scripts create a registry key to prevent re-runs.
   

Going forward:
    We recently started using a KACE 1000 in our environment, and we really want to ditch SMC entirely and start using KACE for all our managed scripts. We have successfully re-created the elevated script (since "login" scripts in KACE 1000 automatically run as the local System account). However, we can't figure out how to make a "run as current user" login script in KACE.
   
    If it makes any difference, we need this to work for either someone sitting at the local console or using a RDC connection for their first login.

    We have read existing forum posts, and web searched the heck out of this topic. The only "resolved" suggestions seem to end with "use Task Scheduler" or "use a RunOnce registry key", which we'd like to avoid for a variety of reasons, if possible. In short, we want to avoid making it a purely local configuration. We want to manage it all using KACE scripting.

    We would also like to avoid using online scripting since those only trigger on timing, and we don't want to have to run a script every few minutes just to catch a first time login.

    Has anyone had any luck building a working KACE 1000 login script that runs as the *real* current user?

2 Comments   [ + ] Show comments
  • Have you worked this out? I am also having troubles getting a script to run at login and do so as the current user - DLCurtis 7 years ago
  • I ended up using a KACE script to deploy a Windows Active Setup configuration to our systems. It's not pretty, but it does work and it is good enough for what we needed. I do wish KACE would incorporate a "Run at logon" feature. I'd like to leverage KACE more, but setting up Active Setup via KACE, just to get something to trigger at login, is a bit too much of a PITA to use it for simple scripts. - Immo 6 years ago

Answers (2)

Posted by: SMal.tmcc 7 years ago
Red Belt
1
add the code to the default users run once key and that will only run for a new user without a existing profile.  The k1000 can do this via a script or even an Managed Install.

Comments:
  • you can use the k1000 to modify the default profile. - SMal.tmcc 7 years ago
Posted by: DLCurtis 6 years ago
Purple Belt
0
Have you worked this out? I am also having troubles getting a script to run at login and do so as the current user

Comments:
  • I ended up using a KACE script to deploy a Windows Active Setup configuration to our systems. It's not pretty, but it does work and it is good enough for what we needed. I do wish KACE would incorporate a "Run at logon" feature. I'd like to leverage KACE more, but setting up Active Setup via KACE, just to get something to trigger at login, is a bit too much of a PITA to use it for simple scripts. - Immo 6 years ago
 
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