Before we dig into the specifics of 3.0 - why it was necessary and how we got there - we need to cover a little bit of Slack history. The good news is that it’s available on our beta channel now. In all seriousness, the experience some customers have had leaves us with a pit in our stomach, and we’ve been working tirelessly towards a more mature version of the app, dubbed Slack 3.0.
Kinda seems like that something is “writing a desktop chat app in JavaScript”. The only silver lining has been being on the receiving end of some absolutely savage burns: Instead of flailing limbs and pitch squeaks, ours has manifested in ways rather more grim: inexplicably failing to render content, reloading during common operations, and error screens that aren’t actionable. Otherwise, i f you continue with the GPO MSI install method, on the users next VM, the msi would run again and recreate what is needed in %localappdata%.Recently Slack on the desktop has been going through an awkward adolescence. Whenever the update.exe runs, it would prompt for elevated credentials but you can just delete update.exe on the golden image. Maybe Slack did this so that users could use their product without local admin privileges and so that the update mechanism could always keep slack up to date.Īssuming that the systems will be single user non persistant vm's, one trick that worked to have a system wide install is to copy the users %localappdata%\slack and put it in %ProgramFiles(X86)% on the golden image and point any shortcuts to slack.exe in it. This suggests that you would be fine with only capturing the %appdata%\slack directory with UEM: It appears that once it is installed to %localappdata% it runs from there but stores the users stuff in %appdata% and the cloud. The contained exe installer didnt appear to take any command line input for target dir. I played around with the slack msi installer and learned that all it does is unpack the exe installer and run it and leaves traces in the registry for uninstall.
0 kommentar(er)
