CS5 Growl

You'll need growlnotify for the pop-up windows.
On Tue, Jun 7, 2011 at 3:01 PM, Ben Toms <bentoms at btopenworld.com> wrote:

Or for more intrusive, use the jamf binary method.

Steve Wood
Director of IT
swood at integer.com

The Integer Group | 1999 Bryan St. | Ste. 1700 | Dallas, TX 75201
T 214.758.6813 | F 214.758.6901 | C 940.312.2475

please say you're using deploystudio or multicast asr and not imaging them one by one…

One by one. BUT, it's part of an domino to exchange migration.

So i've 4 hours booked out per mac, (2 per day).

Whole company is being rebuilt one by one!

Regards,

Ben.

Tah.

I was looking at iHook at previous employer as can be run at logout / over the login window.

Can growl do the same?

Regards,

Ben.

No, Growl cannot run over login window or during logout. A user has to be
On Tue, Jun 7, 2011 at 3:35 PM, Ben Toms <bentoms at btopenworld.com> wrote:
logged in for it to work.

If you are wanting to run during the login or logout process, use the
jamfHelper app to do it:

/Library/Application
Support/JAMF/bin/jamfHelper.app/Contents/MacOS/jamfHelper -help

That will give you all of the switches. Just make sure to use & at the end
of a line called by a script or it won't run your policy.

As an example, I use this when updating any software at login or logout:

/Library/Application
Support/JAMF/bin/jamfHelper.app/Contents/MacOS/jamfHelper -windowType fs
-icon "$iconpath$icon" -heading "$heading" -description "$description" &

That is part of a larger script that sets different variables, like what
image to display on the helper screen, what text, etc. This was developed
by Alan Benedict out of our Des Moines office. It puts jamfHelper into Full
Screen mode (-windowType fs) so the user cannot do anything.

Call that as a Before script in a policy, and then put this command in the
Run box of the policy:

killall jamfHelper

Otherwise the helper will continue to run even after the policy is finished.

I attached a screen grab of what it looks like during a Firefox upgrade at
login.

Steve Wood
Director of IT
swood at integer.com

The Integer Group | 1999 Bryan St. | Ste. 1700 | Dallas, TX 75201
T 214.758.6813 | F 214.758.6901 | C 940.312.2475


Sweeet. I think I've tapped up Alan about it before.

New environment though with no mac maintenance previously. With the userbase requesting it!! So this should look cool.

Do you use jamf displaymessage to notify them when they're logged in?

Regards,

Ben.

Depends on what I am wanting to notify them of. My uptime script uses both
On Tue, Jun 7, 2011 at 3:50 PM, Ben Toms <bentoms at btopenworld.com> wrote:
growlnotify and the displaymessage methods. For a machine that has been up
for 5 days or more, but less than 10 days, I use Growl. If the machine is
narcoleptic and has been up for 10 days or more, I use displaymessage to get
in the user's face.

Of course, you could use jamfHelper for all of it, too.

Steve Wood
Director of IT
swood at integer.com

The Integer Group | 1999 Bryan St. | Ste. 1700 | Dallas, TX 75201
T 214.758.6813 | F 214.758.6901 | C 940.312.2475

Steve,

Thanks for the info on using jamfHelper at login. I have setup a policy based on your info to display a full screen message while Office 2011 SP1 is installed. The message displays as expected, SP1 installs, the killall command clears the full screen window, and then the rest of the policy (update inventory) completes. The policy log file shows all these steps completing without error. The one problem I have is that after killing jamfHelper, keyboard input is no longer recognized until that user logs out. If I use a different window type, such as hud, I don't have this problem.

Any suggestions what may be causing this behavior?

Nancy Fay
Desktop Engineer
West Chester Area School District

Use LockScreen instead

thats what i use

Criss Myers
Senior IT Analyst (Mac Services)
iPhone / iPad Developer
Apple Certified Technical Coordinator v10.5
LIS Development
Software Management Team
Adelphi Building AB28
University of Central Lancashire
Preston PR1 2HE
Ex 5050
01772 895050

there is a known solution somewhere but
killall SystemUIServer

I believe is what they told me when I was investigating that

--
Todd Ness
Technology Consultant/Non-Windows Services
Americas Regional Delivery Engineering
HP Enterprise Services