How to configure a component to setup registry only on Repair?
Hello,
I'm trying to configure registry settings that only apply after the advertised shortcut has been started.
I'm using the following condition for the component:
MaintenanceMode="Modify"
Component is configured with both HKCU dummy entry as a keypath and the actualy HKLM entry I need to set.
Installation log file:
Component: TESTCOMPONENT; Installed: Absent; Request: Local; Action: Null; Client State: Unknown
InstallShield 10:36:34: Attempting to determine component state for TESTCOMPONENT
InstallShield 10:36:34: Install state of component is 2, action is ffffffff
When I start the advertised shortcut - repair is not run. I presume it's because the component state is not re-evaluated somehow. And of course - because it's being started by the same local admin account that ran the initial .msi installation.
Can someone point me in the right direction please? ;)
I'm trying to configure registry settings that only apply after the advertised shortcut has been started.
I'm using the following condition for the component:
MaintenanceMode="Modify"
Component is configured with both HKCU dummy entry as a keypath and the actualy HKLM entry I need to set.
Installation log file:
Component: TESTCOMPONENT; Installed: Absent; Request: Local; Action: Null; Client State: Unknown
InstallShield 10:36:34: Attempting to determine component state for TESTCOMPONENT
InstallShield 10:36:34: Install state of component is 2, action is ffffffff
When I start the advertised shortcut - repair is not run. I presume it's because the component state is not re-evaluated somehow. And of course - because it's being started by the same local admin account that ran the initial .msi installation.
Can someone point me in the right direction please? ;)
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
anonymous_9363
13 years ago
Component is configured with both HKCU dummy entry as a keypath and the actualy HKLM entry I need to set.
Remember that components are only repaired if the data is missing. If the package wrote the HKLM entry when it was instaled, there's no need for it to be repaired.
Posted by:
GrGrGr
13 years ago
Components keypath is set to a HKCU entry. That entry is not applied during initial setup because the condition of the component states it should only run on repair. Presuming the components' condition logic is configured correctly.
I've checked and the HKLM entry from that component is not applied too.
I've checked and the HKLM entry from that component is not applied too.
Posted by:
pjgeutjens
13 years ago
just the HKLM entry should be enough to trigger the repair if set as keypath, and assuming the component is conditioned with something like INSTALLED or your MaintenanceMode =...
Just be sure to set the component's transitive bit (reevaluate condition)
PJ
Just be sure to set the component's transitive bit (reevaluate condition)
PJ
Posted by:
GrGrGr
13 years ago
ORIGINAL: pjgeutjens
just the HKLM entry should be enough to trigger the repair if set as keypath, and assuming the component is conditioned with something like INSTALLED or your MaintenanceMode =...
Just be sure to set the component's transitive bit (reevaluate condition)
PJ
Thank you, the transitive bit did the trick and it indeed worked and re-evaluated conditions on full repair (/famus). The question now is - can you re-evaluate conditions without forcing a full repair? Or running repair only on one feature instead?
The condition re-evaluation does not run when starting an advertised shortcut, btw, which is also disappointing.
Posted by:
jmcfadyen
13 years ago
you can set a CA to force evaluating a condition should it be an issue.
session.doaction
session.evaluatecondition
should help you out there.
session.doaction
session.evaluatecondition
should help you out there.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.