run registry key
hi all,
here's a good one for you all;
i have created a package for office communicator that puts a key into HKLM\...\Run
but something is really weird, when windows starts ocs is not started. it has to be repaired first, then it works as expected.
i have never seen this behavior before. how is it possible, since the run key is present, that it does not trigger the self-healing by itself? why do i need to click the shortcut to repair it?
someone knows how to fix this?
i'm using WFWI 7
thanks all!
here's a good one for you all;
i have created a package for office communicator that puts a key into HKLM\...\Run
but something is really weird, when windows starts ocs is not started. it has to be repaired first, then it works as expected.
i have never seen this behavior before. how is it possible, since the run key is present, that it does not trigger the self-healing by itself? why do i need to click the shortcut to repair it?
someone knows how to fix this?
i'm using WFWI 7
thanks all!
0 Comments
[ + ] Show comments
Answers (6)
Please log in to answer
Posted by:
anonymous_9363
15 years ago
Just because you have an entry in the 'Run' key doesn't mean a package will repair. For that, you need to trigger an advertised entry-point. That can be a shortcut, a file association or COM+ registration.
Search AppDeploy for John McFadyen's blog on repair/self-healing.
Search AppDeploy for John McFadyen's blog on repair/self-healing.
Posted by:
AngelD
15 years ago
It could be but the executable that is launched from the Run registry entry would need to call an entrypoint (ex. COM-Component) for a self-heal to take place.
Did you use COM-Advertising or just the Registry table (hope not SelfReg) to register any COM-Component (.DLL)?
Did you use COM-Advertising or just the Registry table (hope not SelfReg) to register any COM-Component (.DLL)?
Posted by:
kardock
15 years ago
i know nothing about COM-Advertising, can you tell me where to get info on this?
thanks Angel
thanks Angel
Posted by:
AngelD
15 years ago
Do a search?
turn on advertising in the tools -> options
use WiseComCapture.exe stored in the "Program Files\...\Windows Installer Editor" folder to produce a .reg file
import the .reg file and wise should do the rest for your.
Nice step-by-step description from Ian at http://itninja.com/question/gnu,-freeware-and-shareware-programs-to-cloning2953&mpage=1&key=Ꟊ
I suggest you read "A packagers guide to the Windows Registry and COM" at http://johnmcfadyen.spaces.live.com/blog/cns!9DD01136FC094724!151.entry
turn on advertising in the tools -> options
use WiseComCapture.exe stored in the "Program Files\...\Windows Installer Editor" folder to produce a .reg file
import the .reg file and wise should do the rest for your.
Nice step-by-step description from Ian at http://itninja.com/question/gnu,-freeware-and-shareware-programs-to-cloning2953&mpage=1&key=Ꟊ
I suggest you read "A packagers guide to the Windows Registry and COM" at http://johnmcfadyen.spaces.live.com/blog/cns!9DD01136FC094724!151.entry
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.