Script always running. It doesn't report "failed" or "completed".
I am trying to use K1000 to push the updated anyconnect "client" and "start before windows" packages to end users in my company. I am doing this with a script that unzips the two MSI and a batch file I created to the client machines. Then kace runs the batch file that silently installs both packages and throws up a warning about the reboot (the MSI for "start before windows" requires a reboot). When I click "run now" everything works fine except the "Run Now Status" for the script doesn't report failed or completed it just shows it as running even though it is completed.
The computers that are off do report a fail when I click "Run Now", but the computers that are on get the software and reboot but report as "running" in kace. Does anyone have any suggestions on how to get the computers to report back? I believe it is because the computer reboot after installing the silent package that wants a reboot. Our kace can connect over the internet, so it isn't because anyconnect is down for the update. Here is the script and batch file I am using.
echo msgbox "Computer will restart, save your work, then click OK." > "%temp%\popup.vbs"
This is the kace script that call my script:
Thanks for your help!
Answer Chosen by the Author
I've had this problem too. Like you mentioned, I'm fairly certain it has to do with the computer rebooting. Here is my workaround... I don't know if this is proper, but it works for me.
Add a New Task
Add a new Verify - check for a file or folder that should exist after install
Add a Remediation - Select "Always Fail"
What happens is: if the Verify doesn't find the file/folder you specified, then remediation will always fail and it will then show up as Failed in the Run Now Status page. You'll probably need to instruct your msi install to not reboot (with /norestart) and then do the reboot in a separate task after you've verified the install.
Here is screenshot for reference.
Answered 09/01/2016 by: getElementById
Please log in to comment
log in to commentPlease