I'm sure there are better ways to go about doing this, however this is how I finally got it to work for us, so thought I'd share I will be pushing it out to the rest of the company later today or tomorrow. They are running either El Capitan or Sierra currently. It is working with 15 for me (or that could be the config profile), so I am leaving it but want to make you all aware).Īll those combined have been working on my test group of 12 people. 'defaults -currentHost write idleTime 15' (This is where those at jamf and I differed. I also added in 'Files and Processes' with an 'Execute Command' (run command) Su $currentUser -c '/usr/bin/defaults -currentHost write moduleDict -dict path /System/Library/Screen Savers/Flurry.saver'įrom there I added it into a Policy I called 'ScreenSaver/Lock' Since Novemthe store is open All that is left, is to fill up our inventory with new products Stay tuned. Supports Windows XP up to Windows 10 and Mac OSX 10.6 up to Mac OS High Sierra.
We design and develop clock screensavers based on Adobe Flash ® technology for Mac & PC platforms. #!/bin/shĬurrentUser=`ls -l /dev/console | awk ` ScreenClockSaver is a project website by Ax-Easy. Then I have a script called 'ScreenSaver' added to jamf, that then ties into a policy. Then the file path '/System/Library/Screen Savers/Flurry.saver' (First Screen shot on this thread) This is how I (with the help from those at jamf) got it to work in my environment:Ĭonfiguration Profile with Login Window Banner set to have the 'Start Screen saver After:' I have 15 Minutes added.
