[font="Courier New"]
I know this is probably an old topic but I want to ask the community with a subject line that's easy to google ;) Hopefully this will answer all future questions on the matter as well.

I've seen in the Feature Request List that a request has already been made for the:
Ability to run repackager without specifying a setup executable.

I'm assuming this is not currently an option.

So, the question is: Does anyone know of a way to actually capture system registry changes ONLY without specifying a .exe file first?

I don't necessarily need to re-package anything. I need to 'package' some registry modifications. The registry changes I've been able to make from a .vbs script are not all working. Then I have to make those required changes manually in the Windows interface it's self. But, this is too much work.

I don't have the option of making an image and deploying it (eg: they won't pay for it).

If there is some way of making this happen with Repackager please let me know. If there is another way, that would be welcome as well.
0 Comments   [ - ] Hide 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.
Answer this question or Comment on this question for clarity



I don't know if there's a better way to do this, but I always get it to run an innocuous file, like c:\windows\notepad.exe.

Hope this helps,

Answered 03/08/2010 by: dunnpy
Red Belt

Please log in to comment
Dunnpy is correct. In fact, it does not matter what executable you choose as you'll be presented the opportunity to run it or not-- just choose not to run the executable and instead go make your registry edits.
Answered 03/08/2010 by: bkelly
Red Belt

Please log in to comment