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
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)
Please log in to answer
Posted by:
cblake
15 years ago
Posted by:
g13net
15 years ago
Posted by:
jkatkace
15 years ago
Posted by:
g13net
15 years ago
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
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
15 years ago
Posted by:
airwolf
15 years ago
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)?
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.
so that the conversation will remain readable.