Deploy Software to Currently Logged in User

Do you know who you DON'T want the file to go to?

What I'm thinking, and this is without knowing your environment, is that
if your users are not generic users not named something like "staff" but
rather are usernames that are bound to something like OD or AD couldn't
you set a policy to trigger at login and scoped to the users you want to
get the package?

Or what about Self Service?

Or script it to grep or awk the current user exclude known local
usernames that you don't want it installed on and if it exits 0 then
call on the jamf binary to trigger a policy via a custom trigger in the
policy.

Or here's an odd one, Script it, make a policy with a custom trigger.
Script that jamf policy call into a clickable script and e-mail it to
the users you want to have it J. I don't think I'd do this myself
because well, they could forward it, I have no idea what your e-mail
policies are on attachments, might as well use Self Service if you're
going to require user interaction etc... Just trying to think of
different ways to achieve this, thinking outloud (via keyboard). I'm
guessing you're looking for a solution that doesn't require user
interaction though.

-Dusty-

Dustin Dorey

Technology Support Cluster Specialist

Independent School District 196

Rosemount-Apple Valley-Eagan Public Schools

dustin.dorey at district196.org

651|423|7971

You could deploy the app via a policy @ login & call the $3 variable, if you're happy to part script the install.

Having File vault on forces only applying to the current logged in user..

I think there is a way via checking for the currently logged in console user.. but haven as of yet required to do it myself..

Ben Toms
IT Support Analyst GREY Group
The Johnson Building, 77 Hatton Garden, London, EC1N 8JS
T: +44 (0) 20-3037-3819 |
Main: +44 (0) 20 3037 3000 | IT Helpdesk: +44 (0) 20 3037 3883

Apologies.. I meant to bullet point my answer:

1. You could deploy the app via a policy @ login & call the $3 variable, if you're happy to part script the install.

2. Having File vault on forces only applying to the current logged in user..

3. I think there is a way via checking for the currently logged in console user.. but haven as of yet required to do it myself..

Ben Toms
IT Support Analyst GREY Group
The Johnson Building, 77 Hatton Garden, London, EC1N 8JS
T: +44 (0) 20-3037-3819 |
Main: +44 (0) 20 3037 3000 | IT Helpdesk: +44 (0) 20 3037 3883

You could also have the package place the user files in a temp location (ex: /var/tmp/). Then in Remote have a script run "After" the dmg and move the files to " ~/Library/... "

Are these modified plist files? I hardly ever anymore include anything
in /Users from my app packages unless it is a plist I have to customize. That way when the user launches the app for the 1st time they get a
fresh copy from the package's own template. What exactly is it you are
trying to do, if you don't mind me asking?

Thanks

Tom

I'm actually experimenting with Dropbox (dropbox.com<http://dropbox.com>) as a means for shared/synchronized files for some users, and starting to play around with deployment via Casper. I am attempting to deploy an already configured Dropbox to some users. This is purely experimental, on top of being a pilot program in the first place.

This is something that routinely comes up though, and I figured I should learn how to do it.

- Jay Heath
jheath at ecfs.org<mailto:jheath at ecfs.org>
718-329-7542