Hmmmm, wonder if this is the same problem I had.
On Mar 17, 2010, at 11:57 AM, Paul Austin wrote:
At one site running 7.2, had to perform a true-up on Adobe Creative Suite licenses. So I had a policy to run the uninstallCS4 script from the Resource Kit, scoped to a static group of non-authorized users (named the policy with a 2 prefix so it would run first when a machine was seen), and do a recon when done. I also had policies which applied to a Smart Group of users who didn't have Adobe Acrobat Pro 9.3.0 or 9.3.1, to cache and the updates (by actually deploying a new Adobe Acrobat Pro folder).
Saw this happening on a few machines, where the 2uninstall policy would run and recon, a couple of other ones, then here comes the "cache and install Adobe Acrobat Pro 9.3.x" script. Uh, I just uninstalled the Creative Suite, at least 4-5 minutes have passed while running other policies (which may have also had recons as part of the policy), I don't want to re-deploy Acrobat Pro (which won't run anyway because of the licensing being removed as part of the uninstall). It seemed that the smart group wasn't getting updated quickly.
I ended up renaming the "cache and install Adobe Acrobat Pro" update policy with a z in front of the name so it would run last among all of the pending policies. Seems to have worked around the problem, but why I should have to is unclear to me...
--Robert
