RunOnce Reg Key Question
I'm trying to change an IE setting that resides in the HKCU hive. I have been unsuccessful with pushing the change via an MSI so I've been messing with the RunOnce reg key.
I have three files: File 1: Registry key being pushed to HKLM > RunOnce via Altiris DS that calls the batch file below.
File 2: Batch file with a script to execute the registry key below on next logon.
File 3: Registry key that makes the change in IE under HKCU hive.
The script works great when logged in with an administrator account. However, when I push this to the same machine and log in under a non-admin domain account, the registry key never executes. It just sits in HKLM > RunOnce until I log in with an account with admin rights. From my understanding, every user has full access to their HKCU, but do they have zero access to HKLM > RunOnce key? Even unable to execute anything that resides here?
I have three files: File 1: Registry key being pushed to HKLM > RunOnce via Altiris DS that calls the batch file below.
File 2: Batch file with a script to execute the registry key below on next logon.
File 3: Registry key that makes the change in IE under HKCU hive.
The script works great when logged in with an administrator account. However, when I push this to the same machine and log in under a non-admin domain account, the registry key never executes. It just sits in HKLM > RunOnce until I log in with an account with admin rights. From my understanding, every user has full access to their HKCU, but do they have zero access to HKLM > RunOnce key? Even unable to execute anything that resides here?
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
squeakstar
14 years ago
I have certian settings applied for logon for users that apply HKCU registry settings, that specifically apply to an application these users run. I use a simple logon script .bat file which calls a registry file, which works flawlessly:
Bat File script only contains this for the registry bit plus a few other bits of stuff for mapped drives not related.
regedit /s "\\server\app\app_defaults\AppParam.reg"
the file AppParam.reg is an exported registry key with the correct settings for the app in question on a share the users have permissions to access.
For IE settings though surely there is a user group policy configuration option you could use??
Either way your methodology sounds awful convoluted....
Bat File script only contains this for the registry bit plus a few other bits of stuff for mapped drives not related.
regedit /s "\\server\app\app_defaults\AppParam.reg"
the file AppParam.reg is an exported registry key with the correct settings for the app in question on a share the users have permissions to access.
For IE settings though surely there is a user group policy configuration option you could use??
Either way your methodology sounds awful convoluted....
Posted by:
anonymous_9363
14 years ago
For HKCU stuff, either use a feature which contains an advertised entry-point - moving that feature so that it becomes a child of a new feature which contains your HKCU component - or use Active Setup.
Posted by:
dpolishsensation
14 years ago
While it is def possible through GPO, due to office politics, they want us to push this via script/msi/active setup instead of GPO. I have created an MSI with the changes but when it repairs, I'm gettin an error:
"This action is only valid for products that are currently installed."
Been a while since I worked with ActiveSetup and looking for a solution on the Internets now.
"This action is only valid for products that are currently installed."
Been a while since I worked with ActiveSetup and looking for a solution on the Internets now.
Posted by:
squeakstar
14 years ago
Office politics??? surely the method should be the simplest that works...?
anyway... cunning workaround maybe to try WinInstall LE - scan before reg tweak and a scan after reg tweak to create an MSI from that. Hopefully the MSI it creates might do the job, other than it all sounds too weird and making hardwork for yourselves... [;)]
anyway... cunning workaround maybe to try WinInstall LE - scan before reg tweak and a scan after reg tweak to create an MSI from that. Hopefully the MSI it creates might do the job, other than it all sounds too weird and making hardwork for yourselves... [;)]
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.