Notice that this could be taken as the entry on your MSI but t he problem I see here is that even if you modify your MSI to include : TSC_START_AUTO=1 I don't think that on large environments they would like to remove / reinstall the product if it was already deployed just to enable a couple of options like this. We have packaged Snagit 19 and now we are currently provisioning Snagit 2020 via an appstack and have no issues whatsoever. Reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run" /f /v "Snagit User Process" /t REG_SZ /d "C:\Program Files (x86)\TechSmith\Snagit 10\Snagit32.exe /i" And I applied this fix for SnagIt 10 but should be the same thing for many other applications except for the /i that is just assigned to SnagIt. During installation this snagit.reg file will be automatically copied to the ProgramFiles directory. (in my cas directly on the system root (c:)) Put this file in the same directory as your MSI. A log off /in is needed to see it happen. close SnagIT (also the program in the system tray) and start Snagit from the command prompt with the option '/e' A file snagit.reg will be created. Be careful if your deployment is 圆4 or x86 the command below applies only to 圆4 but you can modify it to adjust the path for x86. With the command below you will include the process on "Startup" and even without an icon on StartUp the process will appear on the task bar and also minimized with the /i switch. Products with Unique Install Behavior Products that Require Applications be Closed Before Installation Products that Require a Manual Download List of Known Issues and Considerations Products with Unique Install Behavior The following table contains a list of products that have unique installation behaviors.
0 kommentar(er)
