Video Screencast Help
Search Video Help Close Back
to help

Endpoint Management Community Blog

Showing posts tagged with Wise Packaging
Showing posts in English
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

riva11 | 29 Oct 2007 | 1 comment

Uso questa utility molto spesso e penso che possa essere utile a tutti. Può essere usata in sostituzione della funzione aggiungi/rimuovi programmi e fornisce alcune interessanti informazioni aggiuntive. Una caratteristica molto utile è la stringa di disintallazione di una'applicazione. Per questa operazione, click con il tasto di destra selezionando un'applicazione, visualizzare le proprietà e copiare la stringa completa.

Il download è disponibile a questo link:
http://www.nirsoft.net/utils/myuninst.html

Tip: date uno sguardo anche gli altri interessanti tools di questo sito.

Thanks to k00tje for this tip, the original article Quickly Find an Uninstall String can be read : here .

WiseUser | 07 Aug 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)
?...
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 | 04 May 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".

DavidLockwood | 11 Jun 2007 | 2 comments

The Active Setup key in the registry allows you to specify a command that should run the first time a new user logs on. You can do some pretty cool things once you know how to leverage this key. Read on to get started.

Problem:

Using Active Setup

An application needs to launch a repair when a new user logs on to insert per-user information in to the user profile. Examples of per-user information might be a registry key under HKCU or a file in the user profile under the My Documents folder.

In order to activate a repair a valid application entry point must be launched (advertised shortcut, extension, COM information).

What if an application doesn't have an entry point? What about a plug-in for Excel with no shortcut? Oh dear.

Solution:

Active Setup...

Annette Klomparens | 20 Mar 2007 | 1 comment

The User Interface script (Located in the MSI script of the Windows Installer Editor) is skipped when you remove an installation by selecting the Remove button in Add/Remove Programs. However, executing the .MSI directly to uninstall the installation does run through a User Interface during uninstall.

If you are seeing different behavior when you run the uninstall through Add/remove Programs than when you execute the .MSI directly, you should check the User Interface script for custom actions that have not been conditionalized.

Screenbert | 09 May 2007 | 1 comment

After repackaging an application, do you find it a pain to go change 10 different settings inside of the Windows Installer Editor? Here's a tip that's sure to help.

You can take your company standard for these settings and change their defaults. For instance, if you wanted Windows Installer Editor to always create an EXE instead of a MSI, you would follow these steps:

  1. Open your Wise Share Point\Templates folder
  2. Open the "Windows Application.wsi" file
  3. Click Installation Expert and then Build options under the Release definition section.
  4. Change your setting.
  5. Save and close your wsi file

From now on, all of your repackaged applications will use...