Video Screencast Help
Endpoint Management Community Blog
Showing posts tagged with Wise Packaging
Showing posts in English
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:
http://www.nirsoft.net/utils/myuninst.html

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 http://www.scriptlogic.com/products/msi-readiness-...

Cheers
Harsh

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)
??PolicyName??
Find a Specific Policy (include single quotes before and after name)
?ProductCode =?
Properties List (Top of list)
?ProductCode =?
Product...
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...

duijsterj | 01 May 2007 | 0 comments

If you've ever used InstallTailor you know it can create a "transform" which is a type of Windows Installer database that can be used to customize an installation to a particular group of end users.

Here's a quick demo that'll walk you through the basics.

See the demo, courtesy of software-repackaging.com, here and now.

duijsterj | 30 Apr 2007 | 0 comments

Sometimes it's nice to have someone in-the-know walk you through a complex task or procedure. Here's a dandy (and brief) Flash demo that walks you through the steps it takes to set up Launch Conditions when packaging an application using Wise Package Studio.

View the demo (hosted at software-repackaging.com) here.

GarethStewart | 02 Apr 2007 | 3 comments

The common practice inside most enterprise environments that I've seen are to create one large MSI for any size application. Here's an easy way to make those packages install faster.

If you compile your applications with the "Cabs Outside" option, your packages will install 50% quicker compared to "Cabs Inside".

To do this for all packages, just go into the Windows Installer Editor template you're using and go to Media and change the option to "Cabs Outside".