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.
