It's Time to put on the Big Boy Pants...
For the past year I have been working for a company, that when I started with them, had a very crude Wisescript that was used to Wrap all installs being deployed. At the time they were strictly XP.. Since I came on board I initially tried to get them to adopt a 90 to 95% MSI based rule for all installs being deployed. When that fell on deaf ears, I proceeded to create a more comprehensive Wrapper script for us to use that would ad in faster delivery of packages, as well as add in troubleshooting when problems arose. I have grown this wrapper so that it would address all of the following possible sceneros...
- Checks for Current and Previous Versions
- Check for current running process, warning users to save before continuing install
- Checks and calls for Required PreReq Installs by parsing an INI file with appname and Product codes
- Creating Logs for everything installed (all Prereqs, vendors install, as well as a Log file for the Wrapper itself)
- Checks for 64 bit OS, so a different install could be run if necessary
- and of course capturing the Exit Code from the main vendors installs to pass along to SCCM
It has grown quite complex, expecially when we switched over to Windows 7. However, in the back of my mind I continue to be nagged by all of its shortcomings. For starters, Wisescript is 32 bit only, and running it on a 64 bit OS has a few challengers, another is the fact that in some cases the Wrapper actually gets in the way of some of the vendor's created MSI's logic. Lastly anytime we are trying to run a Vendor's EXE within the wrapper, you get popups warning the users. So either you create an Environment Variable SEE_MASK_NOZONECHECKS=1 so that Exe's can be run from the network, or you can copy all source media to the pc and then run it. We choose the EnvVar route.
I said all that to say, I want to scrape the Wrapper idea entirely and create 2 or 3 MST/MSI Templates that handle the following situations...
- MST with all of our logic that can be applied to Vendor MSI's
- IST template that can be applied if required to create a Setup Capture
- ISM or WSI file to handle all Vendor's EXE installs (basically use a Custom Action to run the exe from binary or installed files)
Does anyone have any suggestions to migrate some of our logic over to a strictly MSI based install method of deployment?
One last thing... We have a banner that runs on top of the desktop that runs the entire time the install is running until its complete. Users have grown accustom to this being there so they know that when its gone, the install is done. Is it possible to Create a dialog that has Variablized text that can popup and stay above all other windows, but not allow vendors dialogs to display? For instance we run all MSI's with /qb! so they at least see progress, but our banner is actually running as a different process that is killed at the end of the script. This is easy with Wisescript but I dont know how to do this with MSI Dialogs. I tried to run our banner process from a Custom Action, but I cant pass the Text Variables. It just displays the variable and does not resolve it.
For the curious, our Wisescript commandline is...
VendorAppVersion and StrReboot are variables inside script. We also have a completely different message for Uninstalls.
So either I try and create a dialog that runs within our Wrapper MSI, or I try to get our current Banner.exe to run and then kick off the vendors install.
All suggestions would be greatly appreciated for either getting banner to work, or in migrating Wisescript to MSI.
Thanks in advance.
Be the first to answer this question