Have been testing OmniPage Pro 14 in preperation for AD deployment. When trying to install manually using the msi and not setup.exe, an error is displayed stating that isscript is required.

If I manually install isscript8.msi first and then install omnipage, everything is ok. However If I install isscript8.msi using AD, and then try to install omnipage, I still get the error sayint that isscript is required.

Has anyone experienced problems installing isscript through AD? It appears to install sucessfully so I can't understand the different results when installing it manually and installing it through AD.
0 Comments   [ + ] Show comments


Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

All Answers

Presumably the isscript8.msi isn't being installed properly when you are trying to send it out via AD... I've never tried deploying the install shield script engine via AD.

Had a quick look at it and it looks like you'd have to change the AgreeToLicense property to Yes for starters then presumably use the install at logon option unless you plan to publish it... Also it might be worth validating the MSI and fixing and suspicious errors / warnings. The eventlog might give you some pointers too.

The solution you are suggestion sounds a bit messy to me - have you considered repackaging the install into an MSI then removing the install shield stuff?

Answered 05/17/2005 by: MSIPackager
Third Degree Black Belt

I've not had success installing ISScript 7, 8 or 9 via GPO. It's got something to do with the missing PublishFeatures and PublishProduct actions.

We've taken the seemingly perverse step of repackaging these so that they actually work.

Now if only developers would stop using them.........
Answered 05/19/2005 by: greenmagnet
Senior Yellow Belt