SMS 2003 pre-check deployment
We are useing SMS 2003 and Wise.
Still learning on both but wondered what the easiest method of haveing a package check if a machine already has the package going out.
Example:
Removal of Zenworks was done by means of a batch file and was unable to identify if Zen already existed, so it would attempt to remove and fail thus reporting back to SMS a fail.
someone mentione scripted packages, not sure what this is
Cheer in advance
Still learning on both but wondered what the easiest method of haveing a package check if a machine already has the package going out.
Example:
Removal of Zenworks was done by means of a batch file and was unable to identify if Zen already existed, so it would attempt to remove and fail thus reporting back to SMS a fail.
someone mentione scripted packages, not sure what this is
Cheer in advance
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
yarborg
17 years ago
Scripted packages usually means using Wise or another type of scripting language to do the check before hand. This means the package actually gets kicked off on the client, the Wise installer package checks some reg keys or files to determine if Zen is there and responds accordingly. If it is then it kicks off the uninstall. If not then it exits with a 0 or 1 or whatever you choose to let you know that it was successful.
I would also agree that this is the best method. Microsoft may recommend using an SMS collection to add only those machines that actually have the Zen.exe (or what ever it is called). This is usually too tedious of a task though if you do deployments often.
I would also agree that this is the best method. Microsoft may recommend using an SMS collection to add only those machines that actually have the Zen.exe (or what ever it is called). This is usually too tedious of a task though if you do deployments often.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
