Heard about this tool at JNUC last week and was super jazzed to deploy it. We installed it by hand on a few machines and it seems to completely cover our use case. That being said I'm having a bear of a time getting it to deploy 'correctly'. This isn't necessarily a NoMAD issue, rather I suspect it simply betrays a fundamental lack of understanding of the core functionality of deploying a custom preference on my part.
We've got a policy to install NoMAD and the launch agent pkg so it launches at start up then do recon. I also built a custom com.trusourcelabs.NoMAD.plist to deploy, which is deploying as a custom payload for com.trusourcelabs.NoMAD in a config profile scoped to a smart group of machines with NoMAD installed.
I can see on the client and in JSS that the config profile is applied. It is not populating in ~/Library/Preferences however (as I assume that it ought to be?), and when I run NoMAD or reboot a new copy of com.trusourcelabs.NoMAD is being built and populated with the default settings. If I default write the settings I want from terminal is behaves like a perfect gentleman.
I don't want to have to run a script to apply these per user since thats not in line with the best practices for deployment....and also feels kludgey. Some guidance on how this functionality is supposed to work would be awesome, especially if there's any gotchas or bits of silliness I should be watching out for.
Anyone's advice is greatly appreciated :D