I looked at the AppSearch and RegLocator Tables and possibly passing the value into a property however it doesnt read in the data value. I believe this can be done via InstallScript but have never used this so would need a step-by-step process for it that I could follow. I'm using Installshield 2012.

Existing environment reg value to read:  HKLM\SYSTEM\APP\KEY     StringName=Variable1
New reg value to write:                         HKLM\SYSTEM\APP\KEY     StringName2=Variable1

Answer Summary:
Cancel
1 Comment   [ + ] Show Comment

Comments

  • Forget script. You were on the right lines using the tables. If that didn't work, you made a mistake somewhere.

    Post the content that you had in those tables and we'll figure out where you went wrong.
    • Thanks VBScab.

      RegLocator Table:
      Signature: AppVersion
      Root: 2
      Key: SYSTEM\CurrentControlSet\Services\NetLogon\Parameters\SystemVersion
      Name:
      Type: 2

      AppSearch Table:
      Property: VERSIONID
      Signature_: AppVersion

      Registry Table:
      Registry: 1
      Root: 2
      Key: System\CurrentControlSet\Services\NetLogon\Parameters
      Name: InternalVersion
      Value: [VERSIONID]
      Component: ISRegistryComponent
      Attributes: 0
Please log in to comment

Community Chosen Answer

1

Hi guys,

I found my error. The stringvalue was listed in my key section as oppose to the Name value in the RegLocator table. Can't believe I missed that. Cheers for the help.

 

Answered 03/20/2014 by: Busby101
Yellow Belt

Please log in to comment

Answers

0

You can create a vbscript for this and put that in a Custom Action.

Answered 03/20/2014 by: SilentKiller
Orange Belt

  • Thanks, if I can handle it natively using the tables I'd rather avoid the use of CA scripts if possible.
Please log in to comment
Answer this question or Comment on this question for clarity