Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
WHS Console no longer working, RDP connection was deleted after NIC driver re-install RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello Homers,

    I have a problem that is partially solved but incorrectly....
    After problems with the Intel NIC in my WHS I needed to uninstall and reinstall the drivers. After this I was no longer able to connect to the WHS console from the clients nor using plain RDP to the WHS.

    I checked the RDP configuration on the server and noticed that the RDP connection under "Terminal Services Configurations" was disappeared.  So I created a new deafult "connector".

    After this action the WHS console from the clients was working but popped up a full desktop of the WHS instead of just the console. So I updated the created RDP Connection and added "C:\Program Files\Windows Home Server\HomeServerConsole.exe" being the program that should start up instead of a full desktop.

    This now looks almost ok, the console now starts and opens in a second window within the first window, so not fully seamless, and after closing it the console reports now that the RDP connection was lost.

    I can only RDP now to the full desktop on the WHS when I use "mstsc /v:WHS /admin" which I understand ofcourse after having changed the RDP configuration to run the HomeServerConsole instead of a full desktop.

    How can I get the original configuration of the RDP connection back?
    What were the orignal settings? Can somebody check??

    Probably the "Environment" tab of the connector settings I guess...

    Guido

      

    Saturday, January 24, 2009 9:49 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Olaf,

    Yep, that's correct, and my qustion was what the original configuration was.

    I got an answer from another MSVP that is was: C:\Program Files\Windows Home Server\HomeServerConsole.exe -b

    The -b option took care of opening of the WHS console in seamless mode, so no extra window.
    It works perfect now!

    Thanks,

    Guido 

    Sunday, January 25, 2009 3:52 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Guido,

    on the environment tab in the properties of RDP-Tcp connection the radio button Run initial program specified by user profile ... is selected. Which would make sense, since the Connector software creates a RDP session to the console. So I assume it is adding the necessary parameters to launch the console application, since a "normal" RDP session is still possible.

    Best greetings from Germany
    Olaf

    Saturday, January 24, 2009 11:12 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Olaf,

    Yep, that's correct, and my qustion was what the original configuration was.

    I got an answer from another MSVP that is was: C:\Program Files\Windows Home Server\HomeServerConsole.exe -b

    The -b option took care of opening of the WHS console in seamless mode, so no extra window.
    It works perfect now!

    Thanks,

    Guido 

    Sunday, January 25, 2009 3:52 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Guido,

    slight correction: You mean WHSConsoleClient.exe, I assume?
    (But this is what also should be done by the connector itself, if using the context menu of the icon, so it is still a little bit strange, what happend on your Client PC that it doesn't.)

    Best greetings from Germany
    Olaf

     

    Sunday, January 25, 2009 5:15 PM
    Moderator