Heya folks. Got an annoying problem with regards to importing registry keys.

We have created a few custom package meta data fields. For internal auditing we create a RegKey that writes application name, version number, etc...

When we import this registry into the package (Installation Expert -> Feature Details -> Registry, then click on Add -> import and add the .reg file it adds some extra characters to the fields. But only on our custom fields.


We've had to add the double ] to the end of the actual key as on import it drops the last ].

An example of how one of our custom fields imports is as follows. (With the additioanl characters in red)


Any clues, help or suggestions much appreciated.
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 have a couple apps that gave me trouble importing reg keys. What I have done is execute the key file 'branding.reg' by calling regedit from the script.

Execute %WIN%\regedit.exe /S %REG_KEY_SOURCE%\BRANDING.REG
Answered 05/01/2009 by: Foleymon
Orange Senior Belt

Please log in to comment

Have you considered updating your Windows template msi with these values? Back up you "Windows Application.msi" file from you sharepoint, then update the msi with the registry items you want in all your MSI. This way, every time you create an MSI, they will already be there.

- J
Answered 05/01/2009 by: jcarri06
Senior Purple Belt

Please log in to comment
Be careful with importing keys like [PROPERTY1], because [ will be replaced by [\[], it is better to put it in the template as mentioned, or create a macro/script that places them in the msi (wsi if you use wise) called "standardize" for example.
Answered 05/04/2009 by: sk
Senior Yellow Belt

Please log in to comment
don't ever do what Foleymon has suggested its a very bad idea.

Why people do these things I will never understand when you have a deployment solution that is designed to cater for such deployment as registry why call an external script to cater for it.

Additonal to that in locked down environments it pure fail.

If you need this quick and easy just use the automation objects to edit your installer directly. One assumes your using MSI in which case its pretty easy with some SQL update / insert commands.
Answered 05/04/2009 by: jmcfadyen
Fifth Degree Black Belt

Please log in to comment
I would have thought the easiest way would be to add to template as already suggested.
Answered 05/04/2009 by: Tone
Second Degree Blue Belt

Please log in to comment
Key inserting whilst creating an MSI is not a problem. It's when customizing manufacturer's MSI's using a transform that is the problem.

I'll look at embedding some vb code to add teh registry keys.

Answered 05/05/2009 by: ninjamaster
Senior Yellow Belt

Please log in to comment
what packaging tool are you using ?

Wise has a good method for dealing with this. I won't go into if your using IS.
Answered 05/05/2009 by: jmcfadyen
Fifth Degree Black Belt

Please log in to comment
Wise has a good method for dealing with thisDoes it? The templates are used for creating new MSIs, true, but remember the OP wants to have this information automatically included in transforms created via InstallTailor. Refer to Jim's other post http://itninja.com/question/gnu,-freeware-and-shareware-programs-to-cloning7789. I don't think Wise handles that, does it? If it does, do tell us how!
Answered 05/06/2009 by: VBScab
Red Belt

Please log in to comment
I use Wise Macro's all the time for doing just this.

Its quick and painless repeatable. Handles reference counting that templates can't.
Answered 05/06/2009 by: jmcfadyen
Fifth Degree Black Belt

Please log in to comment