Software Deployment

Use a lightweight snapshotting tool, like InstallWatch or InControl, make your changes and then include the relevant files and/or registry settings in the transform you created with InstallTailor.

ok, and how can i include the files/registry-values that i captured with installwatch in my transform?

Er...in the same way that you'd add any file and/or registry data in Wise.

The simplest way to add your registry data is to export the settings to a .REG and import it into your Wise project. As for files, browse to the files highlighted as changed/added by InstallWatch and add them to the project. Remember that, as this is a transform, new files will be added in an external CAB file, which Wise will automatically name using the name of the MSI, plus a suffix TRNSFRMx, where 'x' is a number. You can rename this to suit but remember to edit the Media table entry so that the two match.

If you're not up to speed with Wise, this really ian't the place for a tutorial, I'm afraid.

ok, thanks for the help on that one! I've captured the changes with installwatch, but now i have another question though:

The file that needs to be added to the package is placed in the roaming profile folder of the user that runs the installation.
If you look at this screenshot that I've attached you will see that WISE wants to put all the files that should be in the roaming package folder
in the roaming folder of the user that I'm logged in with and running the whole instalation with (the user FRN in this case)

screenshot

How can i change this so that the files that should be installed into the roaming folder gets put in to the roaming fiolder of the user that executes the installation, so that the files isn't installed in to c:\users\FRN\etc etc

I'm guessing that the solution to this is to use some kind of variable like %userprofile% or something...


input on this one is highly appreciated!

For user profile-targetted files and registry data, you can either use Active Setup or set up a user component and have the package self-repair when the user accesses an adertised entry-point (normally a shortcut). Again, there's plenty of information here on AppDeploy about self-repair/healing.

thank you fo the quick answer, i will read up on self-repair/healing then! thanks

IMO opinion active setup should be a last resort - unless your package has no shortcuts.

Self-repair will be pretty straight forward since you've capture the app, make you you validate it though :-)


Cheers,
Rob.