/build/static/layout/Breadcrumb_cap_w.png

Merge Module for ISSScript 9

Hi,
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
Jimmy

0 Comments   [ + ] Show comments

Answers (3)

Posted by: anonymous_9363 15 years ago
Red Belt
0
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?
Posted by: jib 15 years ago
Purple Belt
0
This could be what you need ..

http://kb.acresso.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=Q110580
Posted by: jimmyx 15 years ago
Purple Belt
0
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.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ