Permission issue on the HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\Control Panel\Desktop
Hi
I want to change the screensaver for all the users in my enterprise but its not letting me change th esettings under the Key : HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\Control Panel\Desktop
It is giving me an error message as : Cannot create key.Error while opening key policies
The users dont have the right to edit this particular key.I tried to use the Run as functionality as well but the values get reflected for that particular user not the normal user.
Is there a way to change the permission on the Policy Key for all the users for editing.
I want to change the screensaver for all the users in my enterprise but its not letting me change th esettings under the Key : HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\Control Panel\Desktop
It is giving me an error message as : Cannot create key.Error while opening key policies
The users dont have the right to edit this particular key.I tried to use the Run as functionality as well but the values get reflected for that particular user not the normal user.
Is there a way to change the permission on the Policy Key for all the users for editing.
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
dunnpy
13 years ago
Meera,
This kind of thing can be handled with AD group policy.
I've done one recently where I've packaged the screensaver files and deployed them to machines and then changed the GPO to reflect the new screensaver once deployment coverage was sufficient.
Thanks,
Dunnpy
This kind of thing can be handled with AD group policy.
I've done one recently where I've packaged the screensaver files and deployed them to machines and then changed the GPO to reflect the new screensaver once deployment coverage was sufficient.
Thanks,
Dunnpy
Posted by:
Star
13 years ago
We do not have the AD in place. It is still under the implementation phase.The policies were defined on the WINNT environment.
Any other solution for the same?
Any other solution for the same?
Posted by:
dunnpy
13 years ago
A quick search of the appdeploy message boards throws up this which seems to be your solution.
Thanks,
Dunnpy
Thanks,
Dunnpy
Posted by:
faithkim
13 years ago
hi,
what happens if you use Active setup using Vbscript?
to do this, Create 2 vbscript.
- 1st script : copies vbscript somewhere in your folder & set Active setup to call 2nd script at next logon
- 2nd script : this will run at the next logon and this contains code to set HKCU keys/values
just an idea.
what happens if you use Active setup using Vbscript?
to do this, Create 2 vbscript.
- 1st script : copies vbscript somewhere in your folder & set Active setup to call 2nd script at next logon
- 2nd script : this will run at the next logon and this contains code to set HKCU keys/values
just an idea.
Posted by:
Star
13 years ago
Hi,
I did think of using the Active Setup but my biggest problem here is that I dont want to use the .msi file here.It would just be a file drop and then merging the Registry key with the help of the .bat file
The links that was provided was apt for my environment but it did not work.
Its not making any changes on the policies key.In our environment its not editable and blocks the screensaver to be applied.
Is there any other way of editing the polices key and/or use some other way to see the new screensaver on the machines?
Please suggest.
I did think of using the Active Setup but my biggest problem here is that I dont want to use the .msi file here.It would just be a file drop and then merging the Registry key with the help of the .bat file
The links that was provided was apt for my environment but it did not work.
Its not making any changes on the policies key.In our environment its not editable and blocks the screensaver to be applied.
Is there any other way of editing the polices key and/or use some other way to see the new screensaver on the machines?
Please suggest.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.