| |
Creating MSI Packages |
|
| |
By Erik
Rozman
|
|
| |
An MSI package is used by the Windows Installer
service on client computers as a set of instructions to install software. Most
of the new software released today comes with an MSI package included
yet we may own old software that does not include MSI files, if we want
to deploy the old software using Group Policy Objects we need either an MSI
package or a ZAP files(scripted installation).
There are two solutions
in regard to non-existent MSI files:
The first is to turn to the software vendor and ask for an update copy of the software that includes
an MSI file.
The second solution is a bit simpler - create your
own MSI file. The Windows 2000 CD includes additional software that will aid
you in creating the MSI files.
|
|
| |
Veritas Software Console and WinINSTALL
Discover
The conceptual steps that you will take in order to create
the new MSI file for your software can be described in 6 steps:
- Installing the "author" software
- Creating a template computer
- Taking a before snapshot
- Installing the "old" software
- Taking an after snapshot
- Using the MSI
Installing the "author" software
Before you begin creating MSI files you have to find the
software needed to create it and it can be located on the CD at this path:
\vlaueadd\3rdparty\mgmt\winstle.
You run the MSI file
found in the directory which in turn provides the information for the software
installation-no user interaction occurs at this stage. The applications are
installed as a default in the local drive of your Windows 2000 installation at
the path of \Program Files\Veritas.
At this stage you may be
asking yourself on which computer did I install the software? The answer to
that will come in the next stages.
Creating a template computer
Before you begin you need a computer with only the
operating system and service packs installed. As you can see from the 6 points
I outlined the "author" software is actually going to capture the differences
between the computer without the software and the computer with the software
and translate these differences into an MSI file.
To make this process
effective you need to give the "author" software a clear view of your system
before and after the installation. Not even the software for taking the
snapshot should be installed on the template computer, it should be used
through a share from a different computer.
Taking a before
snapshot
As we said earlier you should run the software from a
share on a computer that you installed it on-the trick here is that you do not
need to create a new share for this specific purpose you can take advantage of
the existing administrative shares. If you have administrative privileges on
the computer that you installed the "author" software you can reach the
software by using the following path:
\\comp_name\drive$\Progaram
Files\Veritas software\Winstall\discoz.exe
After the initial welcome
screen you are asked to provide information on different subjects. |
|
| |
 |
|
| |
 |
|
| |
Installing the "old" application
At this stage the computer will go through a scan and stop by asking you to
provide the installation for the "old" application you want to use:
Once you
provide the location the installation of the "old" application begins. During
the installation provide the "old" software all the information you need and
use it as a template installation since this installation will be used for the
MSI file.
After the installation finishes it is recommended to reboot
the computer. After the reboot you may configure the application for specific
needs-these changes will reflect upon the installations made by the MSI file.
|
|
| |
Taking the after snapshot
At this stage you have to run the WinINSTALL program again,
this time the application identifies it's position and offers you two options: |
|
| |
 |
|
| |
The computer goes under scanning again and
changes are identified, at the end you receive a window stating problems that
may arise: |
|
| |
 |
|
| |
Using the MSI Congratulations(don't you hate it
when wizards congratulate you?), you now have an MSI file to be used for
automatic deployement. |
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
By Erik Rozman MCT,
MCSE, MCSA, MCP+I, CCNA, CNA
|
|
Consulting Articles 
