Lets say I have an application in my unattended OS install that is all tweaked the way I want it. How do I merge all the tweaks in one install file so I can deploy it with SMS or any other deployment system.

Let's take for exemple Quicktime 6.52.

1. QuickTimeFullInstaller.exe must be in the same directory as QuicktimeInstaller.ini
2. I have some registry tweaks that must be imported.
3. I have to copy quicktime.qtp in a target directory.
4. I have some registry and / or desktop cleanup to do after the installs.

Now all that is easy to do in my unattended OS install with batch files, etc. But how do I put all those steps in 1 file so it can be deploy via a deployment system like SMS.

I know it's basic but I gotta start somewhere.

Thanks
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
Answered 05/06/2005 by: VikingLoki
Second Degree Brown Belt

Please log in to comment
0
Thanks for the link. Unfortunately I already knew what was on that page. The only thing I'm wondering is how to make a .msi or exe with all those steps.

I'm not looking for tweaks on Quicktime in particular, I'm looking for general info on what to do when you have all the tweaks and commands you need to install an application and you want to pack that in a nice clean file, either .msi or exe.

Is this what repackaging is?
Answered 05/06/2005 by: qafyg
Senior Yellow Belt

Please log in to comment
0
Repackaging is the process of making a custom version of the setup (normally to allow a slient deployment or to generate a needed setup fromat (msi)) - this is normally done by taking a before and after snapshot of a system where you install the setup to determine the changes it makes. If you have a command line installation you are happy with, you probably do not need to repackage anything.

While a simple batch file would be the easiest approach, you could put your command line installation in an executable using WiseScript or the Admin Script Editor, but to make it an MSI would not gain you anything unless you need to assign the setup via group policy. Placing your command line setup in an MSI involves creating a custom action and it is not too trivial a process.- depending on the tools you have at your disposal. I am actually about to place a couple of videos on AppDeploy for using custom actions in this way with both AdminStudio and Package Studio in the very near future.
Answered 05/06/2005 by: bkelly
Red Belt

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