has anyone got any advice on how to convert sms installer scripts (.ipf) to .msi format

I can't use the legacy convertor tool becuase I will lose all the logic in the scripts

a lot of the scripts have conditions which are set on the fly.

I need to give feedback on my findings

the client wants to go with the msi format as they are moving to sccm 2007 [:@]
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Wow people are still writing IPF scripts? [;)]

I'm not aware of any easy way to do this.. sounds like you will be busy for a while!
Answered 09/18/2009 by: MSIPackager
Third Degree Black Belt

Please log in to comment
0
Wise Package Studio 7.0 SP3 Release Notes
https://kb.altiris.com/article.asp?article=41456&p=1

Enhancements and changes in Windows Installer Editor 7.0 SP3
Abstract:
Convert .EXE, WSE, and .IPF installations to Windows Installer format.
A new tool lets you convert the following script-based setup programs into Windows Installer packages: Microsoft SMS (.IPF, .EXE) and WiseScript (.WSE, .EXE).
To do so, select Tools menu > Convert WiseScript Installation or SMS Installer.
(In Visual Studio: Project menu > Convert WiseScript Installation or SMS Installer.)
Answered 09/18/2009 by: AngelD
Red Belt

Please log in to comment
0
my question is how can you preserve all the on the fly logic in the .ipf file if I convert to wsi or ism

these are scripts that have been written from scratch
Answered 09/18/2009 by: cygan
Fifth Degree Brown Belt

Please log in to comment
0
I wouldn't imagine for a second that the script logic would be transferred. As Rob says, you're going to be busy.
Answered 09/18/2009 by: VBScab
Red Belt

Please log in to comment
0
how reliable are sms .exe's can they be wrapped in an msi
Answered 09/18/2009 by: cygan
Fifth Degree Brown Belt

Please log in to comment
0
how reliable are sms .exe's can they be wrapped in an msi1. Wouldn't that depend on the content and/or the quality of the author's code?
2. If they don't extract and execute an MSI, I don't see why not.

EDIT:
Found this http://www.myitforum.com/articles/6/view.asp?id=488
Answered 09/18/2009 by: VBScab
Red Belt

Please log in to comment
0
thanks guys

next week is decision time with the bosses
Answered 09/18/2009 by: cygan
Fifth Degree Brown Belt

Please log in to comment
0
next week is decision time with the bossesAh ha! That'll be the decision to have a meeting, at which they'll decide when the next meeting will be.
Answered 09/20/2009 by: VBScab
Red Belt

Please log in to comment
0
Ah ha! That'll be the decision to have a meeting, at which they'll decide when the next meeting will be

I think you are spot on.

basically a complied .ipf into and exe is a scripted installation which is based on a procedural model providing the scripted instructions

however windows installer is based on a data driven model hence the installation data in the different installation tables.

the way I look at it I will be going for the wrapping of the .exe's

there are lot's of logic in the many sms .exe's that will require massive amounts of vbs scripting and more logic if they decide to go with vbs

a custom action can run the sms exe silently for the install and uninstall
anyway I look at it msi will not really come into the picture
Answered 09/21/2009 by: cygan
Fifth Degree Brown Belt

Please log in to comment
Answer this question or Comment on this question for clarity