![]() A LaunchAgent wouldn't be able to do that part. It has to run as a LaunchDaemon since there's a jamf recon in the script, which requires root. Something soon enough to kick in shortly after they log in, but not so soon that it will end up tripping over itself. I would choose a timeframe of maybe every 30 seconds, but of course choose whatever you feel comfortable with. The OS throttles them back if they try to run any sooner and you get a bunch of entries in the system.log about it. I would use a StartInterval with some number of seconds so it kicks off periodically until it runs successfully.Ĭouple of points on this: Launchd jobs can't run any more frequently than every 10 seconds. You will need to create a LaunchDaemon to fire this all off. I added a lot of notes in here on what's going on and added spaces between lines to make things a little easier to pick apart, since I'm not sure what your scripting skills are like. Two is deploying cocoaDialog to your Macs (this could be contained in the same pkg that deploys the rest of the items) A simple cat /path/to/file as its result should be enough generally speaking. ![]() One is putting an Extension Attribute script together to capture the information in the exported file. ![]() There are several important part of this all working. I haven't thoroughly tested all aspects of this, but quick tests show that it works. Here's a script that you can use to get you going in the right direction I think.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |