/build/static/layout/Breadcrumb_cap_w.png
03/22/2019 142 views

Hello my question is the next.

After installing an application through script with administrator privileges, I need to run it with the account that started the session, which is a normal user of the domain.

I understand that I could run a new script for this task but it has to be in the same script that generates the installation of the application.


the client is windows 10


Thank you for your answers

6 Comments   [ + ] Show comments

Comments

  • so is it a local or domain user? The title says local account and the text says normal user of the domain
  • sorry,
    they are Domain users
  • So you want to install an application, and then open\run that application with a domain user....

    Is that the same user who installed the application?

    Maybe just task 2 inside a script, and point to launch a program, and select the software's EXE file.

    Now if the user who installed the Application is different, a second script to launch the application is needed, then use Task Chain to link those scripts
  • You might be able to use WMI impersonation to launch the program after installation. Or generate a temp scheduled task to launch the program with the logged in user after installation.
  • >it has to be in the same script that generates the installation of the application.
    Why does it have to be?
    • must be in the same script since the program that executes after the installation must be executed with the account that starts secion
  • I still do not solve it, but what I do for a while is to execute a second script after checking if the program was installed

All Answers

0

Why not simply install with admin rights, as normal, and use one of the many tools around to get the logged-in user's username and SID (you'll need the SID if you need to write to the user's registry hive, of course)?

Answered 03/26/2019 by: VBScab
Red Belt