locked
Desktop background is blank via remote desktop. RRS feed

  • Question

  • When I connect to WHS via remote desktop, the background does not appear.  I've check the box in the options to allow for desktop background but when connected, it's black.  Inside desktop properties, the options for background are lock and greyed out.  I can change this only when I am hooked up to the WHS directly with a monitor.  I don't have this problem when I connect remotely to my HTPC.  This is all in the same network.  Any suggestions on why this is happening?
    Wednesday, December 12, 2007 8:55 PM

Answers

  • By default Windows 2003 servers (WHS is based on W2K3) don't display the background desktop wallpaper in a client TS session, ie. Remote Desktop. You can change that behavior, according to the help description, by running gpedit.msc on the WHS and changing the Local Computer Policy | Computer Configuration | Administrative Templates | Windows Components | Terminal Services | Enforce Removal of Remote Desktop Wallpaper group policy. Here is the guidance for that policy.

     

    Specifies whether desktop wallpaper is displayed to remote clients connecting via Terminal Services.

     

    You can use this setting to enforce the removal of wallpaper during a remote session. By default, Windows XP Professional displays wallpaper to remote clients connecting through Remote Desktop, depending on the client configuration (see the Experience tab in the Remote Desktop Connection options for more information). Servers running Windows Server 2003 do not display wallpaper by default to remote sessions.

     

    If the status is set to Enabled, wallpaper never appears to a Terminal Services client.

     

    If the status is set to Disabled, wallpaper might appear to a Terminal Services client, depending on the client configuration.

     

    If the status is set to Not Configured, the default behavior applies.

     

    You then need to configure the client to display desktop wallpaper when you open the Remote Desktop connectoid and select the Options | Experience tab. See above.

    Thursday, December 13, 2007 12:11 PM

All replies

  • By default Windows 2003 servers (WHS is based on W2K3) don't display the background desktop wallpaper in a client TS session, ie. Remote Desktop. You can change that behavior, according to the help description, by running gpedit.msc on the WHS and changing the Local Computer Policy | Computer Configuration | Administrative Templates | Windows Components | Terminal Services | Enforce Removal of Remote Desktop Wallpaper group policy. Here is the guidance for that policy.

     

    Specifies whether desktop wallpaper is displayed to remote clients connecting via Terminal Services.

     

    You can use this setting to enforce the removal of wallpaper during a remote session. By default, Windows XP Professional displays wallpaper to remote clients connecting through Remote Desktop, depending on the client configuration (see the Experience tab in the Remote Desktop Connection options for more information). Servers running Windows Server 2003 do not display wallpaper by default to remote sessions.

     

    If the status is set to Enabled, wallpaper never appears to a Terminal Services client.

     

    If the status is set to Disabled, wallpaper might appear to a Terminal Services client, depending on the client configuration.

     

    If the status is set to Not Configured, the default behavior applies.

     

    You then need to configure the client to display desktop wallpaper when you open the Remote Desktop connectoid and select the Options | Experience tab. See above.

    Thursday, December 13, 2007 12:11 PM
  • I guess he sees nothing at all. Probably something to do with graphics drivers on WHS (best use windows vga driver, you don't need advanced grpahics anyway on headless device) or broken RdpDD.dll or ...

     

    Please check your WHS eventlogs (on WHS: Start, run, type eventvwr.msc, hit enter) look for errors around the time you try to setup rdp connection.

     

    Also checkout this thread: http://forums.microsoft.com/WindowsHomeServer/ShowPost.aspx?PostID=2141025&SiteID=50

    Thursday, December 13, 2007 1:06 PM
    Moderator
  • Hello Al,

    I've tried the above connecting to WHS PP3 using Remote Desktop and running gpedit.msc but under 

    Local Computer Policy | Computer Configuration | Administrative Templates | Windows Components 

    the only subfolders I see are;

    Search
    Windows Media Player
    Windows Update

    I am logging in through the Administrator account - do I need to enable a different view or would the other options be visible if I logged in physically?

    Dave
    Monday, November 23, 2009 11:43 PM
  • Monday, January 18, 2010 10:37 AM
  • Hello Al,

    I've tried the above connecting to WHS PP3 using Remote Desktop and running gpedit.msc but under 

    Local Computer Policy | Computer Configuration | Administrative Templates | Windows Components 

    the only subfolders I see are;

    Search
    Windows Media Player
    Windows Update

    I am logging in through the Administrator account - do I need to enable a different view or would the other options be visible if I logged in physically?

    Dave

    Yeah i've the same problem / question. I also just see Search, Windows Media Player and Windows Update. But i can't connect physically. Is there another why?
    Tuesday, March 16, 2010 11:43 AM
  • What is your problem *exactly*?  It's best to raise a new question - especially if the previous one has already been answered.


    --
    Tuesday, March 16, 2010 12:06 PM