![]() The reason is what I stated above: msiexec.exe may not be allowed to run for terminal server users. The "StubPath" command can be anything "runnable", and in your case I would suggest not running msiexec.exe but rather a vbscript via cscript.exe or some other batch mechanism (CMD, REG, Etc.). Here is a sample active-setup entry for an MSI file (this is the content of a *.reg file): REGEDIT4 This is just a fancy name for a feature which allows you to "run something once per profile on login". I would use Microsoft's Active Setup feature. That's why I generally prefer to use batch files, scripts or reg files for the kind of situation you are facing. Terminal servers can be a deployment nightmare - users may not have rights to run msiexec.exe and hence MSI self-repair could fail. There are several ways to achieve what you want - one clunkier than the other. Active Setup is no longer advisable ( original source).
0 Comments
Leave a Reply. |