So far I've been using options that come in JSS 8.6 for Configuration Profiles with 10.8 and they appear to be working to me. Successfully added wireless profile and settings for gatekeeper. Does anything appear in your computers inventory records under management history about the status of a deployed payload?
Any further news on this? I'm running 8.6.1, but I'm seeing the same behavior with login items. One item is working, one is not. It worked when I first built the profile. But has since stopped. On the JSS, if I go into the configuration profile, the items (they are Applications, but I added them as "Items") show under Applications and the path to the app is blank. Everything looks normal on the client in the Profiles section. It shows both apps and locations. However, going into the login items section of a user account will show the working application and a "Unknown" application (the application that is not working). I did check the login application when it first worked and all was good. If I rebuild it all I get it to work, but it then does the same thing again.
Any update on this? We have a few items / applications that we set to launch on login, but as soon as you save, it moves the item up to the Applications section and it displays as a blank entry. Is there a way to edit the pull down list of applications so that you can add custom entries and not have to worry about typing them into the Items section?
I can't say I've seen the exact behavior, however I have seen other settings within the Configuration Profiles dialog that "don't stick" when you leave the view. For example, "Use Network Authentication" in a Network payload for 802.1X auth. I suggest you report it to JAMF support if you haven't.
The bug is still present in Jamf Pro 10.9.
If a macOS Configuration Profile with a "Login Items" payload is created and an "Item" is added for an app (e.g. /Applications/Firefox.app), the respective entry is invisible after clicking "Save". However, it is still saved and correctly applied when the Configuration Profile is deployed.
Beginning with DisplayLink 1.4 the "autostart" function can be managed using defaults (Configuration Profile).