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%. 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. Go to Advanced and make sure the ‘Leave app running in notification area when the window is closed’ option is enabled. Next, open Slack and click the arrow next to the name of your workplace. The contained exe installer didnt appear to take any command line input for target dir. shell:startup Move the script you just created into the folder that opens. 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)
