Software Deployment

Naughty, Wayne! First port of call is ALWAYS AppDeploy's Search, surely? :)

http://itninja.com/question/blackberry-3.6-must-run-setup.exe065&mpage=1&key=isscript%2Cmerge禂
http://itninja.com/question/blackberry-3.6-must-run-setup.exe207&mpage=1&key=isscript%2Cmerge窜

G'Day Ian,

I did honest! But the links in the message discussion didn't provide any fruit. One goes to a Macrovision KB and the other goes to the Acresso home page. I was looking it up for someone else who was searching for them. No probs. I'll just advise to deploy the isscript beforehand as a pre-req with the modified dcom entries in thier package.

Thanks again,
Wayne

Hi Wayne,
it depends on which version you need.
Versions 11 and up where never published as single downloads.
But there are ways to get them :-)
Regards, Nick

ORIGINAL: nheim
But there are ways to get them :-)


Indeed, and last time I needed this I downloaded the eval copies of

AdminStudio 7.5 (SMS edition) http://www.acresso.com/promolanding/7318.htm
AdminStudio 8.6 (System Center Configuration Manager edition) http://www.acresso.com/promolanding/7698.htm

and drilled some of the newer msms out of those.

Actually at one time someone from Macrovision contacted me as to question the legality of doing this for my contract work. You could say I didn't really appreciate that.

We had an old thread regarding IS MSMs and one of the forum users also had a legal issue with Macrovision (now Acresso).

Thanks Guys.

Nick: I thought of doing what you hinted at too (when I went looking on Acresso's site) and Kim and jib kind of confirmed, but since it was a query from an acqaintance, I recommended the safer option.

jib: I'm curious as to why you would include an isscript mm? Unless it was a standalone installation (i.e. not managed install). Personally I would prefer to keep right away from including an isscript msm within my packages. If anyone has a moment could someone educa-mate me with a reason for doing this.

Regards,
Wayne

Wayne,

using the merge modules instead of trying to handle deployment of multiple versions of the isscript runtime is what most of us regards as current "best practice". It's just the easiest and most clean way .. for vendor-provided installations you can add the msm to a transform ..

Ok, so there are a plethora of ways to deploy a vendor MSI based on ISScript. Say I include the Merge Module of ISScript in an MST. If some other app installs a lower version of ISScript later, how would one uninstall the app that was installed with an MST containing the MM?

When I manually install a lower version of ISScript, just for testing this scenario, and then go to ARP and attempt uninstalling the app, it just hangs there.

Any help would be greatly appreciated!!

Also, seriously....where can I get isscript msm's. None of the links I've found exist anymore.

Dude...