I don't have a lot of time to write this post, but I wanted to get it out there.

If you noticed, the K1000 uses the Local system account to install applications and run scripts. Sometimes you get a successful test using a user account to test something, then you go to push it via a script or MI, and it fails (might need access to a share or network resource that requires authentication). The LS account doesn't have any permissions to servers and other devices, so the install or script fails.

If you need to test installing something as the local system account, download psexec (google it) and run:

PSEXEC -i -s cmd.exe

This will get you a command prompt running as the local system account. Anything you run from that will run as the LS.


I have used AutoIT (free and cool) to build some macro type installs (clicks buttons and answers prompts) for older apps that don't have silent installs, or require input. It requires an interactive session since it pushes buttons and "interacts" with the desktop (and since pushed via K1000 running as local system). You can use PSEXEC for the same thing.

Try this in a batch file to make it work (and then run that batch file as your Managed Install):


PSEXEC /accepteula -i -s cmd.exe /c & CD %WORKING_DIRECTORY% & <Your AUTOIT Script>.exe

There may be more creative solutions out there, so if there are, I would like to know.
0 Comments   [ + ] Show Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.


it's an important step. Some others for you.

Answered 10/04/2011 by: GillySpy
Seventh Degree Black Belt

Please log in to comment
I use AutoIT to embed domain credentials with local admin privileges if something needs network access during installation. AutoIT is a great complement to the K1000 and K2000.
Answered 10/04/2011 by: airwolf
Tenth Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity