Has anyone had problems running batch files to install applications?
I have a script and it works like a charm locally but when I upload to kace and try to use it nothing happens. Here's my script incase something could be missing.
rem taskkill /F /IM iexplorer.exe
rem taskkill /F /IM iexplore.exe
rem taskkill /F /IM firefox.exe
rem taskkill /F /IM chrome.exe
rem taskkill /F /IM javaw.exe
rem taskkill /F /IM jqs.exe
rem taskkill /F /IM jusched.exe
msiexec.exe /x {26A24AE4-039D-4CA4-87B4-2F86417009FF} /qn
rem taskkill /F /IM iexplorer.exe
rem taskkill /F /IM iexplore.exe
rem taskkill /F /IM firefox.exe
rem taskkill /F /IM chrome.exe
rem taskkill /F /IM javaw.exe
rem taskkill /F /IM jqs.exe
rem taskkill /F /IM jusched.exe
start /wait msiexec.exe /i jre1.7.0_11.msi /qn
pause >nul | set/p "=The Update is complete! Press Any Key To Close This Window"
Answers (3)
rem taskkill /F /IM iexplorer.exe
rem taskkill /F /IM iexplore.exe
rem taskkill /F /IM firefox.exe
rem taskkill /F /IM chrome.exe
rem taskkill /F /IM javaw.exe
rem taskkill /F /IM jqs.exe
rem taskkill /F /IM jusched.exe
rem taskkill /F /IM iexplorer.exe
The above lines will not do anything.. It will just show remarks...
By the way.. What is iexplorer.exe???
If you remove the word "rem" from each line then it will kill those process.. but it is not a good practice..
You should not terminate these generic processes forcefully as you like..
End user may do his critical work on any of the above processes.. If you terminate just like that all his work will be gone
Coming to uninstallation and installation section..
You are using /qn switch which will suppress basic ui as well.. if you want to check something, firt check with /qb as a trail.. If it goes without any issue then try with /qn
I nearly did all of my deployment via batch files attached and used with Managed Installations. There are a couple of things to keep in mind:
Always test the batch script outside of the K1. If the install doesn't go as planned, take the silent switches out and see what's going wrong.
Make sure the client computers have access to the files called in the batch script. I noticed that your script has the following line:
start /wait msiexec.exe /i jre1.7.0_11.msi /qn
Are you packaging the MSI in with the batch script using something along the lines of a zip file? If you are using a network share be sure to include the path to the share and also ensure that your client systems have access to said share.
Also as jagadeish said those REM lines are remarking out the lines so they are not doing anything. That's an awful lot of processes to kill so you might consider running the script while no user is logged on.