08-27-2020, 02:28 PM
(This post was last modified: 08-27-2020, 02:29 PM by Michael Baars.)
Hi JVD,
If you right-click the application in the Scense Explorer and open the properties page, you will find a 'Windows Installer' option in the menu on the left.
In this page you can edit the Windows Installer options for this application (availability of this page depends on the application type, App-V's have a page dedicated to this application deployment type). In the Advanced Settings button you can edit several deployment options like the registered user/company, and one of these settings are MST and MSP files. Please use the %installscript%-variables to reference the root.
Some small notes on your deployment/import:
Next time pre-copy the installers from your local system to the Installscripts share. This has 2 advantages:
- You know everything you need will be available
Yes, Scense copies the installers it thinks it needs (in your case the MSI and CAB), but possibly other files (ini, mst, msp?) are needed as well but are not identified
- You can define the structure.
Even as Scense creates a folder based on the name of the installer (specified by the developers) and the version, there are some companies that state they are IDontKnow and all apps have version 0.1. You could add structure like vendor/application/version/edition...
During the import (drag the MSI into Scense Explorer/select from EasyDelivery) make sure you have the path conforming to your %installscripts%-definition. Don't use your mapped folder (I:/), and there is a difference between //scense.acme.corp/installscripts$ and //scense/installscripts$. If you use the same source, scense will detect it already is in the right share, and will not copy the installer
Good luck!
If you right-click the application in the Scense Explorer and open the properties page, you will find a 'Windows Installer' option in the menu on the left.
In this page you can edit the Windows Installer options for this application (availability of this page depends on the application type, App-V's have a page dedicated to this application deployment type). In the Advanced Settings button you can edit several deployment options like the registered user/company, and one of these settings are MST and MSP files. Please use the %installscript%-variables to reference the root.
Some small notes on your deployment/import:
Next time pre-copy the installers from your local system to the Installscripts share. This has 2 advantages:
- You know everything you need will be available
Yes, Scense copies the installers it thinks it needs (in your case the MSI and CAB), but possibly other files (ini, mst, msp?) are needed as well but are not identified
- You can define the structure.
Even as Scense creates a folder based on the name of the installer (specified by the developers) and the version, there are some companies that state they are IDontKnow and all apps have version 0.1. You could add structure like vendor/application/version/edition...
During the import (drag the MSI into Scense Explorer/select from EasyDelivery) make sure you have the path conforming to your %installscripts%-definition. Don't use your mapped folder (I:/), and there is a difference between //scense.acme.corp/installscripts$ and //scense/installscripts$. If you use the same source, scense will detect it already is in the right share, and will not copy the installer
Good luck!