Word Macro as Entry Point
Does anyone know of a way to create entry points other than file association and icons.
I have a few apps that have MS Word macro's associated with them, macro security requires the user 'enable' the macros when they run Word. I can capture these keys, and 'trust' the macro publisher, but these are HKCU keys and obviously only get healed if you use an entry point to the package.
What I want is to be able to define the word macro as an entry point, therefore if the user runs Word before running the app they won't be prompted to enable/disable the macros.
any help appreciated, thanks,
I have a few apps that have MS Word macro's associated with them, macro security requires the user 'enable' the macros when they run Word. I can capture these keys, and 'trust' the macro publisher, but these are HKCU keys and obviously only get healed if you use an entry point to the package.
What I want is to be able to define the word macro as an entry point, therefore if the user runs Word before running the app they won't be prompted to enable/disable the macros.
any help appreciated, thanks,
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
DuncanPaul
19 years ago
have thought of a fairly rubbish way around it, if I don't include the template as part of install, but launch from (say) run key a script which copies the template into folder, but have HKCU keys as keypaths, then they'll get healed before user has run word.
it would be nice however to be able to create other types of entry points if this is possible.
it would be nice however to be able to create other types of entry points if this is possible.
Posted by:
foxbat5
19 years ago
For any apps which don't have an entry point and need HKCU key's I use Microsoft Active Setup to refresh the key's at login from a .reg file.
This is built into windows and does the job for free
Basically I export all HKCU keys's to a .reg file , deliver the file to an appropriate folder ....eg c:\program files\[vendor]\[AppName]
You'll then need to setup a key under the following HKLM path.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components\[AppName]
StubPath = REG IMPORT "C:\Program Files\[Vendor]\[AppName]\[File].reg"
Version = 1
The above is written to the machine at MSI runtime , when windows logs in for each subsequent user Windows compare the key's in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components with the ones under HKCU if they[:)] are not present it runs the reg import delivering your HKCU key's without user intervention , the process can also be set to refresh at each login or just once but will hit each new user when they login. Not as good as MSI's repair but better than user interactions.
This is built into windows and does the job for free
Basically I export all HKCU keys's to a .reg file , deliver the file to an appropriate folder ....eg c:\program files\[vendor]\[AppName]
You'll then need to setup a key under the following HKLM path.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components\[AppName]
StubPath = REG IMPORT "C:\Program Files\[Vendor]\[AppName]\[File].reg"
Version = 1
The above is written to the machine at MSI runtime , when windows logs in for each subsequent user Windows compare the key's in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components with the ones under HKCU if they[:)] are not present it runs the reg import delivering your HKCU key's without user intervention , the process can also be set to refresh at each login or just once but will hit each new user when they login. Not as good as MSI's repair but better than user interactions.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.