robertf†Þ®×b±Ë¬²*²hœ®‹(~×(

When a user selects a wallpaper in display properties the wallpaper is
correctly loaded. After rebooting however the wallpaper is not loaded and the
user is shown a standard blue background.

If the user tries to set it again, the display properties show that it was
selected all along and the only thing the user needs to do is click 'ok' to
confirm and start the wallpaper load process...

Any suggestions? I tried redirecting the desktop, tried disabling/enabling
activedesktop but it doesn't seem to work.

robertf†Þ®×b±Ë¬²*²hœ®‹(~×(

Perhaps I should add that I'm using 2003 SP1 as server, XP Pro SP2 as client.

try this

hey_current_user\control panel\desktop\

Look for the 'Wallpaper' string value =C:\WINDOWS\Web\Wallpaper\Gateway.bmp

change it there if you want you can delete it

robertf†Þ®×b±Ë¬²*²hœ®‹(~×(

Hi,

That string value is incorrect indeed, it says profile \local
settings\application data\microsoft\wallpaper1.bmp. The correct wallpaper is
stored in the 'Convertedwallpaper' string.

I can ofcourse change it for 1 user 1 time, but I need to automate this. I
can't have users nagging that it doesn't work and changing it myself.

Regards

robertf†Þ®×b±Ë¬²*²hœ®‹(~×(

Okay, here's what happened, after your suggestion I started searching for
those wallpaper settings and I found
http://forums.whirlpool.net.au/forum...s.cfm?t=394990

Windows XP creates a bitmapped version of a JPG file but does so under
%userprofile%\LOCAL SETTINGS\application data\microsoft and directs the
wallpaper registry string you mentioned to that location. However, since
local settings are not roamed, the user needs to recreate (or actually; let
windows do that by clicking 'ok' in display options) the temporary bitmap on
every computer he/she logs in.

Now my situation was even more worrying, since I went for the delete cached
versions of roaming profiles group policy, effectively deleting the local
settings every single time. This is plain stupid programming by Microsoft, if
you provide the possibility of roaming your desktop wallpaper (which you do
by putting it in hkey_current_user) you should place the wallpaper1.bmp
temporary bitmap in APPLICATION DATA, not in LOCAL SETTINGS. That way the
bitmap is roamed as well...

Any idea how to escalate this to a team that is actually able to do
something about this?