I'm working on one of those FUN applications (Retrospect Client 7.6) that has to have a certain version of ISScript on the system to work (in this case version 9).
Previously (for SPSS 16) when this is the case I have added the ISScript.msi into the install policy but after browsing about this issue through Appdeploy would I be right in thinking that best practise would be to add the ISScript as a Merge Module?

If this is the case could someone please point me in the right direction for a v9 msm (I have 7,8,10 and 11 just not 9!!)

Many Thanks in advance
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


As the saying goes, "Merge Module, Schmerge Module"...we could debate the point endlessly. How rigidly does your site employ Best Practise? Does it include the use of MMs where possible? Are they all up-to-date there? (PS. if your site's anything like those I've been to, I already know the answer to that one!)

If you're deploying through GP, I'd go the MSI route, if only because the logging is easier to follow when things go wrong! If you must have a MM, why not just create one from the MSI?
Answered 02/17/2009 by: VBScab
Red Belt

Please log in to comment
This could be what you need ..

Answered 02/17/2009 by: jib
Purple Belt

Please log in to comment
Many thanks for the replies chaps I'll give the MM a try and if not I'll roll out the ISScript.msi in the same policy.
Answered 02/18/2009 by: jimmyx
Purple Belt

Please log in to comment