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 | 17 Sep 2009 | 1 comment

How to register a dll using Msiexec.exe /y and Msiexec.exe /z

1. Go to File Section where the file is present
2. Double click the file
3. Goto Self registration tab
4. Selct the registration Method as "Use order Specified below"
5. Hit ok

Goto MSi Script section and you can find corresponding custom action for registeration .

Why we do this type of dll\ocx registration Compared to self reg table is ?

If the dll registration gets wrongly captured in the self reg table then it will throw error upon installation . When we install using the above suggested method then it wont throw any error if dll is not getting registered.

nac | 17 Sep 2009 | 1 comment

Many times we interfere with the MSI script sequence in InstallExecute sequence, AdminExecuteSequence, advertised sequence, InstallUISequence, AdminUISequence. Following lists will be helpful in maintaining proper sequence.

It's not necessory that sequence number should be like this only but order is suggested to be the same.












NOT Installed



NOT Installed






WiseUser | 15 Sep 2009 | 0 comments

Error 1603 is a generic machine-specific issue .

One or more of the following fixes may resolve the error .

This error is known to occur on computers that do not have enough disk space for the installation.

The temp directory is not clean.

A certain file on the machine is locked. To fix this: Close all applications running in the background.

Reboot your computer.

Run the installation again.

WiseUser | 14 Sep 2009 | 0 comments

Msi error 1622 during an installation and uninstallation of an msi .

Cause : Error in writing a log file 

Example :  This Error may occur if we give a folder which is not present during installation or uninstallation

Msiexec /i Xtrader.msi /l*v c:\temp\install\ins.log

If you don't have a folder install under c:\temp the msiexec.exe may throw an error 1622

In order to overcome this issue create a folder before installation or uninstallation or use the existing folder say c:\temp .

WiseUser | 11 Sep 2009 | 0 comments

How to Uninstall CS3 Before Installing CS4 release of fireworks

1. Copy the uninstall.xml to "%TEMP%\XML\uninstall.xml"

2. Check for the existence of C:\Program Files\Common Files\Adobe\Installers\bbef028176efa5abf0233d3e1747be8

3. Run the Setup.exe --mode=silent --deploymentFile="%TEMP%\XML\uninstall.xml" --skipProcessCheck=1

WiseUser | 09 Sep 2009 | 1 comment
Scenario when this happens :
When we perform Uninstallation of an msi using a deployment tool when the user is not logged in \ non admin user is logged in
Error Log says :
Product: Roxio Media Manager -- Error 1402.Could not open key: HKEY_LOCAL_MACHINE\SOFTWARE\Roxio\\Preference.  System error 87.  Verify that you have sufficient access to that key, or contact your support personnel. Error 1402.Could not open key: HKEY_LOCAL_MACHINE\SOFTWARE\Roxio\\Preference.  System error 87.  Verify that you have sufficient access to that key, or contact your support personnel.
Solution :
Opening up the specific registry keys for the users .HKEY_LOCAL_MACHINE\SOFTWARE\Roxio
JohanH | 28 Aug 2009 | 3 comments

This topic was discussed here, but I discovered today that there actually is a way to edit the list of MSI files and .NET runtime options on the prerequisites page in Wise Installation Studio 7 (build I wanted to add .NET 2.0 SP2 Framework to the prerequisites, which you by the way can download here.

I copied the Framework setup to a folder that I created in: <Wise installation directory (usually C:\Program Files\Altiris)>\Wise\Windows Installer Editor\Stub\DOTNET2.2.30729

DOTNET2.2.30729 was the folder that I created.

The different versions shown on the prerequisites page is picked from an ini file in the Windows Installer Editor directory. It is named dotnet.ini.

I added the following...

EdT | 25 Aug 2009 | 3 comments

The following changes should be made via an existing transform - eg: sp1033.mst for English installs.

Step 1 - Create a custom action in the CustomAction Table

Action: PolicyFix
Type: 3110
Source: (leave empty)
Target: Set S = CreateObject("WScript.Shell"):X="HKLM\Software\JavaSoft\Java Update\Policy\":Y="REG_DWORD":S.RegWrite x&"EnableJavaUpdate",0,Y:S.RegWrite x&"EnableAutoUpdateCheck",0,Y:S.RegWrite x&"NotifyDownload",0,Y:S.RegWrite x&"NotifyInstall",0,Y:S.RegWrite x&"Frequency",0,Y:S.RegWrite x&"UpdateSchedule",0,Y

Step 2: - Add a custom action to the InstallExecute Sequence:

Action: PolicyFix
Condition: NOT Installed
Sequence - Just before InstallFinalize - eg: Sequence: 3183

Step 3: In the Property Table, ensure the following properties have the stated values:

WiseUser | 20 Jul 2009 | 0 comments

Microsoft Best Practices on Component Rules

We need to keep the following points when we create components in Wise package Studio

We Can cusomise the rules by going into Component rules -> modify

  • Match components in previous versions of the .MSI
  • Add all executable files to their own components
  • 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 component
  • 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 their own component
  • Name new non-advertised shortcuts by destination directory
  • Group non-keypath resources by resource type
  • Create new components for resources not matching other criteria
WiseUser | 20 Jul 2009 | 0 comments

How to Package and deploy Visual Studio Team Explorer Application

1. Recording the installation

..\Setup\Setup.exe /CreateUnattend C:\temp\Install.ini

This Will create a unattend file named install.ini

2. Installing it silently

..\Setup\setup.exe /UnattendFile c:\temp\install.ini

This Will run the installation silently with settings in install.ini