-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Custom Keys #74
Comments
Yes absolutely on both, this is a very needed feature, both Entirely custom and to add single keys. It is planned and coming. Regarding the screensaver, that is a tricky payload. It exists in 3 domains and with different settings. I can respond better tomorrow about that specific payload. |
Hello again. Yes, the screensaver payload has had some changes, and it's actually split in two parts. Device level and user level. So if you need So you might want both, one in the user scope and another in the system scope. You can read more in the profile docs under Screensaver. But if you feel that anything is missing outside of that documentation, please write here again with what that is and I'll add it in. |
Yeah I figured that. The idleTime key does work in a computer scoped policy though, so I manually edited the profile in an IDE before signing it and uploading it to Jamf. Good tip though to know I can find the keys this way. Thanks |
Ah, great. Then I'll add |
I've updated the manifest for |
Awesome! Thanks. |
@ahrenstein is this issue resolved? If so, please close this issue. |
Oh yeah this is resolved. Thanks a ton |
I noticed that the ScreenSaver policy only sets loginWindowIdleTime but I also wanted to set idleTime so that end users have a screen saver timeout. I could not find an option for it, nor could I find a way to manually edit the profile in Profile Creator.
It'd be really nice to have a section to deploy a custom payload. Maybe something as simple as allowing you to add key:value pairs or even just a place to edit raw XML and have it lint it before letting you save it.
The text was updated successfully, but these errors were encountered: