It may be a question of timeing in that when the OPS is updating the info in the Mandatory profile that includes data like "screensaver" and "desktop wallpaper" the explorer shell is already loaded for the end user session and so they don't display correctly even though they are in the proper places in the registry. I would be curious if a user were able to end task on Explorer.exe in their session and start it up again if the wallpaper would should up as expected. If you're using group policies, you could set them up to "run logon scripts synchronously" which forces the explorer shell to not start untill all scripts have completed processing. This can add to your login time though (not by a ton, but sometimes even an additional 10 seconds can seem like an eternity to end users). Personally, I'm not a fan of wallpapers, and certinly not screen savers in end user sessions on TS servers (had a user somehow load up Seti@home as a screen saver on a TS box a while back . . that sure brought the TS servers to it's knees as soon as the user walked away from his desk). As is mentioned in the thread here, you can disable wallpapers on the ICA connection settings (as opposed to through grouppolicies) of each server. And of course, within grouppolicy you have the option of defining default screensaver options for end users, as well as the ability to deny them from selecting one. (assuming you're running an AD network of course w/ at least windows 2000 servers). HTH J ________________________________ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Lilley, Brian Sent: Wednesday, September 29, 2004 10:08 AM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Wallpaper My wallpaper is a picture of an Aprillia RSV 1000 Millr R with a leather clad babe sitting on top, so I disagree... actually, I have the same problem with flex on win2k and XP... -----Original Message----- From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]On Behalf Of Robert Barrett Sent: 29 September 2004 17:57 To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Wallpaper ICA connection is not set to disable wallpaper. I agree whole heartedly about wallpaper, my point has always been if you are actually doing something then your wallpaper is never visible, if you are not doing something then who cares what is on your computer as your screensaver should kick in or turn off your monitor. Bob Barrett FVSD#52 ________________________________ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of BRUTON, Malcolm, FM Sent: Wednesday, September 29, 2004 9:51 AM To: 'thin@xxxxxxxxxxxxx' Subject: [THIN] Re: Wallpaper What do you want wallpaper for ??? Most people get rid of it.... How about you look at properties on the ICA connection and verify the disable wallpaper option is not checked. Malcolm ________________________________ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Robert Barrett Sent: 29 September 2004 16:32 To: thin@xxxxxxxxxxxxx Subject: [THIN] Wallpaper Since the last one went so well, I figured I'd share another problem with you. This one falls squarely under the public relations part of the job. :-) We are using Flex Profiles and hence an underlying mandatory profile. The issue is that each user logs in and sets a pretty background and then later they logout. The next time they login the background is gone. Not really gone, because if you look in the display properties and look at the desktop tab, the background is selected, the preview is even there, but no background on the computer. Same thing with screensaver settings. The strange thing is all of the settings are saving properly in the ops file, they get loaded correctly. If a user checks the registry the entries for wallpaper and screensaver are there, but they do not get applied. It is like the ops file cannot overwrite the default user/mandatory profile settings. Any ideas? Robert Barrett MCSE, CCA Enterprise Administrator robertb@xxxxxxxxxx <mailto:robertb@xxxxxxxxxx> Phone: (780) 927-3766 Fax: (780) 926-3037 http://www.fvsd.ab.ca <http://www.fvsd.ab.ca/> ************************************************************************ *********** The Royal Bank of Scotland plc. Registered in Scotland No 90312. Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB. Authorised and regulated by the Financial Services Authority This e-mail message is confidential and for use by the addressee only. If the message is received by anyone other than the addressee, please return the message to the sender by replying to it and then delete the message from your computer. Internet e-mails are not necessarily secure. The Royal Bank of Scotland plc does not accept responsibility for changes made to this message after it was sent. Whilst all reasonable care has been taken to avoid the transmission of viruses, it is the responsibility of the recipient to ensure that the onward transmission, opening or use of this message and any attachments will not adversely affect its systems or data. No responsibility is accepted by The Royal Bank of Scotland plc in this regard and the recipient should carry out such virus and other checks as it considers appropriate. Visit our websites at: http://www.rbs.co.uk/CBFM http://www.rbsmarkets.com ************************************************************************ ******** ======================================================================== ====== This message is for the sole use of the intended recipient. If you received this message in error please delete it and notify us. If this message was misdirected, CSFB does not waive any confidentiality or privilege. CSFB retains and monitors electronic communications sent through its network. Instructions transmitted over this system are not binding on CSFB until they are confirmed by us. Message transmission is not guaranteed to be secure. ======================================================================== ====== Notice: This transmission contains confidential information intended only for the use of the individual or entity to whom it is addressed. Any disclosure, copying, distribution, or action in reliance on the contents of this transmission is strictly prohibited by anyone except the party to whom it is addressed.