menu.nomad.login.ad.json blank values trigger behavior.
magnusviri opened this issue · comments
I just tried menu.nomad.login.ad.json and it doesn't work right. It creates a lot of default blank values that trigger unintended behavior. For example, a blank EULA text will trigger the EULA to display.
I should add that ljcacioppo gets around this by making most of the values optional. Maybe something similar could be done here in the build script?
Can you take a screenshot of what your profile in Jamf looks like? I don't personally use Jamf's Schema for profiles, but my exp. is that if you leave preferences checked they will appear in the profile. If you're not using a preference from the custom schema you should uncheck it.
