07-28-2021, 03:44 AM | #1 |
Junior Member
Join Date: Jan 2017
Posts: 25
|
DisplayLink 1.4 (defaults can now autologin)
Maybe its me, but I had a hard time finding this article:
Enabling/Disabling DisplayLink Manager autostart via command line https://support.displaylink.com/know...er-autostart-v Basically defaults commands can be used to launch DisplayLink on behalf of the user. This means Configuration Profiles can be used if you're managing Macs using an MDM server (Jamf Pro, WS1, etc.). This article should be considered a "hot" item for those of us who manage/support macOS in enterprise. |
07-29-2021, 12:16 PM | #2 |
DisplayLink Tech Support
Join Date: Jan 2020
Location: Katowice, Poland
Posts: 269
|
Hello donmontalvo,
Thank you for your feedback on that. If you have not seen one of our newer FAQs about deploying DisplayLink on MacOS with Jamf you can click on that link. In case of any questions, feel free to post your questions here. Kind regards, Jakub
__________________
Jakub Dabrowski DisplayLink Where to download the latest Windows drivers How to clean up a corrupted installation How to report issues to DisplayLink for a speedy resolution |
07-29-2021, 09:09 PM | #3 |
Junior Member
Join Date: Jan 2017
Posts: 25
|
The Jamf Pro "files and folders" payload isn't intended to launch applications. That would likely create a significant security risk.
Apple recommends using a Launch Agent. With that said, the one that comes with the DisplayLinkLoginScreenExtension.pkg package doesn't seem to work. Code:
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>CFBundleVersion</key> <string>1.4.0 (120)</string> <key>Disabled</key> <false/> <key>KeepAlive</key> <true/> <key>Label</key> <string>com.displaylink.DisplayLinkUserAgent</string> <key>LimitLoadToSessionType</key> <string>LoginWindow</string> <key>ProcessType</key> <string>Interactive</string> <key>ProgramArguments</key> <array> <string>/usr/bin/open</string> <string>-W</string> <string>/Applications/DisplayLink Manager.app</string> </array> <key>RunAtLoad</key> <true/> <key>ThrottleInterval</key> <integer>5</integer> <key>Umask</key> <integer>0</integer> </dict> </plist> 1. Launch Terminal and run this to create a preference file: defaults write /private/tmp/com.displaylink.DisplayLinkUserAgent AppAutostart 1Then run this to convert the preference file to an uploadeable format: plutil -convert xml1 /private/tmp/com.displaylink.DisplayLinkUserAgent.plistThen cat the file to make sure it is readable, if it comes back with gibberish, it wasn't converted properly: cat /private/tmp/com.displaylink.DisplayLinkUserAgent.plist2. Create a new Configuration Profile using the "Application & Custom Settings" payload, and upload /private/tmp/com.displaylink.DisplayLinkUserAgent.plist to the payload, using com.displaylink.DisplayLinkUserAgent as the preference domain, scoped to all computers. 3. There is no step 3. Thanks, Don Last edited by donmontalvo; 07-29-2021 at 09:49 PM. |
07-29-2021, 09:30 PM | #4 |
Junior Member
Join Date: Jan 2017
Posts: 25
|
Attached screenshots.
|
07-30-2021, 11:31 AM | #5 |
Member
Join Date: Mar 2018
Posts: 58
|
Great post @donmontalvo
Need more of this on here. |
07-30-2021, 12:52 PM | #6 |
Junior Member
Join Date: Jan 2017
Posts: 25
|
We’ve been working with Jakob on this, he is incredible.
|
Tags |
command line, configuration profile, defaults, login |
|
|