Flash deployment issues
Ok, I have created a distribution to deploy flash updates to all my PCs. Sometimes it works no problem, but a lot of times the Flash install does not work. Doesnt matter if I use the EXE or MSI file to deploy flash. I see that the packages gets copied to the DOWNLOAD folder or KBOX, but after a split second the package is removed and no errors are reported. I can be logged on to the machine as a domain admin will full rights over the PC and the install does not happen. I can then, while still logged on as a domain admin with full rights, update flash manually while remotely logged on to the machine.
Not sure why Flash is such a nightmare to deploy and keep updated. All the other packages I created work great without problems.
Ideas?
Thanks
Not sure why Flash is such a nightmare to deploy and keep updated. All the other packages I created work great without problems.
Ideas?
Thanks
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
dunnpy
13 years ago
Is this a Package Development question, as that is where you've posted this question, or a KBOX deployment question - which has it's own fora on AppDeploy?
If you're distributing Flash Player for an organisation then you need to sign a distribution agreement with Adobe - link here.
You will then be emailed a link to download the installer, and the MSI version is the one best suited for customisation/deployment for KBOX.
You would then customise the MSI with an MST file, to set your own standards that identify this as a 'managed' package - disabling updates etc. (see Package Knowledge Base entry for Flash on this site), 'cos you don't want your users updating this themselves, or being prompted to download the newest version.
You first step in troubleshooting your issue would be to specify a log file for the MSI installation on your commandline in KBOX and see what output that gives you on some test machines.
Hope that helps,
Dunnpy
If you're distributing Flash Player for an organisation then you need to sign a distribution agreement with Adobe - link here.
You will then be emailed a link to download the installer, and the MSI version is the one best suited for customisation/deployment for KBOX.
You would then customise the MSI with an MST file, to set your own standards that identify this as a 'managed' package - disabling updates etc. (see Package Knowledge Base entry for Flash on this site), 'cos you don't want your users updating this themselves, or being prompted to download the newest version.
You first step in troubleshooting your issue would be to specify a log file for the MSI installation on your commandline in KBOX and see what output that gives you on some test machines.
Hope that helps,
Dunnpy
Posted by:
jmcfadyen
13 years ago
many of the adobe player type applications have CA's which run in user space.
If you are deploying as a system account this account has no profile loaded during execution which causes CAs running in user space to fail.
If you are deploying using a system account you need to condition the CA's to not run.
If you are deploying as a system account this account has no profile loaded during execution which causes CAs running in user space to fail.
If you are deploying using a system account you need to condition the CA's to not run.
Posted by:
techbeck
13 years ago
I think I got it resolved...2 problems....
I have the Flash installed scheduled for a few times a week. Users who are already using IE and has IE open, the flash install will either not happen or the changes will not take effect until the user closes all other IE windows. The other issue is the updates on a lot of the systems are really out of date. Why we bought KBOX so I may have to start pushing out those update soon.
thanks
I have the Flash installed scheduled for a few times a week. Users who are already using IE and has IE open, the flash install will either not happen or the changes will not take effect until the user closes all other IE windows. The other issue is the updates on a lot of the systems are really out of date. Why we bought KBOX so I may have to start pushing out those update soon.
thanks
Posted by:
anonymous_9363
13 years ago
Problem one can be handled by a blanket email to tell users that they must exit IE by time 'x' on date 'y'. You then need to build intelligence into your package so that IE gets killed if it's detected as running.
Problem two should be handled by the package, by uninstalling/upgrading older versions.
Problem two should be handled by the package, by uninstalling/upgrading older versions.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.