Video Screencast Help
Endpoint Management Community Blog
Showing posts tagged with Wise Packaging
Showing posts in English
DavidLockwood | 28 Mar 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

The Active...

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 | 30 Jan 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 your new...

Screenbert | 29 Jan 2007 | 9 comments

Many times packagers use merge modules for applications to prevent conflicts when uninstalling that application later on. Here's a "best practice" to keep in mind when using merge modules.

There are drawbacks to merge modules, such as if a patch comes out for something in that module. You would then have to create a patch for each application you have.

You may find that it is better to ban merge modules altogether. Instead create a MSI for each of your merge modules and then make them a pre-requisite for the application that requires it.

The benefit of this is that when a patch comes out for whatever is in the merge module you only have to deploy one patch instead of a patch for each module.

Screenbert | 06 Sep 2006 | 2 comments

If you've recently upgraded to Wise Studio 7, you'll probably notice that you're missing a few options, such as build settings (installation .exe name), Media, Screen, Password and so forth. Read on to find out how to get things back to normal.

In order to see these options you have to run the WiseScript Package Editor with the /PE switch. The best way to modify this for new packages is as follows:

Open the Windows Explorer. On the menubar click "Tools", then "Folder Options".

Click the "File Types" tab. Find the file with the extension of WSE and click the "Advanced" button. Make sure the "Open with Wise Package Studio" is selected, then click edit. At the end of the "Application used to perform action line...