To see if the environment variable is actually there Then try opening Slack and see if it gets rid of that annoying admin prompt. # Create PLIST file that sets an environment variableįile="/Library/LaunchDaemons/"Ĭom.COMPANYNAME.disable-slack-auto-updatesĪfter you create the plist file on a test machine, you should log out and back in. Here is a script I'm working on this morning for this in my environment. The best way to do this is to implement this environment variable SLACK_NO_AUTO_UPDATES No system.log output when i press cancel, neither when i enter the admin credentials.
May 10 11:58:31 SecurityAgent: DEPRECATED USE in libdispatch client: dispatch source activated with no event handler set set a breakpoint on _dispatch_bug_deprecated to debug May 10 11:58:30 SecurityAgent: objc: Class TKTokenRefCtkd is implemented in both /System/Library/Frameworks/amework/Versions/A/Security (0x7fff9712afd0) and /System/Library/Frameworks/amework/Versions/A/MachServices/SecurityAgent.bundle/Contents/MacOS/SecurityAgent (0x10522fd10). May 10 11:58:30 SecurityAgent: objc: Class TKTokenRefImpl is implemented in both /System/Library/Frameworks/amework/Versions/A/Security (0x7fff9712afa8) and /System/Library/Frameworks/amework/Versions/A/MachServices/SecurityAgent.bundle/Contents/MacOS/SecurityAgent (0x10522fce8). I do get an output from terminal saying: May 10 11:58:30 Slack: DEPRECATED USE in libdispatch client: dispatch source activated with no event handler set set a breakpoint on _dispatch_bug_deprecated to debug But the pop-up on every start is still anoying. If you click on cancel, the app still starts. When they update Slack (which is simply a new installation of the most recent client), it always shows the dialogue mentioned in the subject or attached screenshot on every app start, until someone types in admin creds. We're currently running our mac's with automatic install scripts via jamf.
0 kommentar(er)
