We have been using a wrapper on my current contract for quite some time. But when we switched over to Windows 7, we ran into a few problems with our installs.

The biggest is UAC (we want to keep it in place but limit the amount of times a user will have to click on anything)

as it stands, since we are using a wisescript wrapper, we get prompted for initial EXE, then if we run anything inside the Wrapper that is an EXE, we get another prompt.

one way to get rid of this is to copy all media local before executing exe, or we have added the SEE_MASK_NOZONECHECKS=1 environment variable and then remove it after install is finished. This works sometimes but other times it does not.

So, my question is, would it be possible to add a Customized Manifest file to our install that will allow pc to trust install?

Copying all media to local pc before running it is not a perferred method in my opinion. Trying to make install go as quick as possible, ya know?

 

0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Community Chosen Answer

2

Here is the basic layout... 3 different WSE's (Install, AppSearch, and Uninstall)

The title of the Wrapper is versioned, and not used for the appname. EX: CompanyName_Wrapper_2.9.3 (we keep a copy of all previous versions of the wrapper for reference, plus when you open up a previous wrapper that is version 2.0, you know what updates are missing in case you need to make changes)

 

<<Install Wrapper Layout>>

* Declare all Variables

* Detect 64bit OS

* Check if Product is installed (use Include Script - AppSearch) (here is the entire content of that script http://www.itninja.com/blog/view/searching-for-installed-msi-s-via-wisescript)

* Check for and create our Log file directory

* Check for and Set Environment Variable (SEE_MASK_NOZONECHECKS)

* Uninstall section is next... we call it via Commandline (if CMDLINE = /uninstall)(so your Wrapper.exe /uninstall will kickoff this section)(this has the Include Script path to Uninstall.wse)

* Check if Latest Version Already Exist (exit with PROCEXITCODE 1638)

* Check if Older Version is installed (also checks if %APPEXE% is in use so we can notify user it needs to be stopped in order to continue, if they click OK it will Kill process)

* Main Install Section that will run the product install based on vendor specs. (install PreReqs, run vendors install, copy files and so forth)(dont forget to use the 64 bit var you set above in Variables if you need to have two different setups)

* Occationally we have to rerun Include Script AppSearch to make sure product was installed correctly, if it is then set PROCEXITCODE=0

* Verify ExitCode section (if successful you can add stuff here, like branding registry, applying security, or adding ActiveSetup keys)(if unsuccessful then set PROCEXITCODE=1

!! All of the steps above have a line added to the Log file for the wrapper, as well as creating a Log for any executiables run for the install.

 

Answered 08/08/2013 by: ekgcorp
Tenth Degree Black Belt

Please log in to comment

Answers

1

Also, we deploy via SCCM.. so factor that into your answer.

Answered 08/07/2013 by: ekgcorp
Tenth Degree Black Belt

  • I ran into this problem as well and like you, had mixed results with the SEE_MASK_NOZONECHECKS=1 approach. I believe this behavior was improved with 8.0MR1, which should have carried over to the Flexera release (not sure which version you are using). We do a hybrid of copying files local - and running from the server for binaries that are updated monthly (i.e. IE or Office installs which receive regular hotfixes). In our case, we added the file servers as trusted sites, and we didn't receive any additional prompts. Not sure if that's an option for you?
    • P.S. I'd still love to see your wrapper :)
  • I won't be able to share the script straight out, because there is some proprietary company info within it. I could however discuss its structure, and how over time I came to develop it to what it is today. There are a few pieces that I grabbed from here... http://wisescript.dragonsoft.us/ like checking for 64bit process and setting a property.
Please log in to comment
Answer this question or Comment on this question for clarity