You'd need to list the available users on the system that need Slack app in their home directories. Those copies of Slack don't have the Squirrel Update prompts. Also, this script wouldn't run if the installed copy of Slack was originally sourced from the App Store or MDM managed by the IT organization. Not every user on the system would need Slack in their Dock. The only caveat is that you must provide a pre-determined list of users for the machine you attempt to run the script against. The new solution script below would help simplify the deployment by installing the Slack app in the users' ~/Applications directory and add the shortcut to Dock. From an administrative prospective, one would have to be extremely mindful to also query the apps installed in users' home directories as several management tools rarely take ~/Applications directory in consideration. This would also requires multiple copies of Slack apps on the same machine for multiple non-admin users to access. By default the directory doesn't exist and has to be created. Optionally, we can deploy Slack app to each user's ~/Applications directory. Solutionįortunately for us, Slack developed a knowledge-base article on enterprise deployment best practices. The only upside of this solution is that all users on the same machine would be using the same copy of the latest Slack version, which simplifies the deployment. The script would notify all users actively using Slack that the app would restart itself in several seconds.Īdmittedly, the above solution wasn't organic and understandably it can be a grave security concern for some. Initially as a fun side-project to satisfy my curiosity, I came up with a solution to mitigate this by having the Slack app, which was already installed in the main /Applications directory, automatically update itself as soon as the Launch Daemon script fetches a new update from. Thus, they aren't able to dismiss the Squirrel Update prompts on their own, which was a productivity hindrance. I manage several macOS remotely, and one of the biggest pains is that our users aren't administrators on those machines. This work was inspired by the challenges I encountered in the workplace. My work's IT folks said nothing has changed on their end that should have affected this.įor now I guess I'll just use the App Store version since the web version doesn't integrate into my workflow well, but I'd really like to figure this out.Install Slack app in User's Applications Directory - macOS Background I've uninstalled and reinstalled it several times (both on and off my work VPN), checked the /Macintosh HD/Library directory for temp files containing "slack" (couldn't find any), and rebooted the machine several times. Other Electron apps (like VS Code) are working just fine on the same machine. Note: Unresponsive for 112 seconds before sampling Path: /Applications/Slack.app/Contents/MacOS/Slack Just says it was unresponsive, which isn't news to me. I've skimmed through the error report and nothing meaningful stood out to me. Force quitting the app brings up the "Report to Apple" popup. If I right click on the icon it says "Application Not Responding" with an option to force quit. After it finishes I open Slack.app and proceed past the "unknown file downloaded from the internet" warning, and the icon just bounces up and down in the dock for several minutes before it just stops bouncing. If I download it from the Apple App Store it works, but I don't want to use the App Store version, and the natively installed version worked just fine until suddenly it didn't despite seemingly nothing having changed.Īfter moving Slack.app to the /Macintosh HD/Applications directory it seems to go through the normal install process. The Slack desktop app is failing to launch 100% of the time on my work machine when using the version downloaded from.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |