Help with batch script logging in K1000
This is my first post on appdeploy as the guys at Dell Kace were not able to help me. Currently, my request is being escalated. Kinda bummed as what I'm trying to do seems very simple, I just can't get it to work with the Kbox.
I have a batch file that checks to see if certain apps are installed. If they are installed, I uninstall them, then echo UNINSTALLED SUCCESSFULLY, else, I echo NOT CURRENTLY INSTALLED. The script runs perfectly, however I would like some accountability for each time it runs. When running from a command prompt, i can MyBatchFile.bat > log.txt -which lets me know which apps were uninstalled/not installed.
I am able run the batch file, then upload the log.txt, thru the Kbox, however, the log is blank. I've tried this so many different ways, i can't type them all out.
Here's what my OnlineKscript looks like:
MyBatchFile.bat is added as a dependency.
Task-1
Verify
1. run the batch file 'run.bat' which only contains: test.bat >log.txt
On Success
1. run the batch file 'test.bat' which contains the app code/uninstaller info
2. upload "C:\Program Files\KACE\KBOX\packages\kbots\47\log1000.txt"
That's it.. the script runs and does what it's supposed to do, the log file is uploaded, but it does not display any of the info I'm looking for.
Is there a better way to do this rather than build the batch file task-by-task into the a Kscript as recommended by Dell?
I have a batch file that checks to see if certain apps are installed. If they are installed, I uninstall them, then echo UNINSTALLED SUCCESSFULLY, else, I echo NOT CURRENTLY INSTALLED. The script runs perfectly, however I would like some accountability for each time it runs. When running from a command prompt, i can MyBatchFile.bat > log.txt -which lets me know which apps were uninstalled/not installed.
I am able run the batch file, then upload the log.txt, thru the Kbox, however, the log is blank. I've tried this so many different ways, i can't type them all out.
Here's what my OnlineKscript looks like:
MyBatchFile.bat is added as a dependency.
Task-1
Verify
1. run the batch file 'run.bat' which only contains: test.bat >log.txt
On Success
1. run the batch file 'test.bat' which contains the app code/uninstaller info
2. upload "C:\Program Files\KACE\KBOX\packages\kbots\47\log1000.txt"
That's it.. the script runs and does what it's supposed to do, the log file is uploaded, but it does not display any of the info I'm looking for.
Is there a better way to do this rather than build the batch file task-by-task into the a Kscript as recommended by Dell?
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
airwolf
13 years ago
Is there a better way to do this rather than build the batch file task-by-task into the a Kscript as recommended by Dell?
Not if you want to do it with the KBOX. Your goal is to run a script on a client, output results, and then upload those results to the KBOX. If the logs are uploaded to the KBOX but they are blank, it sounds like a bug to me.
Posted by:
bstadmin
13 years ago
Seems that as flexible as the Kbox is, there's got to be a way to do it. For 20K on a systems management appliance, you should be able to run a simple bat file and log the results somehow. I'll keep digging..
Posted by:
airwolf
13 years ago
20K for a systems management device is a bargain. SCCM would run you about 10-20 times that without an EA.
There may be another way to get information into the KBOX (I'm thinking custom software inventory), but I'm not sure exactly what you are trying to accomplish with the logs. KBOX is designed more for live data rather than historical data.
You can use KScripting to log what it's doing, but the KBOX will only show the last run. You should be able to replace your batch file with KScripting anyway, because you're just checking for the existence of software and uninstalling it.
There may be another way to get information into the KBOX (I'm thinking custom software inventory), but I'm not sure exactly what you are trying to accomplish with the logs. KBOX is designed more for live data rather than historical data.
You can use KScripting to log what it's doing, but the KBOX will only show the last run. You should be able to replace your batch file with KScripting anyway, because you're just checking for the existence of software and uninstalling it.
Posted by:
bstadmin
13 years ago
True (just checked and it was actually a little over 30k with node licenses) Anyway, no doubt the kbox was one of the best investments we've ever made.
So, i just read your scripting PDF and it looks like you are doing something similar with the very first example re: defragin' the C: drive. I'm going to try something similar where i just call for cmd.exe cd to the Kbot directory and run a command which runs the batch file and logs the output, then upload it.
(btw, the bat file is pretty long and checks for multiple versions of software, etc. and I just don't have the time to rebuild it all into a kscript)
Thanks a ton for your help.
So, i just read your scripting PDF and it looks like you are doing something similar with the very first example re: defragin' the C: drive. I'm going to try something similar where i just call for cmd.exe cd to the Kbot directory and run a command which runs the batch file and logs the output, then upload it.
(btw, the bat file is pretty long and checks for multiple versions of software, etc. and I just don't have the time to rebuild it all into a kscript)
Thanks a ton for your help.
Posted by:
airwolf
13 years ago
The example in my Scripting article only uses that method because it's the only way to get a log of something that KScripting can't do back up to the KBOX. In your case, KScripting can perform uninstalls (you can setup dynamic labels and scripted uninstallations to automate deployment). I know it'll be a headache to "rewrite" the batch file as a KScript, but that's the most effective solution, in this case - aside from KACE fixing the bug causing blank logs.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.