An Error Occurred Opening The Default Desktop Registry Key Bginfo
Contents |
Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 01 September 2005 Location: Portugal Status: Offline Points: 1 Post Options Post Reply please ensure the current user has rights to change logon desktop settings Quotetiagonmas Report Post Thanks(0) QuoteReply Topic: Error when applying BGInfoPosted: 01
Bginfo An Error Occurred While Attempting To Set The New Desktop Settings
September 2005 at 5:50am Hi There! All went well when I run bginfo on my first server but
What Is Bginfo
when loggin on to the second server with my administrator account with a roaming profile it gives me an error when trying to apply: "An error occured while attempting to set
Bginfo Windows 10
the new desktop settings.Please ensure that the current user has rights to change desktop settings:Cannot create a file when that file already exists" Can you help me ? What file already exists ? thanks, Tiago gawarecki Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 29 November 2005 Status: Offline Points: 2 Post Options Post Reply Quotegawarecki Report Post Thanks(0) QuoteReply Posted: 29 November 2005 at 3:12pm I get a very similar problem using v4.7 on Windows XP. Error text is: An error occured opening the Default Desktop registry key. Please ensure the current user has rights to change Logon Desktop settings: Access is denied. Sure would be nice to know *which* registry key the program is looking for. The problem does not happen for the Administrator, just everyone else (including me). The shortcut running BGInfo is placed in "All Users" startup group. The configuration file is placed in my folder, which all users can read, but not write to. That should not be a factor, for I get the error too. If I remove the "/timer:0" from the shortcut, the error happens after the timer reaches zero, so the error must happen due to saving of information versus reading data. I am inexperienced as to changing logon settings, and so the error is of little instruction to me. A look through the "Help" for "Computer Management" and "Local Security Policy" showed nothing for "Logon Desktop". For what it's wo
Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing http://forum.sysinternals.com/error-when-applying-bginfo_topic1109.html Store Headlines Experts Exchange > Questions > How can I run a bginfo fix reg key on startup for standard users? Want to Advertise Here? Solved How can I run a bginfo fix reg key on startup for standard users? Posted on 2010-01-22 Windows XP https://www.experts-exchange.com/questions/25077626/How-can-I-run-a-bginfo-fix-reg-key-on-startup-for-standard-users.html MS Legacy OS Windows OS 1 Verified Solution 2 Comments 2,286 Views Last Modified: 2012-05-08 Good Morning Experts, I have an issue with BGINFO that is almost solved. Basically group policy runs this batch file: ============== @ECHO OFF SET BGINSTALL=\\%DOMAIN%\netlogon\bginfo\bginfo.exe SET BGCONFIG=\\%DOMAIN%\netlogon\bginfo\walser.bgi SET BGSETAS=\\%DOMAIN%\netlogon\bginfo\bginfo.vbs regsvr32 /s shimgvw.dll regedit /s \\\%DOMAIN%\netlogon\bginfo\bginfofix.reg %BGINSTALL% %BGCONFIG% /nolicprompt /timer:0 /silent cls GOTO END :END EXIT ============ And this works great, but I ran into the issue where users would do the setas background. I fixed that with a registry change, which is reflected in the batch above. However, when a normal user logs in they don't have the priviledges of editing registry, and that batch doesn't take place and the user can still do a setas background. Here are the registry changes: [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\ActiveDesktop] "NoChangingWallPaper"=dword:00000001 [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\System] "WallpaperStyle"="2" "Wallpaper"="\\\\%DOMAIN%\\netlogon\\bginfo\\walserbackground.jpeg" Si
Server Microsoft Windows Server 2012 Join the Community! Creating your account only takes a few minutes. Join Now Have been trying to get Windows Server https://community.spiceworks.com/topic/1276295-set-wallpaper-on-rds-host-server-sessions-how 2012 R2 RDS host servers to have a default desktop wallpaper when users log in. Can not use the standard Admin Templates / Desktop / Desktop / Wallpaper GPO b/c it does not apply to remote desktop sessions. Have tried GPP to set registry entries but either Windows 2012 R2 did away with these items or they just don't work for some other an error reason...I could not browse to them and pasted them in. Have tried BGInfo in a logon script but keep getting this error: 'An error occurred opening the Terminal Services registry key. Please ensure the current user has rights to change desktop settings: Access denied.' I can NOT find ANYthing that tells what this KEY is to enable it. All users logging into RDS host an error occurred servers are standard domain users. I've enabled as many policy things as I can find or read about, I've set BGInfo to run as administrator... BGInfo script says: \\fp1\logo$\bginfo.exe \\fp1\logo$\mso_logo.bgi /timer:0 /nolicprompt Is there any way at all to get RDS host servers to have a default desktop wallpaper?? Thank you, Tom Reply Subscribe RELATED TOPICS: Imaging RDS host servers for deployment   14 Replies Habanero OP Justin1250 Nov 5, 2015 at 7:00 UTC TomMLS wrote: Have been trying to get Windows Server 2012 R2 RDS host servers to have a default desktop wallpaper when users log in. Can not use the standard Admin Templates / Desktop / Desktop / Wallpaper GPO b/c it does not apply to remote desktop sessions. Thank you, TomThis should work fine. You just need to turn on loopback processing. 1 Poblano OP TomMLS Nov 5, 2015 at 7:07 UTC Microsoft explicitly states that that Desktop/Desktop Wallpaper policy does not work for remote desktop sessions; this disclaimer is at the end of the policy description. Loopback processing is enabled for all the RDS group policy objects. Thank you, To