locked
WHS console add-in which can run remote applications on the connected workstation RRS feed

  • Question

  • Hello,
     
    we currently have an application running on workstations. Now we would like to build an add-in for the WHS console for administrating our application. The application itself has a number of configuration screens which store the configuration locally.

    To enable the user to configure each workstation application, it would be nice, to let the user select the workstation (using WHS console) and as sool as 'Configure' is pressed the application is started on the workstation and displayed on the computer which executes WHS console.

    As far as I can see, the WHS console is an application running on the Server which is just displayed on the computer from which WHS console was started (using RDP). Can this be done on workstations as well? That means: can RDP be used to run an application remotely and not the whole desktop?? Is this possible on Windows XP or is that feature limited to Windows Server Versions??

    Thanks,
      Gerhard.
    Monday, September 15, 2008 7:27 AM

Answers

  • You would be (much) better off adding the ability to push configuration settings down from the server to the clients, instead of trying to run a remote desktop session from the server to the client. Not all Microsoft operating systems support incoming Remote Desktop connections (only XP Professional and Media Center, and Vista Business, Enterprise, and Ultimate).
    I'm not on the WHS team, I just post a lot. :)
    Monday, September 15, 2008 11:30 AM
    Moderator
  • If your interested in how the Windows Home Server Console does its thing using RDP this site should offer a good starting point. If you just want to lunch a specific program using RDP with the full desktop, in the remote desktop connection client click on Options then click on Programs and check "Start the following program on connection". Then specify the program and the path to that program on the remote desktop along with any argument to pass into it when it starts. When you connect only that program will appear in the RDP session, in fact this is essentially how WHS console sets up it's own RDP session passing in the location of the HomeServerConsole.exe on the server along with the -b argument to remove its window chrome. Of course, there is some other work done with WHS connector on the client side to allow things to execute locally on the client such help files in the help viewer and URLs in the browser on the client but you get the idea.

    With this said however, as Ken mentioned this will only work if the remote computer is able to receive desktop connections. Going further, it sounds like this violates the WHS Development guidelines for add-ins as well, specifically "The console is not a general-purpose desktop" part of the guidelines. The reason that the development guidelines strongly suggest against this is that the WHS console is really just meant for one person to use, the WHS Administrator. As such there are a few caveats that go along with is such as when a new instance of the console is opened any other console instances are instantly terminated. This obviously would not be a good thing if you plan on having multiple people configure the workstations simultaneously. Following the WHS development guidelines you would probably want to build some type of service that is then hosted on the server using the WHS Console to configure the service running on the server. Then you would have your client application on the workstations retrieve their configurations from the server either though a polling mechanism or as Ken mentioned a push mechanism.

    Hope this helps.
    Tuesday, September 16, 2008 5:46 AM

All replies

  • You would be (much) better off adding the ability to push configuration settings down from the server to the clients, instead of trying to run a remote desktop session from the server to the client. Not all Microsoft operating systems support incoming Remote Desktop connections (only XP Professional and Media Center, and Vista Business, Enterprise, and Ultimate).
    I'm not on the WHS team, I just post a lot. :)
    Monday, September 15, 2008 11:30 AM
    Moderator
  • If your interested in how the Windows Home Server Console does its thing using RDP this site should offer a good starting point. If you just want to lunch a specific program using RDP with the full desktop, in the remote desktop connection client click on Options then click on Programs and check "Start the following program on connection". Then specify the program and the path to that program on the remote desktop along with any argument to pass into it when it starts. When you connect only that program will appear in the RDP session, in fact this is essentially how WHS console sets up it's own RDP session passing in the location of the HomeServerConsole.exe on the server along with the -b argument to remove its window chrome. Of course, there is some other work done with WHS connector on the client side to allow things to execute locally on the client such help files in the help viewer and URLs in the browser on the client but you get the idea.

    With this said however, as Ken mentioned this will only work if the remote computer is able to receive desktop connections. Going further, it sounds like this violates the WHS Development guidelines for add-ins as well, specifically "The console is not a general-purpose desktop" part of the guidelines. The reason that the development guidelines strongly suggest against this is that the WHS console is really just meant for one person to use, the WHS Administrator. As such there are a few caveats that go along with is such as when a new instance of the console is opened any other console instances are instantly terminated. This obviously would not be a good thing if you plan on having multiple people configure the workstations simultaneously. Following the WHS development guidelines you would probably want to build some type of service that is then hosted on the server using the WHS Console to configure the service running on the server. Then you would have your client application on the workstations retrieve their configurations from the server either though a polling mechanism or as Ken mentioned a push mechanism.

    Hope this helps.
    Tuesday, September 16, 2008 5:46 AM