Software Deployment

Try to validate the MST and check

I will do but this is an MST that gets created with the Wise software. I make NO changes to it so unsure why it should fail :#

When viewing the MST in Wise, any errors should be shown with the offending cell highlighted in red, making it reasonably straightforward to trace the error path.

Try creating MST using Install Tailor n give a try

Universal transform will create a feature table entry by default which may cause problem during installation

This universal transform that gets created with Wise is riddled with errors by default.... :#



Try creating MST using Install Tailor n give a try

Universal transform will create a feature table entry by default which may cause problem during installation


How do I create teh Base MST though with Install Tailor as it's looking for an MSI to run? Do I create a "blank" MSI?

All I'm looking for is a branded MST (With some reg keys and stuff) that can be run as Base when creating MST's with manufaturer supplied MSI's?

Open Vendor provided MSI and change some property values if required or do some changes and "Save As" MST.

This will defenetly install the application with MSI and newly created MST

I don't think my question is being understood :p

I know how to create an transform for an MSI. What I'm trying to do is create a transform that I can use as the base MST which has some branding information (regkeys and the like) that I can use against *every* other transform that I create from a vendor provided MSI.

I thought by creating a "Universal Transform" through Wise was the answer but seems to have loads of validation errors.

I'll create an empty MSI and run that to create by base MST.

I know how to create an transform for an MSI. Perhaps not. A Universal transform starts off with a completely blank MSI, i.e. with no tables whatsoever. Your idea of using a blank MSI and saving it as an MST with your changes makes sense. I don't think Wise uses templates for transforms, though, does it? That means you'd have to add the base MST to each of your deployments or merge it with any response transforms you create.

ORIGINAL: VBScab

A Universal transform starts off with a completely blank MSI, i.e. with no tables whatsoever.

If thats the case then why, when running this created MST (and no chances made to it) does it error as initially explained?

When you start up a new project and choose "Customize MSI using transform" you can state there a "Base MST". This is the transform that I'm trying to create that has our branding in it so save me having to import some regkeys and the like everytime we're creating a transform from a vendor MSI. Currently doing this manually but it's causing problems (See http://itninja.com/question/gnu,-freeware-and-shareware-programs-to-cloning7740)

I've written some VB that can run embedded in the MST but can't create a base one.

:@#

You use WORKBENCH?!?!? That must make...what...three of you. LOL...

Anyway, here's what it says in WB (with my emboldening):1. Double-click the InstallTailor icon.

A Welcome dialog appears.

2. Complete the dialog:

nWindows Installer package

Specify the installation file (.MSI) or transform file (.MST) to create a transform for.

nBase MST file

Specify a transform to apply to the installation.

3. Click Next.

If you specified a transform file, you might be prompted to specify the base .MSI, if that information is not embedded in the transform. I think you have misunderstood how that dialog is meant to be used. It means you choose either an MSI for which you want to create a response transform OR you choose an existing MST to which you want to apply more changes.

You will find your time more productively used if you create a script, onto which you can drop MSTs which you create, so that your branding and such gets added. The same script could also be used for a pre-QA flight check. Alternatively, you can create your base MST and, as I mentioned, simply add it to each deployment, alongside the actual response transform.

ORIGINAL: VBScab

You use WORKBENCH?!?!? That must make...what...three of you. LOL...


As opposed to???

Shortcuts in the Quick Launch toolbar?

Unless you use the workflow/process list? In that case, how about a more configurable and capable workflow tool? I edited a freely-downloadable ASP-based tool from Planet Source Code and use that. The beauty is that it can be turned to any workflow process and isn't bogged down in the Wise UI. The only thing I haven't turned it to doing is running the Wise tools but I don't miss those.

ORIGINAL: VBScab

That must make...what...three of you. LOL...


<raises hand> Make that 4 :) hehe.

ORIGINAL: ninjamaster
What I'm trying to do is create a transform that I can use as the base MST which has some branding information (regkeys and the like) that I can use against *every* other transform that I create from a vendor provided MSI.
Why not create a merge module which includes one or more custom action to read properties and alike to "install" the branding information.
The MSM you would just include in any transform.