Software Deployment

Did you register for the corporate deployment MSI from Adobe?

http://www.adobe.com/products/players/fpsh_distribution1.html

If so, the mms.cfg setting is all you should need...

Cheers,
Rob.

Yes both the old and the new one but that didn't work. It only work when I have already installed the msi file, then it don't ask for updates when you run a website using Flash.
But when I install the msi on a computer and a newer version is out there I still get the update message even if the cfg file is there.

ORIGINAL: MSIPackager

Did you register for the corporate deployment MSI from Adobe?

http://www.adobe.com/products/players/fpsh_distribution1.html

If so, the mms.cfg setting is all you should need...

Cheers,
Rob.

Hmm guess I've not seen that as we package in a pre-production environment with no internet access.

Surely though when it comes to deployment time (Group Policy / SMS or whatever) it will be done under the system account which (obviously) wouldn't have internet access anyway?

Unfortunately our environment have internet access when installing msi files.[:(] So I hope to find some solution to it[:)]
ORIGINAL: MSIPackager

Hmm guess I've not seen that as we package in a pre-production environment with no internet access.

Surely though when it comes to deployment time (Group Policy / SMS or whatever) it will be done under the system account which (obviously) wouldn't have internet access anyway?

Well you say you've set the ISCHECKFORPRODUCTUPDATES propery to 0 which hasn't helped... How about you try removing the following 2 CAs:

CheckForProductUpdates
CheckForProductUpdatesOnReboot

They sound suspicious [;)]

Cheers,
Rob.

Here how I did it :
http://itninja.com/question/does-mms.cfg-work-with-flash-9.0?&mpage=1&key=&#37977

Thanks. I was thinking about that Custom Action and now I tried to delete both but it still gave me the update message on install. Seams to be a hard one to get around...[;)]

ORIGINAL: MSIPackager

Well you say you've set the ISCHECKFORPRODUCTUPDATES propery to 0 which hasn't helped... How about you try removing the following 2 CAs:

CheckForProductUpdates
CheckForProductUpdatesOnReboot

They sound suspicious [;)]

Cheers,
Rob.

Well then I'd setup verbose logging and have a look through that - it can't be that hard to track down... [:)]

Thanks. I will try that also. I thought that solution was the same as the mms.cfg file but for home users.[;)] But Ill give it a try.
ORIGINAL: darkfang

Here how I did it :
http://itninja.com/question/does-mms.cfg-work-with-flash-9.0?&mpage=1&key=&#37977

This was a hard nut to crack. I have tried the old Regmon and Filemon and I only monitoring the FP_AX_MSI_INSTALLER.exe and the install_flash_player_10_active_x.msi.
But I could not see any actually difference when I installed the new one that didn't ask for a update and the old one that did.
I also tried to use Ultra Network Sniffer but I'm a newbie on that one so the only thing I manage to se was that my computer was connecting to some IP addressees.[&:]

The verbose msi log didn't show so much either. One thing that look a bit suspicious was
MSI (s) (A0:68) [17:22:40:863]: PROPERTY CHANGE: Adding UpdateStarted property. Its value is '1'.

And
MSI (s) (A0:68) [17:22:41:029]: Executing op: ComponentRegister(ComponentId={ED69B7BD-45A0-40C5-81A0-DCC1CFEBC694},KeyPath=02:\SOFTWARE\Adobe\Shockwave 11\AutoUpdate\,State=3,,Disk=1,SharedDllRefCount=0,BinaryType=0)

And
MSI (s) (A0:68) [17:23:08:348]: PROPERTY CHANGE: Deleting UpdateStarted property. Its current value is '1'.

I tried to set the HKLM\SOFTWARE\Adobe\Shockwave 11\AutoUpdate to "n" instead off "y" in the msi but it seams as the exe file overwrite it.[:@]
I am going to try and se if I can manually set the regvalue and se if that makes any difference[:D]