1 of 1 people found this helpful
Make sure you aren't just looking at the error code shown in the scheduled task chart, make sure you find the machine affected and see if there are any descriptions for the error. Often an errorcode has been translated.
LANDesk has the return code mapping feature that tries to do what you are asking for with templates for different types. The issue with a batch file is that LANDesk really is only responsible for copying over the batch file and any associated files and then launching it. If something goes wrong with those bits LANDesk is normally good at telling what went wrong (there are exceptions but not too many).
If something goes wrong in the batch file, then actually the error code LANDesk knows nothing about because it is simply passing back whatever you called gave to it as an errorcode. You can right click the machine to see if a log uploaded, but if not then you will need to investigate the affected machines and try launching the batch file manually to see if it is an issue somewhere in your script.
If you write scripts and control your own errorcodes by making decisions based on success or failure then you can use your own return code template, or perhaps look st using sdclient /msg="your message here" to send an update based on where the machine got to in your batch file.
I wish there was a magic answer to this one but it does sort of depend on what you are trying to do and whether it is LANDesk or your batch file that went wrong.
MarXtar Ltd/MarXtar Corporation
LANDesk Expert Solution Provider
The One-Stop Shop for LANDesk Enhancements
Update - New Stand-Alone State Notifier Console for Service Desk Operators
Update - State Notifier now detects machine and user Idle states
Update - WoW & State Notifier now integrate for even more functionality
Thank you for your detailed reply, Mark. It makes sense that some errors Landesk just would not be able to report accurately if it's not an actual problem with Landesk deployment but rather a problem with the batch file or script being deployed. However, my frustration is that I will get a batch file to deploy succesfully to many machines but there are always those few that seem to generate cryptic error codes that I ahve a tough time deciphering. It just doesn't make sense to me why a deployment will work for a big group of machines but a few have issues.
Is there a way to access the client log files remotely through the Landesk console? This might make things easier for me when I do have to check log files for errors. Sometimes I have to check the vulscan logs or other client side logs, and I want to be able to do this without having to remotely connect to the machine or have the machine physically in front of me. We used to have a c: drive share turned on for client workstations so I could access files that way, but I believe that has been turned off now for security purposes. I wasn't sure if Landesk had an easy built in way to do this, or if I just have to resort to the old fashioned methods to be able to examine the logs. Again, I apologize if this is common knowledge that I am failing to find on my own.
Thank you for your help! It is greatly appreciated!