IIRC, I ran into the same problem using (I assume you are) the built-in deployment wizard. The solution I ended up using ran something along the line of choosing to "save this package for later use," which creates a bunch of files used in BUILDING the installer file. Then, just poke around... it's a fairly rudimentary scripting language, but much can be accomplished.