Let the User configure the Display Sleep timer.

Assuming 10.9... take a look at the security authorizationdb.

See:
https://jamfnation.jamfsoftware.com/discussion.html?id=8997
https://groups.google.com/forum/#!msg/macenterprise/FVXoxlV5S1c/qP4JukeDpe4J

You probably need something like this:

#!/bin/sh
security authorizationdb write system.preferences allow
security authorizationdb write system.preferences.energysaver allow
exit 0

Usually I would say @Niels.Illem is correct, but I believe if you are using a configuration profile for the settings instead of a first boot script, it may supersede any user interaction.

Not tried it personally but you could try setting it up with MCXtoProfile which lets you set the profile on the equivalent of the "Once" setting. Would need a bit of exploring but could get you to a solution!

Hello Niels, Pblake,

yes, in general, our user do have the rights to change the settings, but Pblake is correct. The Config Profile just overwrites the settings again and again. Is there any ways to have both options at once?

thanks and best regards,
Kevin

@davidacland :

Thanks for your answer! You mean that the Config Profile only run once? Unfortunately that would not be applicable for us, as users must not change certain settings of the Energy saver settings.

Alternatively ignore profiles, lock out the system preference and give them a GUI applescript that triggers a defaults write command to change the value.

The issue is, that we currently support ~1000 Macbooks. As the value has to be changeable by the user, a script that has to be run by them, maybe with a prompt that asks for the value, is not user friendly enough for us. On one hand we don't want to restrict them too much, on the other hand, we want to manage some of the settings permanently. Is there any way to combine that, without locking out the system preference?

In that case I would have a script that runs behind the scenes (triggered by Casper login trigger probably) that sets the energy saver settings you need using defaults write, leaving the "user" energy saver settings alone.