Configuring Default Machines for Packaging

Are you a SVS packager? If yes then you also need the ability to use clean machines. Packaging on a clean machine is not necessary, but it helps you creating clean packages that need less editing before exporting.

Most of us use VMware to build machines, and with the clone function it is easy to have a clean environment. But you always have the need for software on the clone that you wish to have on one machine, but not on the other. Software like Adobe Acrobat, .Net versions and several others. I found a great tool free for personal use that helps me out just by editing an XML sheet.

The tool is called Installpad, and can be found on http://installpad.com/

Click to view.

When you have installed Installpad, then you simply add software to your list by clicking in the screen and choose "add new application".

Click to view.

The add new application dialog appears:

Click to view.

After you configured the software that you want on the machine the list is built in XMl format. It look like:

<ApplicationList>
 <InstallationOptions>
  <SilentInstall/>
 </InstallationOptions>

 <Application>
  <Name>Gaim</Name>
  <FileUrl>http://superb-west.dl.sourceforge.net/sourceforge/gaim/gaim-1.5.0.exe</FileUrl>

  <Options>
   <DownloadLatestVersion/>
  </Options>

 </Application>

</ApplicationList>

So, how does it work?

First of all, you install Installpad on the machine you wish to build your packages for. Installpad then creates a list of software installed on that machine, and it finds the paths it needs in the registry inside the uninstaller paths. These paths are also used by the controlpanel applett add/remove software, or appwiz.cpl.

After building the list, you export the XMl file to the new build machine, and install Installpad on that machine. The real handy people are using Installpad as a layer. That simplifies the use tremendously.

The xml sheet can be edited manually so you can select the software you need.

After you have done this just reboot the new cloned clean machine and Installpad will install all software you selected automatically.

By using the Installpad XML sheet, you will notice that you are able to use some scripting inside to do the tasks more automatically. There are several install options available.

<Application>
 <Name>Application name</Name>
 <FileUrl>application url. FTP is not currently supported</FileUrl>
 <Options>
  Download latest version, if possible
  <DownloadLatestVersion/>
  Attempt to install silently (no dialogs/questions)
  <SilentInstall/>
  Pass command line arguments to the installer
  <InstallerArguments>/s /c</InstallerArguments>
  Run a script after the installer exits
  <PostInstallScript> C:\scripts\removeDesktopShortcuts.bat </PostInstallScript>
  Alternate location to try in case the first one fails. Many <AlternateFileUrl> tags can be used for a single application 
  <AlternateFileUrl> http://mymirror.com/file.exe </AlternateFileUrl>
  Whether the item is checked by default
  <Checked>false</Checked>
  Folder to extract the zip to (if item is a zip file). Overrides location in the user's preferences
  <InstallationRoot> C:\Program files\</InstallationRoot >
  </Options>
</Application>

In the script above you will notice that you have the ability to do silent installs, or not, and that you can give alternate download locations.

In my situation I have all software located on a webserver, and it will use all software located on my webserver. This gives me control over the versions, and I'm always assured that I have clean software on paths that work.

Use it to your advantage, and get a look on this.

Regards
ErikW
www.DinamiQs.com