Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Management Community Blog
Showing posts tagged with Wise Packaging
Showing posts in English
WiseUser | 22 Aug 2007 | 0 comments

I've become a big fan of the Test Expert Tool that comes with Wise Package Studio. Here are a few very cool tasks you can perform with the tool.

  1. Verify proper installation, uninstallation and installation with user privileges.
  2. Application verfication tests such as launching the shortcuts and opening help files.
  3. Uninstall tests – We can find the created files, created registry entries, destroyed files, destroyed registry entries, residual files, and residual registry entries after uninstallation of the application.
  4. Machine capture – It Records the pre_ installation state of the PC to facilitate both install and uninstall tests.
    • Setting directories to be watched for uninstall tests.
    • Setting a file, wildcard or directory to be ignored.
    • Setting registry entries ignored during uninstall tests.
  5. Adding a user defined test case – We can define our own test case and check manually whether it passes or...
WiseUser | 21 Aug 2007 | 3 comments

The SelfReg table contains information about modules that need to be self registered. The installer calls the DllRegisterServer function during installation of the module; it calls DllUnregisterServer during uninstallation of the module. The installer does not self register EXE files.

If you're thinking of using the SelfReg table in the Installer Database, here are a few reasons to rethink your strategy.

  1. Rollback of an installation with self-registered modules cannot be safely done using DllUnregisterServer because there is no way of telling if the self-registered keys are used by another feature or application.
  2. The ability to use advertisement is reduced if Class or extension server registration is performed within self-registration routines.
  3. The installer automatically handles HKCR keys in the registry tables...
WiseUser | 16 Aug 2007 | 3 comments

We use deferred custom actions to perform actions and manipulate system files. Here's an example where I learned something new about these actions and Installshield \ VB Script.

One of my applications needs to append a value to the Autoexec.bat file, and we use VBScript to do this work. I wrote a custom action to append a value in the .bat file. Since the file is present in "c:\" I used "WindowsVolume" but it was not recognized in the deferred custom action. This is because deferred custom actions doesn't recognize installer properties like SourceDir or WindowsVolume.

To solve this issue, here are the steps we took. This is not an issue if you use WiseScript. But not all projects use WiseScripts.

  1. Create a custom action which has embedded VB code in it that appends the value to the .bat file. Let the custom action name be "APPBAT" and set the custom action as deferred system context and leave the sequence blank -- to be modified later
  2. Create...
WiseUser | 14 Aug 2007 | 2 comments

For those of you working with Wise Package Studio's advertising functionality, here are a few guidelines to live by.

Advertising Settings in Wise Package Studio

Select one of the "scan" options if you want Windows Installer Editor to inspect your computer's registry and the files in the installation and automatically add Windows Installer advertising information for the files that you add to your installation.

Various options can be set in windows installer -> edit -> Preferences ...

  • Do not scan advertising information: Select this when you want to use self-registration for components that support it. Windows Installer Editor will not scan files or the registry.
  • Scan advertising information into registry keys: Add advertising information to the installation as...
WiseUser | 13 Aug 2007 | 0 comments

By default, an .MSI package cannot contain more than 32,767 files due to the column definition of the sequence column in the file table.

Read on to find out how to work around this pesky limitation.

The default data type for the sequence column is integer. Set the data type to double integer to avoid issues with installations including more than 32,767 files. This change enables the .MSI to accept up to 2,147,483,647 files in the Files table. Below are the steps to convert the column definition:

  1. Open Microsoft's Windows Installer database editor, Orca.exe. If you do not have Orca, obtain the table editor from the Platform SDK for Windows Installer.
  2. Select Open from the File menu and browse for the .MSI file.
    Note: Select the Windows Application.MSI template (or the template used by your...
R-Vijay | 09 Aug 2007 | 0 comments

Wise Package Studio's SetupCapture application has a number of configuration options which can affect the quality of the resultant package. I will discuss them here by the option description.

(I have collected some info regarding the importance of the Setup Capture Phenomenon. I do understand that many of you are aware of these, but still I wanted to share the info with you all. Just consider this a brush up, if you're already in-the-know.)

Include files deleted during capture and Include registry keys deleted during capture: Unless you are trying to capture an upgrade/patch, you probably don't want to use these options

Capture changes in hardware registry entries: In reality, this means most of the data in the HKEY_LOCAL_MACHINE\SYSTEM key (which includes services and...

marco.baars-123 | 18 Jun 2007 | 1 comment

I use this small utility very often and thought it might be helpful to you all. It can be used as a replacement for add/remove programs and gives you some additional information. A very helpful feature is the uninstall string of an application. Just right-click on an app, ask the properties and copy the full string.

You can download it here:

Tip: Be sure to check out the other utilities on this website.

Harsh Mokal | 18 Jun 2007 | 0 comments

MSI Readiness Analyzer for Windows Vista is a free standalone utility for IT professionals which analyzes MSI application installers and highlights methods to prepare them for Windows Vista. MSI Readiness Analyzer shows where application installers can take advantage of new technology in Vista, and also where problems might occur.

For more information and to download this tool please access


WiseUser | 06 Jun 2007 | 3 comments

If you get that "deer-in-the-headlights" feeling every time you try to find something in a Windows Installer Log, this list of search terms should undoubtedly help.

?Feature: ?
Feature and component states (Top of list)
?is managed?
Find out if package was installed as ?managed?
?Machine Policy?
Find All Computer Policies (press search again key to forward through list)
?User Policy?
Find All User Policies (press search again key to forward through list)
Find a Specific Policy (include single quotes before and after name)
?ProductCode =?
Properties List (Top of list)
?ProductCode =?
Harsh Mokal | 03 May 2007 | 0 comments

Sometimes in packages ICE03 is encountered, which states that a particular entry is not according to a correct format. Here's some info to help you avoid this this chilly error.

ICE03 occurs mainly because of ESCAPE Characters like [,],{,} and so on.

Windows Installer does not automatically recognize these formats. Hence, they need to be written according to a special construct.

The main rule that should be followed is that:

If a substring of the form [\x] is found, it is replaced by the character x ,
where x is one character, without any further processing.
Only the first character after the backslash is kept; everything else is removed.

For example, to include a literal left bracket ([), use [\[].
The text [\[]Bracket Text[\]] resolves to [Bracket Text].

Some examples are:
1) [ should be written as [\[]
2) ] should be written as [\]]
3) { should be written as [\{]
4) } should be written as...