Executing script using Computer Manufacturer condition doesn't work
Hello everyone,
This is my first post. I am using Altiris DS 6.9 with Service Pack 2. I am attempting to setup a job that executes a vb script but only on IBM physical hardware (not HP or VMWare, which are the other two platforms in our environment). To do so I've setup the Default condition to be blank, and created a custom condition as follows:
Field - Computer Manufacturer
Operator - contains
Value - IBM
When I test the script against a server that I know shows "IBM" for Manufacturer property, nothing happens. The job is executing but stays "stuck" that way, at least for several minutes when I have to manually delete it to stop. There is no evidence anything has exec'd on the target system.
I have already tested this job manually using "Default" condition to run on everything, and it works fine. This only happens when I test my new custom condition as described above. What could I do to troubleshoot this? Does it make a difference if I place IBM in quotation marks ("IBM") for the Value field?
Thanks, I look forward to participating in the forum.
Additional detail
Some more notes that might be helpful:
I tested with quotes around "IBM" and it made no difference.
The Task progress and Status Detail remain blank when executing.
OS? AClient or DAgent?
What OS is the target computer? (i.e. XP, 2003, Vista, 2008).
If you are using XP or 2003, are you using AClient or DAgent? Would suggest that you utilize AClient if possible as I have had problems in the past with the DAgent not always completing jobs or staying connected.
Also, irregardless of whether or not you are using AClient or DAgent, make sure that the client/agent version matches the DS version or that will also cause a problem.
If you double click on the
If you double click on the computer and check the hardware tab, what is the manufacturer. Maybe you can post the screenshot. Also I didn't think you could have a blank default condition. Don't you need a Run Script with a REM at a minimum?
Correct
Good call Brandon. I believe you are correct. A simple run script with the following code would work: "REM DEFAULT PLACEHOLDER"
Computer Product Name
I usually use Computer Product Name to diferentiate between VMWare virtual servers and physical HP servers.
And I always use a REM DO NOTHING for the default part. This will ensure that I do not get prompted that I am deploying a job with a condition that has no tasks assigned. And furthermore that if I should run the job on a different server/computer nothing will happen.
In case you have both Windows and Linux/VMWare machines I would also reccommend that you use this as a condition. Trying to boot a Linux machine into Windows is a no go :)
________________
/mlogan
AClient needed restart
So, it turns out my AClient was hosed and I needed to restart the service. We also rebooted our Altiris DS server today. The combination of these resolved my issue. Thanks for your suggestions. I did find the "REM Do Nothing" script to be very helpful for ensuring the job is bypassed properly with green checkmark when my physical condition does not apply.
Would you like to reply?
Login or Register to post your comment.