New Boundary Support Forum
Home      Members   Calendar   Who's On
Welcome Guest ( Login | Register )
      



Prism SIFs as Custom Action in MSI filesExpand / Collapse
Author
Message
Posted 1/12/2004 4:09:00 PM
Supreme Being

Supreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme Being

Group: Advanced Members
Last Login: 1/21/2004 10:48:00 AM
Posts: 154, Visits: 1
There have been a few times lately that I have been completely unsuccessful in creating an MSI that works and that I can deploy via Win2k AD GPO. I've tried both Prism Deploy and InstallShield Admin Studio without any luck. As a work around I used Prism Deploy and just saved it as a self installing EXE - which works beautifully. I then created a basic MSI in InstallShield Developer. Add a feature, add a component and create a custom action to run the created EXE, deferred in system context if necessary, after the install initialization sequence and stored in a binary table. Works great!

Post #255
Posted 1/12/2004 4:09:00 PM
Supreme Being

Supreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme Being

Group: Advanced Members
Last Login: 1/21/2004 10:48:00 AM
Posts: 154, Visits: 1
I have done these exact series of steps to deploy:

- Google Toolbar

- Crystal Reports Developers Edition 8.5.

Here are the steps I used for the google toolbar as an example

1. I create a Prism Deploy Self Installing File (SIF) for my application - in my example I will use the google toolbar.

2. I then create a blank Prism Deploy Package and add the SIF from step #1 to a folder like "c:\program files\Install google toolbar.

3. In the folder Install Google Toolbar, I add my SIF file.

4. I then create an msi from the Prism Deploy package from steps #2 and #3.

5. I then use ORCA or better still try the new much improved MaSaI msi editor to edit the msi.

6. Create a custom action - type 18 for executable and give it a name like InstallGoogleToolbar.

7. In the InstallExecuteSequence table add a new table entry row - InstallGoogleToolbar - give it a value say of 7000 so that it is the "last item" to execute and a condition of Not Installed - so that it deploys just once - the first time that it is pushed via group policy and active directory.

8. In the File table of the msi, you should have just one item - the SIF file. Under the component column of this table you will find an entry that looks something like "InstallGoogleToolbar.EXE.14" or something like that.

9. Go back to step 6 above and add this component value (from step 8) to the "source" column of the custom action.

I have used this technique several times for msi packages that I am having difficulty creating. In affect, I am using the msi as a "wrapper" for a Prism Deploy SIF! - which I find deploys without problems

Creating Prism Deploy packages I find are much easier and more reliable than msi packages but we are using active directory and group policy so msi's are the the direction we must use.

I hope this helps anyone creating msi packages from Prism Deploy. In most cases, you can just save your pwc file as an msi but if the resulting msi does not deploy properly try this "wrapper" technique.

John Falloon
Software Specialist
British Columbia Securities Commission
Vancouver, BC
Canada

Email: jfalloon@bcsc.bc.ca

Post #256
« Prev Topic | Next Topic »


Reading This TopicExpand / Collapse
Active Users: 0 (0 guests, 0 members, 0 anonymous members)
No members currently viewing this topic.
Forum Moderators: New Boundary Support

PermissionsExpand / Collapse

All times are GMT -6:00, Time now is 11:01am

Powered By InstantForum.NET v4.1.3 © 2008
Execution: 0.359. 12 queries. Compression Enabled.