Scripted Install with Windows 7

I have a scripted install setup which is very basic. All it does it call a batch file to run the msi setup for our anti-virus. On Windows XP machines, I do a run now on the script and it works.

I am in the process of testing Windows 7 in our network. When I pushed the script to my Windows 7 box, the script will not run. When I check the KACE folder I see that it pushed the batch file to the Windows 7 box. If I run the batch while on the box, the install works.

Any ideas as to why the script doesn't run when I push the install?

Thank you

0 Comments   [ + ] Show comments

Answers (6)

Posted by: cblake 13 years ago
Red Belt
My suspicion would be that there's an error that isn't being displayed, or the UAC is halting the install. Can you run the batch manually and detect any such behavior?
Posted by: g13net 13 years ago
Senior Yellow Belt
I thought it was UAC so I disabled it and no luck.

When I run the batch manually it works fine.
Posted by: jkatkace 13 years ago
Purple Belt
I assume you're on the 5.0.25648 agent, which is the one compatible with Windows 7.

What do the scripting logs show?
Posted by: g13net 13 years ago
Senior Yellow Belt
yes I have the most recent agent.

Started: Nov 17 2009 11:46:26 AM
Finished: Nov 17 2009 11:46:26 AM
Elapsed Time: 0 seconds
Status: in state 'verification_success'
Status Log START
FINISH (in state 'verification_success') Activity Log Launching program: C:\Program Files\KACE\KBOX\\packages\kbots\65\kace9932.bat
Posted by: dtuttle 13 years ago
Purple Belt
put some debugs stuff in you batch file... see if it even executes... (IE redirectors, or copy text files)
Posted by: airwolf 13 years ago
Red Belt
Since it works in XP, the first thing that comes to mind is UAC - or possibly something that acts differently in Windows 7 than in XP. Dale's suggestion of writing some debugging into the script is a good idea. Keep in mind, the KBOX agent runs everything under the local SYSTEM account, so the fact that it works when you run it manually probably means it's an interactivity issue or an authentication issue.

Are you installing the MSI by calling it directly (i.e. - install.msi /passive /norestart) or are you passing the MSI to msiexec.exe (i.e. - msiexec.exe /i install.msi /passive /norestart)?
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

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

Sign up! or login


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