/build/static/layout/Breadcrumb_cap_w.png

Package wont deploy from AD-policy

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)

Grtz,
Stefan

0 Comments   [ + ] Show comments

Answers (1)

Posted by: WiseMonkey3 19 years ago
Senior Yellow Belt
0
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.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ