Cannot Install Adobe Flashplayer 9.0.16 Using SMS 2003

Question

We are using SMS 2003 in an enterprise environment.
We have been unable to install Flash Player V9.0.16 using
SMS.
We had the same problem with Flash Player V8.0.24, and
finally gave up.
All other SMS packages we create install without difficulty,
including applications such as Adobe Reader 7x, MS Office 2003,
etc.
The error generated by SMS is:
The program for advertisement "MNG20107" failed ("MNG00099" -
"Adobe Flashplayer 9.0.16").
A failure exit code of 1 was returned.
User context: NT AUTHORITY\SYSTEM
Possible cause: Systems Management Server (SMS) determines
status for each program it executes. If SMS cannot find or
correlate any installation status Management Information Format
(MIF) files for the program, it uses the program's exit code to
determine status. An exit code of 1 is considered a failure.
Solution: For more information on the exit code, refer to the
documentation for the program you are distributing.
Attempts to search on the internet for an understanding of
this error have been unsuccessful.
Basically, we are looking for input from other SMS Admins who
have had problems installing Flash Player 9 with SMS, whether they
fixed it or not.
Hopefully, someone can provide some insight as to the nature
of the failure. I don't think its really SMS, as it generally
pushes other packages just fine. Only Flash seems to refuse to play
nice.
I am not interested in using Group Policy to push this
package, please start a seperate thread to have that discussion.
Thanks

Answer 1

I had the same question about what accounts were used in SMS
with advanced security. I was having a problem loading some
bluetooth drivers. Here's the reponce I got from an SMS list.
Do you have access to SMS R2? You can now use the custom
update tool for Adobe Flash.
You are correct about the Software Installation Account, it
is only for the legacy clients.
What kind of installer is the Bluetooth software using?
InstallShield?
If it is InstallShield (MSI based), I have had many problems
with InstallShield packages (MSI based) running under the SYSTEM
account, but it runs fine under my user account (which has Admin
rights). If this is the case take a look at this link:
http://community.macrovision.com/showthread.php?t=117720&page=3&pp=6
The information I'm refering to in the link is the following:
"Your probably referring to one of the many threads that
MichaelU and I had on this subject.
BTW I'd never read the document above. I've always followed a
simple approach with each release of InstallShield.
1) Install InstallScript MSI and use DCOMCNFG to determine
the AppID of the offending DCOM server.
2) Edit the ISSCRIPT.MSI to remove the RunAs registry value
of the AppID.
3) Edit the ISSCRIPT.MSI and add an entry to the
RemoveRegistry table in case the value has been previously seeded
out in the wild by a different install using the same version of
InstallShield.
4) Add the new MSI to my build environment"
Thanks,