@TheCPUWizard said:
@mallard said:
@TheCPUWizard said:I have a couple of headless media servers.. Home Server Console (instaled on a client) should be able to talk to the box event without general RDP enabled.
It might work if the general remote desktop service isn't generally enabled, but it's not going to work if the RDP port is blocked by the the firewall!
The versions of Windows Home Server that I evaluated did NOT use RDP or the normal RDP ports for the Home Server Console application...this may have changed, but I have not heard of it, nor needed to research it. If that is still true, then it is completely possible to have RDP disabled AND blocked - yet still use the Console Application...
The version of WHS I messed about with on one of my servers before deciding it was rubbish and switching to full WS2003 most certainly did and the documentation I can find seems to support me on this one.
e.g. "The configuration interface, called the Home Server Console, is delivered as a Remote Desktop Protocol application to remote PCs - while the application runs on the server itself, the UI is rendered on the remote system." (Wikipedia)
"I have recently altered the port that my home server listens on for rdp to something other than the default 3389. Obviously, the home server console connects using this port. I need to change the port that the console connects with and cannot find it anywhere." http://social.microsoft.com/Forums/en/whssoftware/thread/b3348b4d-3d57-4212-bc84-a1b5a9ddd340
"These tell the browser based RDP session to use HomeServerConsole.exe as the "shell", with a command line parameter to tell it not to show the Minimize and Exit buttons." http://www.windows-now.com/blogs/dougknox/remote-desktop-access-windows-home-server.aspx