I noticed something the other day, after I had updated some packages. If I replaced a zip file in a post-installation task, zip file had the same name, but the exe that was run in the zip file changed its name the task would not run. The post install task was verified that the command line was updated to reflect the new exe. All RSA's were completely synced, but it still did not run. I think this is a bug, or the kbox 2000 doesn't compare hashes or dates to realize the file has been replaced. Has any one else experienced this? I would just make a new post install task, and eliminate the problem all together, but it links to around 20 scripted installs, and I have around 10 tasks that get updated frequently.
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


This content is currently hidden from public view.
Reason: Hidden by Admin
For more information, visit our FAQ's.