It will do that if 8.1.2 isn't marked as an upgrade over 8.1.1.

[EMAIL PROTECTED] wrote:
> Acrobat has found a new way of being a PITA, but it's probably because of 
> something subtil in my GPO configuration...
> 
> I'd asked the group about leaving the old GPO for Acrobat (which installed 
> 8.1.1) when 8.1.2 came out.  I was told I could leave the 8.1.1 as is, and 
> the system would apply the newer one.
> 
> WELL, when users re-boot, it seems the system tries to apply both versions 
> (whether or not they've already been applied).  Sometimes it installs 
> 8.1.2 first, then attempts 8.1.1.  (That seems to result in no Acro reader 
> at all.)  I think I've deleted the 8.1.1 GPO.
> 
> HOWEVER, users still have to sit and watch in annoyance as a re-booted 
> machine once again goes through the 8.1.2 installation process.
> 
> Where in the network is the "leave it the $#*& alone!" setting for once a 
> GPO has been applied?

-- 

Phil Brutsche
[EMAIL PROTECTED]

~ Upgrade to Next Generation Antispam/Antivirus with Ninja!    ~
~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm>  ~

Reply via email to