Packaging SnagIt V8.22
Hi everyone,
I've managed to successfully package SnagIt 8.22; however, I've run into a minor issue pushing the package out in a lockdown environment. I've set the registry key to disable the Tip of the Day from showing. This registry key works when I log in under an Admin userID (the Tip of the Day doesn't display), but when I log in as a non-admin user, the Tip of the Day dialog pops up, even though it's set in the registry to not display at all. Does anyone have any suggestions/explanations as to why it works under Admin, but not non-admin? I've used Filemon and Regmon and it doesn't indicate that you need admin rights in order to make that registry change. Thanks for your help...
I've managed to successfully package SnagIt 8.22; however, I've run into a minor issue pushing the package out in a lockdown environment. I've set the registry key to disable the Tip of the Day from showing. This registry key works when I log in under an Admin userID (the Tip of the Day doesn't display), but when I log in as a non-admin user, the Tip of the Day dialog pops up, even though it's set in the registry to not display at all. Does anyone have any suggestions/explanations as to why it works under Admin, but not non-admin? I've used Filemon and Regmon and it doesn't indicate that you need admin rights in order to make that registry change. Thanks for your help...
0 Comments
[ + ] Show comments
Answers (13)
Please log in to answer
Posted by:
spartacus
12 years ago
Using the registry editor, navigate to the following key
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer
within this key, add a new string value named, Logging
Set the contents of the Logging value to microwaveup
Now log on as a new user who has previously not clicked the advertised shortcut and click the shortcut to allow the (defective) self repair to occur.
While still logged on as the new user, navigate to the %TEMP% folder in explorer, and search for the most recently created MSI<nnnnn>.log file (where <nnnnn> will be a randomised number). This will be the verbose log of the self repair activity for that user.
Don't forget to remove registry value mentioned above, once you have the log file.
Spartacus
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer
within this key, add a new string value named, Logging
Set the contents of the Logging value to microwaveup
Now log on as a new user who has previously not clicked the advertised shortcut and click the shortcut to allow the (defective) self repair to occur.
While still logged on as the new user, navigate to the %TEMP% folder in explorer, and search for the most recently created MSI<nnnnn>.log file (where <nnnnn> will be a randomised number). This will be the verbose log of the self repair activity for that user.
Don't forget to remove registry value mentioned above, once you have the log file.
Spartacus
Posted by:
AngelD
16 years ago
I guess this registry setting is stored under HKCU?
If so then you need to make sure the application triggers a repair on first use which in that case will install/repair the missing/broken component holding this setting.
Create a component that only holds this registry entry or some "CurrentUser" component that is repaired when the keypath for that component is missing.
If so then you need to make sure the application triggers a repair on first use which in that case will install/repair the missing/broken component holding this setting.
Create a component that only holds this registry entry or some "CurrentUser" component that is repaired when the keypath for that component is missing.
Posted by:
jsun
16 years ago
Yes, it's under HKCU. I'm fairly new to packaging, how would I set that registry key up so that it repairs itself? The registry key is under my CurrentUser feature, but not as a separate component.
Posted by:
jmcfadyen
16 years ago
Just mark it as the keypath to the component.
ensure there is some advertising in the app such as an advertised shortcut.
thats it
ensure there is some advertising in the app such as an advertised shortcut.
thats it
Posted by:
VinaySalimath
16 years ago
I am also getting the tip of the day dialog but there is no registry entry created in HKCU but a txt file within the C:\Documents and Settings\User\.The text file entry says TIP Of the Day = False.but this when i install in that machine where i captured is working fine but when i install in a clean built machine that does not happen.Could you please help me.
Posted by:
AngelD
16 years ago
From http://www.appdeploy.com/packages/detail.asp?id=287:
[HKEY_CURRENT_USER\Software\TechSmith\SnagIt\7]
ShowTipOfDay = 0 DWORD <- Do not show Tip of the day
So maybe something similar works for version 8?
[HKEY_CURRENT_USER\Software\TechSmith\SnagIt\7]
ShowTipOfDay = 0 DWORD <- Do not show Tip of the day
So maybe something similar works for version 8?
Posted by:
AngelD
16 years ago
According to Package Knowledge Base > SnagIt 8.x this version is already an MSI so you should create a transform for it instead.
Same registry settings for the "Tip of the Day" seems to apply for this one also:
HKEY_CURRENT_USER\Software\TechSmith\SnagIt\8]
ShowTipOfDay = 0 DWORD
Same registry settings for the "Tip of the Day" seems to apply for this one also:
HKEY_CURRENT_USER\Software\TechSmith\SnagIt\8]
ShowTipOfDay = 0 DWORD
Posted by:
VinaySalimath
16 years ago
Suppose you dont have a registry entry in HKCU\Software\ then you mean to create the same with the application name if so then i have tried that option also.but did not work any way this has created lot of headache to me so what i did is changed the desitination of that component to USERPROFILE.Hope it works.
Posted by:
AngelD
16 years ago
Create a new component called CurrentUser and add the registry (Registry table) to that component. Make sure to add this component to the same feature as EXE file (the shortcut runs) component resides in. So when the shortcut is launched the CurrentUser will be repaired if the registry isn't already there on the computer.
Posted by:
MARIN
16 years ago
Posted by:
AngelD
16 years ago
I even set a registry key as key.
The registry key you used as the keypath was included in the "new component"?
Make sure to use an advertised shortcut.
Is a repair triggered at all if you launch the shortcut?
A verbose log would tell you more of why the "new component" isn't repaired.
The registry key you used as the keypath was included in the "new component"?
Make sure to use an advertised shortcut.
Is a repair triggered at all if you launch the shortcut?
A verbose log would tell you more of why the "new component" isn't repaired.
Posted by:
MARIN
16 years ago
Yes I added the key to a registry key in the new component and there appears no repairscreen when I click on the shortcut.
Posted by:
zzpack
12 years ago
Just a simple question perhaps.
After a new user has logged on the computer and clicks on an advertised shortcut, then the self repair triggers. Which is fine, but it doesn´t do what I want it to do.
But how do I log that repair behavior??
After a new user has logged on the computer and clicks on an advertised shortcut, then the self repair triggers. Which is fine, but it doesn´t do what I want it to do.
But how do I log that repair behavior??
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.