#Novation launchcontrol not working download zip#
#Novation launchcontrol not working full#
#Novation launchcontrol not working windows#

plist to use the QueueDirectories key instead of WatchPaths, but when I went to load the LaunchAgent I see the following errors:

#Novation launchcontrol not working windows#

The script works great when I run it manually once the Outlook first run windows are disabled. Thanks everyone for your efforts with this, especially. So no need to create the directory ahead of time. As soon as Outlook launches it creates that directory and the script specified in the LaunchAgent fires. Load the LaunchAgent that uses the path of ~/Library/Containers// as the directory for QueueDirectories. While you can't use WatchPaths, you can use QueueDirectories and not even bother to pre-create that folder. Its possible to do, but would take some work and experimenting to get it right.Įdit: I just ran another quick test, and this is even easier than I first thought. However, as long as the directory remains non empty, the LaunchAgent will continue to run on whatever interval its set to (10 seconds by default unless otherwise specified) so the script would need to run the setup of the account, then either remove itself, or disable the LaunchAgent so it won't run again. My test script simply put up a basic dialog so I knew it was working.

As long as the permissions are set correctly on the folder, Outlook drops files into that dir upon first launch, and it fires the script pretty quickly. I did a little experimenting on this though, and it seems its possible to pre-create the ~/Library/Containers// directory along with an Office 2016 installation, say as a script run 'After', leave the directory empty and then load a user level LaunchAgent watching that directory with QueueDirectories. There is the QueueDirectories item for launchd, but the thing about them is that it only works if the directory is not empty, so you can't, for example, use a path like /Library/Containers/ since its already populated with other directories.

(blast from the past) I will have to double check on this, but I believe this rule of launchd jobs is still valid today. has a writeup on this from his blog from years back. If its not there, the LaunchAgent won't use it as a trigger, and actually removes the path from its internal list of items to watch. Launchd's WatchPath function can only watch items (files/folders) that exist. The directory doesn't get created as part of the Office installation, only when Outlook first gets launched, and that point its too late.

#Novation launchcontrol not working full#

For the time being, anyone who'd like to test the AppleScript part of the solution is more than As far as I can tell in my testing, this path: ~/Library/Containers//ĭoesn't exist on a Mac that has not already had and run Outlook on it previously, so in the case of setting up newly setup/imaged Macs with Office 2016 installed on them, I don't think it'll be possible to use that full path as a WatchPath for the LaunchAgent.

From there, the script runs the same as older versions with a handful of changes.Īs I make more progress I'll post more.

Use a launchd agent to watch specific folders to know Outlook has been launched.

Use a configuration profile to suppress the Outlook first run window.

I'm still trying to find the right combination of items for the agent to watch.Īlso, the guide is only updated through about page 24. What's not done yet is the launchd agent to trigger the script at first launch of Outlook. You'll find it in 'ROOT/Library/Talking Moose Industries/Scripts/Outlook Exchange Setup 5.0.scpt'. The AppleScript itself should be ready for those who use it standalone as a double-clickable script or add it to Self Service. This is still a work in progress, but I've uploaded what I have so far to GitHub.

/Library/Talking Moose Industries/Scripts/OutlookExchangeLaunchAgent.shįeedback, as always, is greatly appreciated.

/Library/Talking Moose Industries/Scripts/Outlook Exchange Setup 5.0.scpt (customize this).

#Novation launchcontrol not working download zip#

I've also made minor changes to the AppleScript itself to better accommodate all potential settings not just Active Directory as well as accommodate this new setup.Ĭlick the Download ZIP button to the bottom right and locate these files in the ROOT folder: For now, be sure to keep the names and paths of the files and folders the same as I've created them unless you're comfortable changing the references in the three files. The ROOT folder simply designates the 'root' of the hard drive or '/'. The only file you need to customize is the AppleScript. The whole setup consists of one LaunchAgent file and two scripts.

After a lot of research into launchd QueueDirectories and WatchPaths, the WatchPaths made the most sense because I can monitor for the existence of specific files. I've devised a launchd setup that works well for me in my testing to automatically configure Outlook 2016 the first time it's launched. More stuff ready for anyone who'd like to test.