QuickTime 7.6.4 Auto-update
I know this subject has been beaten to death but I have tried so many ways to get rid of the "Check for updates automatically" checkbox to be unchecked. I have created a transform and copy over the qtp file and it only works in my profile. I have read a post from Nick about resource hacker but I cannot find out how to even use the tool. I have been working on this off and on for three weeks now and cannot get this to work. I created a VBScript to copy over the qtp file but it doesn't seem to always work. I am pretty new to the world of packaging and need to deploy this out to 3500 machines. Thanks for any help you can provide me!
0 Comments
[ + ] Show comments
Answers (8)
Please log in to answer
Posted by:
djain3
15 years ago
Posted by:
Nitroglycerin
15 years ago
Posted by:
Nitroglycerin
15 years ago
Posted by:
Nitroglycerin
15 years ago
Posted by:
pjgeutjens
15 years ago
ok, quick rundown of Active Setup.
1) You create a registry key in HKLM\Software\Microsoft\Active Setup\Installed Components\<Some Name>, and a value StubPath=<command> , value Version = 1.0.0
2) Every time a user logs on, windows will check to see if the corresponding HKCU\Software\Microsoft\Active Setup\Installed Components\<Some Name> key exists
- If it doesn't, Windows will execute the command in StubPath and write the key to HKCU
- if it does exist, Windows will check the Version value, if it's higher in HKLM than in HKCU , the command will execute again and HKCU is updated, if not, nothing happens
So basically you can make a command (exe, vbs, msi repair, whatever) execute once for every user the next time he logs on, this way you can for example write registry keys in their HKCU hive. By increasing the Version value you can make a command execute again for users.
This functionality results in the "Applying personal settings for Application X" dialog boxes you've undoubtedly seen before
Hope this helps,
PJ
1) You create a registry key in HKLM\Software\Microsoft\Active Setup\Installed Components\<Some Name>, and a value StubPath=<command> , value Version = 1.0.0
2) Every time a user logs on, windows will check to see if the corresponding HKCU\Software\Microsoft\Active Setup\Installed Components\<Some Name> key exists
- If it doesn't, Windows will execute the command in StubPath and write the key to HKCU
- if it does exist, Windows will check the Version value, if it's higher in HKLM than in HKCU , the command will execute again and HKCU is updated, if not, nothing happens
So basically you can make a command (exe, vbs, msi repair, whatever) execute once for every user the next time he logs on, this way you can for example write registry keys in their HKCU hive. By increasing the Version value you can make a command execute again for users.
This functionality results in the "Applying personal settings for Application X" dialog boxes you've undoubtedly seen before
Hope this helps,
PJ
Posted by:
Nitroglycerin
15 years ago
Posted by:
aogilmor
15 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.