Registry Entries
Hello Forum,
I´m new with the Repackager.....We have a programm installation (setup) that we want to convert into a msi file.
The problem is, the programm generates an entry in the "Path" String of the system variable.
This is the affected reg Key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment
Name: Path
Typ: REG_EXPAND_SZ
Standard Value: %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32;
The Programm installation generates at the end of the value a new entry, like this:
Value: %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32;C:\TEST\TEST1
The problem is, that the MSI File don´t generates this registry entry.
I´ve look into the XML File. There is a regsitry entry to this key, but I can´t see the content.
I think it is not set.
Anyone have a trick to solve this problem?
Thanks a lot!
I´m new with the Repackager.....We have a programm installation (setup) that we want to convert into a msi file.
The problem is, the programm generates an entry in the "Path" String of the system variable.
This is the affected reg Key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment
Name: Path
Typ: REG_EXPAND_SZ
Standard Value: %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32;
The Programm installation generates at the end of the value a new entry, like this:
Value: %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32;
The problem is, that the MSI File don´t generates this registry entry.
I´ve look into the XML File. There is a regsitry entry to this key, but I can´t see the content.
I think it is not set.
Anyone have a trick to solve this problem?
Thanks a lot!
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
bkelly
14 years ago
Recipe files don't include values by design so they may be safely shared with others. The value is actually based on that of the computer on which the MSI is generated. If you wanted to update this to be dynamic based on the existing contents of the current path, you would need to update the MSI after it was created as this is not a supported scenario within the AppDeploy Repackager itself.
There are several other threads addressing this problem, one that seems to provide a lot of answers can be found here: http://itninja.com/question/how-do-you-roll-out-new-machines?1840
There are several other threads addressing this problem, one that seems to provide a lot of answers can be found here: http://itninja.com/question/how-do-you-roll-out-new-machines?1840
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.