Hi there,

I've made a few packages, which all work if I double click them. Now I'm testing them as well with auto-installing through AD-policy.
I've put all my packages in the same directory (a sub dir for every package). I've added them in the correct part of the AD to deploy on one test computer.

The problem is that some packages are installed without any problems, and some others are not even found or tried. It totally ignores them, and I really don't know why.
Every package is build the same way (wininstall 7.5), they are all relative simple programs, and I really don't know why they are not installed, when some other packages are.

Anyone got a few tips that might help?
All Os's are XP
AD is from server 2003
Installation is from 1 workstation to another using a share (everyone full control)

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


The quickest way to see what happened to your msi on the machine is with the event viewer.
It will tell you in the Applications event about any ad deployed apps.

You can also turn on MSI logging, for machine assigned apps look in the Windows\temp folder for the logs & in the users profiles temp for published apps.
Answered 08/05/2004 by: WiseMonkey3
Senior Yellow Belt

Please log in to comment