none
Loading Programs on WHS RRS feed

  • Question

  • I would like to load a couple of programs on my WHS box.  How do I do that other and attach the monitor, keyboard, and mouse?  Also, then how do I manage the program?  The program is a home automation program that needs a machine running 24/7...

    Thanks,

    Stan
    Monday, January 5, 2009 4:19 AM

Answers

  • Embedded Automation has a home automation add-in (mControl) specifically for Windows Home Server. That would probably be the recommended course of action. I don't think Smarthome has an equivalent for HouseLinc.

    If you want to try to install HouseLinc anyway, you can either connect monitor, keyboard, and mouse to your server and log in directly, or connect by Remote Desktop:
    • From any PC on your network: Start/Run/mstsc.exe and press enter.
    • Enter the name of your server.
    • Enter the user name administrator, and the password for your server's console.
    • Somewhere in here you'll get a security warning or two. Click through them.
    • When your remote desktop session starts, you'll see a warning page displayed. Take this to heart; it's possible to do some serious damage. Then close the page.
    You're now logged in much as though you were using a physical console.

    If HouseLinc is controlled through it's own web site, you'll need to be extremely careful. Windows Home Server uses several web sites for various purposes, and recovering if the HouseLinc installation messes them up could require a server reinstallation.

    I'm not on the WHS team, I just post a lot. :)
    Monday, January 5, 2009 5:13 PM
    Moderator

All replies

  • MSSMacro said:

    I would like to load a couple of programs on my WHS box.  How do I do that other and attach the monitor, keyboard, and mouse?  Also, then how do I manage the program?  The program is a home automation program that needs a machine running 24/7...

    Thanks,

    Stan


    Installing anything on WHS other than an add-in (which is done through the Console) is unsupported.  The reason it's unsupported is it requires you to logon to the server desktop and if you're not really careful, you could accidentally change some setting that would normally be ok to change on a computer, but could be a problem on WHS (due to the way it handles file storage).  In order to logon to the server deskop, you need to use either A) a keyboard, mouse and monitor connected to the server hardware or B) use Remote Desktop Connection and logon remotely.
    Monday, January 5, 2009 4:25 AM
    Moderator
  • Let's start with the hardware part of your question:
    Is this a self-built/local-built WHS, or an HP MediaSmart Server?
    If the latter, you can't connect KB/mouse/monitor to it, as, well, it lacks a display output.

    As for installing software on it:
    You can either connect things & log on locally, or connect to the server via remote desktop, and install the program.

    Words of caution:
    Local logon, as well as RDP connections, to a WHS, as well as installing software, is:
    1- possibly (depending on what, exactly, you're doing) against the EULA;
    2- an unsupported use of WHS (read:  MS isn't responsible if you or your automation program breaks things);
    3- creates the possiblity of 'breaking' WHS.  There are a lot of SBS2k3 tools and utilities that are accessible via the desktop (that aren't available via the Console) that, when used incorrectly (or, for some, used at all) can create major issues for WHS (usually requiring a Server Reinstallation to fix.)  Just watch what you do in there; and, if you don't know what something does, don't use it.  ;)

    HTH,
    Chris
    [If this post helps to resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.]
    Monday, January 5, 2009 4:31 AM
  • Okay - I get the risks...  How would I set up a remote desktop session?  I built this WHS on a HP 864n machine and one of the intended uses is to run this HouseLinc2 software.  Since I haven't really done anything with the server other than get it up and running, now is the time to try something out...

    So other than the EULA potential problems, I assume that unless I get in there and start changing settings, I should be okay or at least safer...
    Monday, January 5, 2009 4:42 PM
  • You'll be alright, just don't change any firewall or security settings.  Use remote desktop from a windows machine and type in your servers ip address or name.  this will allow access as long as you have the administrator password, which just so happens to be the server console password.  
    athlon 3400, 2gb ram, 9 drives totaling about 3.5 tbs.
    Monday, January 5, 2009 4:58 PM
  • Embedded Automation has a home automation add-in (mControl) specifically for Windows Home Server. That would probably be the recommended course of action. I don't think Smarthome has an equivalent for HouseLinc.

    If you want to try to install HouseLinc anyway, you can either connect monitor, keyboard, and mouse to your server and log in directly, or connect by Remote Desktop:
    • From any PC on your network: Start/Run/mstsc.exe and press enter.
    • Enter the name of your server.
    • Enter the user name administrator, and the password for your server's console.
    • Somewhere in here you'll get a security warning or two. Click through them.
    • When your remote desktop session starts, you'll see a warning page displayed. Take this to heart; it's possible to do some serious damage. Then close the page.
    You're now logged in much as though you were using a physical console.

    If HouseLinc is controlled through it's own web site, you'll need to be extremely careful. Windows Home Server uses several web sites for various purposes, and recovering if the HouseLinc installation messes them up could require a server reinstallation.

    I'm not on the WHS team, I just post a lot. :)
    Monday, January 5, 2009 5:13 PM
    Moderator
  • Thanks - that did it...  It is running with no issues (at least not now)...
    Tuesday, January 6, 2009 2:36 AM