Posted on 03-03-2009 12:28 AM
For some odd reason I can install Flash via ARD and locally, but not using Casper....well, it actually installs, but every browser refuses to acknowledge the plugin.
I've checked permissions and structure...everything seems OK.
Anyone have any history here?
Thanks,
jeremy
Posted on 03-03-2009 12:52 AM
Any possibility the browser was running during install?
Posted on 03-03-2009 04:02 PM
nope!
Posted on 03-03-2009 04:10 PM
I know the problem! It starts with an AD and ends with a BE!
If Safari doesnt see something that is odd. If it was other browsers I'd say make sure it has a higher priority at imaging. However, if you are pushing with remote or a policy I'm not sure.
You make me paranoid now to check it again. What version are trying to install?
Craig Ernst
UW-Eau Claire
(715) 836-3639
Sent from my iPhone
Posted on 03-03-2009 04:16 PM
We've been installing Flash Player 10 using the pkg without issues. We run it as a startup item to ensure the browsers aren't open.
-John
Posted on 03-03-2009 04:21 PM
There may be some apps that require someone be logged in at install, at least in Adobes case. This is being found possibly in CS4 with Photoshop and InDesign, but I can't confirm that.
Try it while someone is logged in and see what happens?
Craig Ernst
UW-Eau Claire
(715) 836-3639
Sent from my iPhone
Posted on 03-03-2009 07:59 PM
I've got the latest Flash Player installing just fine with Casper 6.01.
On 3/3/09 2:28 PM, "Jeremy Matthews" <jeremymatthews at mac.com> wrote:
With all .pkg installers I cache them first and then install all cached
packages. I do all this with a login policy to ensure applications aren't
running.
--
bill
William M. Smith, Technical Analyst
MCS IT
Merrill Communications, LLC
(651) 632-1492
Posted on 03-03-2009 08:05 PM
Login policy...so a user is essentially logged in when yours runs. Interesting.
Craig E
Posted on 03-04-2009 05:47 AM
I do 99% of my software pushes as login policies. This guarantees the
On 3/3/09 10:05 PM, "Ernst, Craig S." <ERNSTCS at uwec.edu> wrote:
machine is up and running and that the software gets installed before the
user sees his Desktop. It requires setting the preference in the JSS Admin
section to not allow the login to complete until all the policies have run.
Also, if someone's waiting for an update then all I have to tell him is "Log
out and log in again."
Bigger pushes such as OS updates take longer and require restarts. I'll
handle those by caching them ahead of time and then scheduling an install or
creating a log out policy.
--
bill
William M. Smith, Technical Analyst
MCS IT
Merrill Communications, LLC
(651) 632-1492
Posted on 03-04-2009 08:32 AM
Using a self-service policy...
Installing the newest version, as of yesterday/
-j