The Year of The Geek - Latest Comments

Re: Updating Our DEPNotify Process With a LaunchDaemon

John M. — Tue, 04 Feb 2020 16:14:27 -0000

I just set the script to remove the launch daemon instead of unloading it. It was the easiest way to fix it. It won’t stop it from running but at a reboot it won’t exist so it won’t run again.

Re: Updating Our DEPNotify Process With a LaunchDaemon

PeternBHill — Tue, 04 Feb 2020 07:15:34 -0000

Hi John. You mentioned having issues removing the LA. Can you go into more detail on that? I'm stuck there too. Im using Jamf's DEP Notify starter and if I add a line to remove the LA, DEP Notify hangs on that policy. If I use a logout policy/script to remove the LA and reboot, com.depnotify.launch is still there causing DEP Notify to start again. It's quite difficult to get this working as I would like :P . Thanks! Peter

Re: Revisiting Apple Logic Content and Indexing

Joshua R. — Thu, 11 Apr 2019 12:59:29 -0000

I can attest that these are the only files required. As it appears Apple is slowly deprecating the usage of the User Template folders, I was able to get these files to the users needed folders utilizing a LaunchAgent and script.

Re: Revisiting Apple Logic Content and Indexing

Chris — Fri, 08 Mar 2019 18:21:55 -0000

Thanks for this. Got this working and after some testing I have found the only files required to copy the index over are: LoopsDatabaseV09.db, com.apple.logic10.plist and com.apple.garageband10.plist. In the case of Logic the 2 keys required in the plist are DontShowAdditionalContentDownload and LCCurrentDatabaseSchemaVersionString09, the rest of the plist generates during first run along with all the other files in Audio MusicApps.

Re: Updating Our DEPNotify Process With a LaunchDaemon

John M. — Wed, 27 Feb 2019 17:35:08 -0000

Hi TimL,

The scripts are just set to executable by running chmod a+x (or u+x). The reason I do this is just for making sure that the system can run the script no matter what. it also makes it easy for me for testing. I can just do a ./script and it'll run.

Re: Updating Our DEPNotify Process With a LaunchDaemon

TimL — Wed, 27 Feb 2019 16:06:46 -0000

Disregard the part about PPPC above...it is related to my company's wallpaper branding script which utilizes an Applescript sudo -u... "tell Finder" and bringing up a privacy prompt.

Re: Updating Our DEPNotify Process With a LaunchDaemon

TimL — Wed, 27 Feb 2019 10:25:21 -0000

Hi John M. . Firstly, thank you for posting the above and documenting your process! I've had DEPNotify workflow in use for about a year now, but found a lot of your ideas very helpful in re-writing and re-thinking our deployment process. I have a couple of questions: 1. can you share the reasoning behind your provisioning shell scripts appearing as UNIX executable files in your screen shots? Is there a particular method or tool you use to do this (other than remove the .sh extension and add execute privileges to the file)? I'm running into an issue where com.mycompany.myscript.sh is generating a privacy prompt (Mojave) over the DEPNotify window asking for permission to access Finder (?) I wonder if by creating a PPPC profile I can prevent this from occurring if my shell script where an "application" instead? Thanks in advance! Again, great work and great contribution to the community!

Re: Updating Our DEPNotify Process With a LaunchDaemon

Koning Eindbaas Van de Bende — Mon, 11 Feb 2019 10:15:30 -0000

nevermind... ;) that's what the postinstall does...

Re: Updating Our DEPNotify Process With a LaunchDaemon

Koning Eindbaas Van de Bende — Thu, 07 Feb 2019 06:51:30 -0000

I probably keep on needing something that the launchdeamon actually loads... ?

Re: Updating Our DEPNotify Process With a LaunchDaemon

Koning Eindbaas Van de Bende — Thu, 07 Feb 2019 06:29:39 -0000

Could I also use this package as a "Enrollment package" and cut out the enrollment policy?

Re: Deploying Macs with DEPNotify

John M. — Fri, 25 Jan 2019 14:06:42 -0000

It's supposed to start pretty quickly though I have seen it take a minute or so. Most times it's due to the jamf server not running the policy right away due to MDM commands taking too long to run.

Re: Deploying Macs with DEPNotify

Koning Eindbaas Van de Bende — Fri, 25 Jan 2019 09:44:38 -0000

So.. The DEPnotify package gets installed via a policy. How long does it take for you guys before the first policy gets kicked off? For me I have to wait several minutes, after enrollment, before the first policy drops and DEPnotify starts...

Re: Updating Our DEPNotify Process With a LaunchDaemon

John M. — Fri, 21 Dec 2018 15:36:42 -0000

Hi there! The API user and password are for getting information FROM the jamf API without hardcoding passwords into the script. Since that script resides on the jamf server you can do this.

Re: Updating Our DEPNotify Process With a LaunchDaemon

Brant Backes — Fri, 21 Dec 2018 15:12:40 -0000

Hi John,

I'm confused on the Scripts Payload for your policy above. The Parameters call out an API User. What is that for? I must be missing something here in your documentation?

Re: Deploying Macs with DEPNotify

John M. — Mon, 15 Oct 2018 07:27:58 -0000

Good luck with it, Chris! I do have an automated setup working in my enrivonment now that I’ll be publishing something on eventually. You can find it on my git page under depnotify-automated.

Also, keep checking back here or on YouTube, I’m doing a presentation at JNUC next week about it!

Re: Deploying Macs with DEPNotify

Chris Beard — Mon, 15 Oct 2018 06:45:39 -0000

Thanks for the article. We're looking to start with DEPNotify at University of Oxford and this looks like a great primer.

Re: Updating Our DEPNotify Process With a LaunchDaemon

John M. — Tue, 21 Aug 2018 09:29:09 -0000

Once the package is installed you have to log into the system. When you log in, DEPNotify should launch and do all of the tasks you assign it.

Re: Updating Our DEPNotify Process With a LaunchDaemon

Stuart SLSIT — Mon, 20 Aug 2018 05:30:01 -0000

Hi John, thanks for your reply, in response to "Have you tried just installing the package as a standalone without triggering with jamf?" Yes we have and it doesn't seem to do anything, it say's it's installed but nothing then runs, what should happen? All permissions are set to root:wheel 644
Our Post Install script is as yours is above. We have copied your scripts to the letter but with making changes to our -event policy names to match Jamf. Do you have any troubleshooting advice? Or perhaps a video of set up/what to expect? thanks for any help.

Re: Updating Our DEPNotify Process With a LaunchDaemon

John M. — Fri, 17 Aug 2018 11:33:36 -0000

Hi Stuart,
How are you triggering the script? I assume it's a post install script in the package like I describe above. Have you tried just installing the package as a standalone without triggering with jamf?

Would you mind sharing your sanitized post install script here?

Unfortunately troubleshooting here is a bit difficult as it could be any number of issues. If your launch daemon isn't running, it's most likely permissions or an error in the code. I did find that setting the permissions on the launch daemon in Composer worked better than using the script. The permissions I use for the launch daemon are: root:wheel 644

Re: Updating Our DEPNotify Process With a LaunchDaemon

Stuart SLSIT — Fri, 17 Aug 2018 11:00:17 -0000

We are getting nothing from this set up, obviously something we have done!! All we get is:

Disable Auto Updates ASAP
Setting main script permissions
set LaunchDaemon permissions
load LaunchDaemon

and then nothing?! Any ideas? TIA

Re: Revisiting Apple Logic Content and Indexing

John M. — Fri, 20 Jul 2018 13:44:40 -0000

I have not seen this happen, typically that happens when Logic can't find the package receipts, but if you're using this method it should place them all.

Sorry I don't really have anything more helpful.

Re: Revisiting Apple Logic Content and Indexing

Tyler Garcia — Thu, 19 Jul 2018 14:45:25 -0000

Hey John,

Thanks so much for this! I've got this working pretty well at the university I support. I have a question though. After all of the content is installed and the loops are indexed, everything *appears* to be there, yet when I open the Sound Library Manager window, it acts as if everything is uninstalled. Does this happen to you? Thanks!

Re: Updating Our DEPNotify Process With a LaunchDaemon

John M. — Tue, 10 Jul 2018 15:49:02 -0000

Ah my error. That's found on my Git page: https://github.com/jmahlman...

Re: Updating Our DEPNotify Process With a LaunchDaemon

tanya e. pfeffer — Tue, 10 Jul 2018 15:43:14 -0000

I mean the assignAndRename script..

Re: Updating Our DEPNotify Process With a LaunchDaemon

tanya e. pfeffer — Mon, 09 Jul 2018 15:45:36 -0000

Thanks, John. Would you mind also sharing your script?

Thanks!

-tep