can anyone help with writting a vbs script to solve ice91.

the package I have is only used for per machine installations or is there another option to solve my problem

your views will be very much appreciated
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


Ice 91 is only a warning - not an error.

If the following statements are all true, you should usually be fine:

1) All your applications "entry points" (shortcuts, Clsids, extensions, etc) are advertised. And your OS supports advertising.

2) All the above entry points are in the same feature or a "child" feature of the feature containing the problem component(s). If you have captured the installation using a Wise product, this will usually be true.

3) The component(s) have an HKCU keypath that is not likely to pre-exist in any user's profile (no ICE38 errors).

4) The original source MSI will be available to the user the first time he runs the application (in the event that a file needs to be copied to his profile). Bear laptop users in mind too - some people like to pre-copy the MSI to a local folder before installing it.

For "per-machine" installations, the Windows Installer service will repair the broken components the first time the user runs the application (if all the above are true).

You could write a script to verify all these things.
Answered 07/22/2005 by: WiseUser
Fourth Degree Brown Belt

Please log in to comment