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
B_Raj | 27 Oct 2009 | 1 comment

I’m here with 10 Questions & Answers to describe some of the basic things we need to take care while we approach to repackage an application.

 1.How do you Customize the vendor MSI?

 Vendor MSI’s should not be re-packaged or edited. Create a transform file to customize the vendor MSI. 

  • Some vendors supply utilities to customize their MSI behavior. Where this is the case, such utilities should be first considered as the appropriate method of customizing the MSI.  For example, use Microsoft’s Custom Installation Wizard  to customize the Office XP suite.  

2.When will you create a new MSI wrapper/ Wrapper Script?

This technique can be used in scenarios in which the installation program is not in MSI format and a setup capture is not appropriate.

Example:  Service packs and security patches

3.How do you treat INI files while repackage an...

B_Raj | 27 Oct 2009 | 0 comments

The table below lists some of  the language IDs for which the Windows Installer has

localized resource strings.


LangID           (Hex)              ACP                (Abbr)           Language (country)

 1025                 401                1256                ARA               Arabic (Saudi Arabia)

 1027            ...

B_Raj | 27 Oct 2009 | 3 comments


My intention by publishing this post is to help the newbies to understand the basics about packaging and repackaging technologies.And ofcurse for those who prepare for interviews !! :-)

 1.What is Application Packaging?

Simply Application packaging means,the process of Creation of an Installation Program for a Software. Or we can say it as creation of a setup file. Setup.exe is an installation file, a program that puts all of the files and registry keys in the right places so that everything works correctly.

  2.What is Application Repackaging?

The process of creating a customized installation using an already packaged installation is termed as Re-packaging.

The setup routine can sometimes be very complex and open to user error especially when thousands of repeat installations are required in a corporate environment. In such environments reliability and repeatability are crucial.


B_Raj | 26 Oct 2009 | 0 comments

While we deal with large windows installer packages, time required to install the package is one of the key factor in measuring the efficiency\quality of the package.

I’m briefing  here about some of the techniques that can be used to reduce the installation time of a MSI package.


The MSIFASTINSTALL property can be used to reduce the time required to install a large Windows Installer package. The property can be set on the command line or in the Property table to configure operations that the user or developer determines are non-essential for the installation.

How MSIFASTINSTALL Property will help to reduce the time?

1. This property helps to skip creating system restore point action in MSI install sequence.

2. This property helps to skip calculating the space requirements action in MSI install sequence. (Filecost)

Thus,if the developer is sure...

B_Raj | 25 Oct 2009 | 0 comments

Msispy is an utility which comes along with Windows installer SDK. If you want to troubleshoot a MSI package in component level or feature level, I will recommend this tool as the best option for repackagers.It provides a nice GUI and command line utilities which makes it very user friendly.

MsiSpy provides a component level view of the products and features installed on a system, using either an MSI Package, or the registry information. Msispy also displays the status of each, and allows you to partially or completely re-install missing or damaged items. You  can also re-configure any product or feature, selecting the install level, and specifying whether to install it locally or run it from a network server.

 Some of the main features are;

  1. It allows you to open an MSI package and display all information about it.
  2. It display information about all the products installed on the computer.
  3. Allows you to load a...
B_Raj | 24 Oct 2009 | 0 comments

This error is due to an error in Directory table of the MSI.

Generally occurs while a directory entry that references something non existent as its parent. If you ignore the ICE 03 validation error (Similar to the below mentioned Eg.) while developing the MSI,During the installation you will be getting the “Internal Error 2705. Directory” error.

Eg: of an ICE 03 error :

Orca validation reports an ICE03 error: “Not a valid foreign key; Table:Directory, Column: Directory_Parent, Key ):newfolder1″

 This error can be fixed by editing the Directory table.The wrong entries in the ‘Directory table’ will be highlighted in red colour.

WiseUser | 23 Oct 2009 | 2 comments
Success = 0
Error: General Detection error = 17301
Error: Applying patch = 17302
Error: Extracting file = 17303
Error: Creating temp folder = 17021
Success: Reboot flag set = 17022
Error: User cancelled installation = 17023
Error: Creating folder failed = 17024
Patch already installed = 17025
Patch already installed to admin installation = 17026
Installation source requires full file update = 17027
No product installed for contained patch = 17028
Patch failed to install = 17029
Detection: Invalid CIF format = 17030
Detection: Invalid baseline = 17031...
WiseUser | 22 Oct 2009 | 0 comments

When we try to install office 2007 which is 32 bit installation on a windows server with terminal services enabled you will be getting the following errors

Error Information :

Loaded Dll : \\sbc-netapp01\Install\microsoft\Sv_office_ent_2007\Enterprise.WW\OSETUP.DLL.
Catalyst version is : 12.0.4518.1014
JobExecutionMode is InstallExecutionMode.
Error: failed MsiEnumProducts ErrorCode: 2(0x2).
Catalyst execution finished: 02/08/2008 10:44:24. Return code: 30015. Exception caught: ErrorCodeOnly.
PERF: TickCount=544812 Name=RunSetup Description=End function

Solution or work around suggested for this problem

  1. Open Terminal Services Configuration.
  2. Click Server Settings.
  3. Right-click Permission Compatibility, and then click Properties.
  4. Click to select the Full Security check box, and then click OK...
WiseUser | 13 Oct 2009 | 2 comments

How to Check for prerequisite Microsoft .Net framework 2.0 installed on the machine before installation ?

1. Define a Property Name as DOTNET2 in the properties section to Null
2. In System Search Add -> Registry and do the following
   Property - DOTNET2
   Operation - Read raw value from registry
   Key -SOFTWARE\Microsoft\.NETFramework\policy\v2.0
   Value Name - 50727
3. Go to Launch Condition - Build the condition


For Checking .net version 1.0

Regvalue name is SOFTWARE\Microsoft\.NETFramework\policy\v1.1

Value is "3706-4322"

WiseUser | 06 Oct 2009 | 1 comment

1. Create your Office customization by running

setup.exe /admin

Which will open up the Office Customization tool

2. Select Create a new Office Professional Plus 2007 option

3. Take the settings as you want in the following set of options available

 a) Setup
 b) Features
 c) Additional Content
 d) Outlook

4. Save the resulting msp in the same directory

5. Run the  setup.exe with following option

 setup.exe /admin office.msp

Tips to update the patches

If we get any updates, say any patches from Microsoft then place it in Updates folder

Setup.exe has a logic to read and execute the newly found msp files from the Updates folder