General discussion

Locked

Setting default wallpaper

By larryalbert ·
I am trying to set a default wallpaper for all my users and prevent them from changing it. I currently have a build that they use which is on a Windows 2000 Pro machine. This was done by making changes to the registry, I have tried to duplicate it but I am not having any success. I know that this can also be done through a GP but we don't have that much control we are not able to set policies at the level I am at without going through a huge amount of red tape. Any ideas? I have consulted a registry book with has me changing the registry at HKCU\control panel\desktop also tried HKU\.default\control panel\desktop but know luck. Also tried from the Techrepublic site the adding a key under HKCU\software\microsoft\windows\currentversion and calling it system then add to strings (wallpaper and wallpaperstyle) but this did not work either.
Thanks

This conversation is currently closed to new comments.

7 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by CG IT In reply to Setting default wallpaper

group policy is applied local, site, domain and OU with local being applied only to the local machine log in for a computer belonging to a workgroup. You may change a registry key for the local machine but if you log on to a domain, the site, domain GP and domain OU GP will take prescidence over a local machine GP.

Collapse -

by larryalbert In reply to

I don't have the ability to set any group policies. That is why I need to know how to do this through the registry. Thanks

Collapse -

by CG IT In reply to Setting default wallpaper

theres a not widely used option for GP. That is loopback setting. loopback provides alternative to the default method of the ordered lits of GPOs that are applied.

There are 2 methods for loopback. replace which the GPO list is replaced by the local computer GPO at start up or merge, where the local GPO for the local computer is applied later in the list. merge method of local computer policy has precedence if it conflicts with settings in the user list at log on.

Collapse -

by CG IT In reply to

you rejects my first suggestion, however you indicate that you don't have much control over policy settings at the level you are at. I assume that you work in a AD environment and users must log on to a domain. Therefore, GPOs at the site, domain or OU level set by domain admins or enterprise admins always takes precedence over those set at the local machine level , except under special circumstances by using the loopback advanced GP option. To set the advanced GP looback option, you must be an domain administrator for the domain in which the computers belong or an enterprise administrator or have sufficent rights delegated to you to change GP.

If you are not working in an Active Directory environment with GP being applied to users are they log on, then local machine set GP is applied in which case your registry edits would apply as users are loggin in to the local machine, not on the domain.

Collapse -

by CG IT In reply to

Further, the block policy inhereitance, or no override are the only ways in which to block site, domain or OU GPO from being applied as users log on to the domain.

Collapse -

by CG IT In reply to

you can change the registry all you want but if a GPO is applied when loggin on to the domain, that will take precedence over any registry edits to the local machine as the site, domain or OU GPO overrides local machine settings.

Collapse -

by CG IT In reply to

user profiles are stored in Active Directory and not on the local machine. User settings and computer settings for those users and computers which log on to the domain are stored in Active Directory. Therefore registry edits at the local machine level are not applied in a domain AD environment specifically because of central administration of what a user sees on the desktop or has been made available to them.

Back to Windows Forum
7 total posts (Page 1 of 1)  

Related Discussions

Related Forums