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 | 23 Oct 2007 | 0 comments

Here's a nifty tool I found that makes working with MSIs a real joy.... Exaggeration? maybe, but this tool's sweet (and free).

A common use MSIDiff is to automate changes you wish to apply over and over again to MSIs produced by other tools.

To do this you start by first manually making (and testing) the proposed changes using a table editing tool similar to the free "ORCA" tool and then using MSIDIFF to generate the code to perform these changes.

The generated output (typically with minor changes) is then executed via the (also free) MAKEMSI tool (you may have made it more generic so parameters are passed into it).

Download MSIDIFF here.

riva11 | 23 Oct 2007 | 0 comments

In questo articolo viene descritto un intelligente tool che ho trovato che rende lavorare con file MSI una vera gioia .... Esagerazione? forse , ma questo è un tool davvero eccellente (e gratuito).

Un uso comune di MSIDiff è di automatizzare le modifiche che desideri applicare ripetutamente a dei file MSI prodotti da altri tool.

Per fare questo si deve come prima cosa creare manualmente (e testare) le modifiche proposte usando un tool di editing simile al tool gratuito "ORCA" , poi come secondo passo si deve usare MSIDIFF per generare il codice che permette di eseguire questi cambiamenti.

L'output che viene generato (solitamente con piccole modifiche) viene poi eseguito tramite il tool (anche questo gratuito) MAKEMSI (è possibile farlo in maniera generica , in questo modo i parametri sono passati al suo interno).


WiseUser | 23 Oct 2007 | 2 comments

Uninstallation for the Installshield applications sometimes use rundll32.exe. Here are some of the different silent uninstallation cmd lines that I've come across:

  1. RunDll32
    C:\PROGRA~1\COMMON~1\INSTAL~1\PROFES~1\RunTime\0701\Intel32\Ctor.dll,LaunchSetup "C:\Program Files\InstallShield Installation Information\{BBDE6ABE -EF72-4752-9C09-EE9D6DE3102A}\Setup.exe" -l0x9 AnyText -remove -s -f1c:\Uninstall.iss
  2. RunDll32
    C:\PROGRA~1\COMMON~1\INSTAL~1\PROFES~1\RunTime\0701\Intel32\Ctor.dll,LaunchSetup "C:\Program Files\InstallShield Installation Information\{BBDE6ABE-EF72-4752-9C09-EE9D6DE3102A}\Setup.exe" -l0x9 AnyText /s /f1c:\Uninstall.iss
  3. RunDll32
    C:\PROGRA~1\COMMON~1\INSTAL~1\engine\6\INTEL3~1\Ctor.dll,LaunchSetup "C:\Program Files\InstallShield Installation Information\{5CE1EF14-2595-4320-A638-A627EE1D1BB9}\Setup.exe" -l0x9 -uninst -s

This piece of cmd line we...

R-Vijay | 22 Oct 2007 | 0 comments

If you have to install a .cer certificate with an msi installation, here's a great tip that points out several points you need to be aware of.

R-Vijay | 22 Oct 2007 | 11 comments

If your application requires installation of components such as files or registry keys on a per-user basis, but your application has no advertised entry points or other triggers to initiate the installation process, then Active Setup is the solution.

What is Active Setup?

Active setup is a process that runs automatically when a user logs in.

How Does Active Setup Work?

Registry keys at HKLM\Software\Microsoft\Active Setup\InstalledComponents\%APPNAME% and HKCU\Software\Microsoft\Active Setup\InstalledComponents\%APPNAME% are compared, and if the HKCU registry entries don't exist, or the version number of HKCU is less than HKLM, then the specified application is executed for the current user.

How do you create an Active Setup?

To implement Active Setup, you need to package all your user installation requirements into an EXE preferably, using SMS Installer, or Wise Installation System, and place the EXE on the client...

WiseUser | 19 Oct 2007 | 0 comments

The latest Adobe Suite applications come with install.xml and uninstall.xml files. You can edit the XML and decide which application you need to install from the suite of apps. Here's some info about doing just that.

Generally, these XML files are placed under the deployment folder in the suite. Check for the deployment folder in the CD.

Here are the command lines you'll need if you want to invoke the XML files to help with the installation:

Install Cmd:

Setup.exe" --mode=silent --deploymentFile="%CD%\deployment\install.xml 

Uninstall Cmd:

Setup.exe" --mode=silent --deploymentFile="%CD%\deployment\Uninstall.xml 

I found One more tricky thing, you can do the configuration part as well using the XML files.

Configuration to suppress the Serial key, Registration, Updates:

Instead of doing a capture\snapshot, you can create and use an XML file called application.xml.override which has the following entry...

R-Vijay | 19 Oct 2007 | 0 comments

Gacutil must not be called from a custom action. Gacutil is not designed to be used during installation.

Gacutil.exe works, but it is a developer tool, and developer tools go into SDKs and not runtime packages typically. It isn't really appropriate to put more tools into the runtime because that causes it to get larger, which makes it more difficult for applications to redistribute because of increased download size, etc.

In general, installing an assembly to the GAC is an application deployment activity, and is most often done during application setup. One should use Windows Installer to install your application. Starting with version 2.0, Windows Installer has built-in functionality to install assemblies to the GAC - the MsiAssembly and MsiAssemblyName tables in particular.

Its always better to use a MSI as an installer and directly authoring files, registry and GAC installation steps using built-in Windows Installer functionality instead of using a batch...

WiseUser | 19 Oct 2007 | 1 comment

We Can set the following property values as an administrator option in Wise Package studio instead of giving the values in the properties. This option is not used by most package developers.

Type of installation:

Per machine installation
Per user installation
Determined by user access

REBOOT Option:

Reboot If required
Always Reboot
Never Reboot

When using other settings like Rollback options, create advertised shortcuts as regular shortcuts, reinstall options etc.

WiseUser | 17 Oct 2007 | 0 comments

What is the difference between customizing an installation through the use of command-line parameters and the application of transforms? Get your answers (right here) while they're hot.

The main difference between these two types of customizations is that the customizations applied using the command line are only applied to the current installation but the changes made using transforms are applied during the original installation and all future repair and modifications of an installation.

When customizing the .MSI through a command line, you can only modify properties. An example of modifying a property through the command line is:

msiexec /i C:\Example.msi ALLUSERS=2.

This would set the property ALLUSERS to 2 for the current installation. However, this customization is not applied to the cached version of the .MSI, so during repairs, the value of ALLUSERS would be the value assigned at design time.

If you want to further customize an .MSI,...

R-Vijay | 16 Oct 2007 | 2 comments

Here are a few tips I picked up from Microsoft about how to "color inside the lines" when using any tool (including Wise Package Studio) to create an MSI. Hope these help.

  • Match components in previous versions of the MSI:
    1. Keypath resource matches a resource in previous .MSI list
    2. Match component layout of previous .MSI
    3. Set component key to match previous version.
  • Add all executable files to their own components
  • Create new component for the resource
  • Add all .TLB files to their own components
  • Group matching .HLP and .CNT files together
  • Group matching .CHM and .CHI files together
  • Put registry keys associated with files or components in matching components.
  • Put current user registry keys in their own component
  • Put non-current user registry keys in their own component.
  • Group all non-executable files to...