Limit to Server on time and KVM RRS feed

  • General discussion

  • There seems to be an assumption that the server will be on continously - I have no intention of leaving the network (four computers) on after bedtime or when leaving the house. As a result "headless" operation is not a viable option - a solution may be use of KVM cable.
    Friday, April 20, 2007 10:27 PM

All replies

  • What does not leaving things powered on have to do with headless operation?  Why do you need to access the server at all if there are no powered machines attached to it?
    Saturday, April 21, 2007 12:42 AM
  • Two things -


    First you're missing the point of WHS - one of things it does is backup the four PCs on your network when you're not using them - when is that most likely to be?  When you're in bed.  Sure, it's environmentally friendly to shut your PC down when you're not using it, WHS can wake it from standby, back it up, and put it back to sleep.  Another use for WHS is to allow secure remote access to, not only the files on the HomeServer itself, but also on the four network PCs - that's access when you're not at home.


    Second - you can shutdown a headless WHS - you do it from the WHS console that the Connector CD installs on your PCs



    Saturday, April 21, 2007 2:52 AM
  • Backups here are scheduled in the time frame 3:00 - 6:00 PM and perform when the PCs are in use.  Shutting down a "Headless" server is not the problem - yes it can be shut down via the Server Connector, however, at the present, it cannot be booted from the Connector.


    The problem is in validation of a successful boot after a  shut down server without access to a monitor.  One assumption of a successful boot would be ability of a PC to connect, however on several occassions, at least here, if one PC is booted before the server, the server will not boot until the PC is shut down or two or more attempsts are made to boot fom the server.

    Saturday, April 21, 2007 11:58 PM
  • I was, at first, overt to cutting the KVM cable. Though I rarely use it (it is still connected just in case of bios tweaks or general tuning pre boot), I use Remote Desktop to get into the server desktop. Really not been an issue for me.

    Backups? Well, I too sometimes turn my PC's off at night (too noisy). Plus, I really don't need WHS to back up the OS of my two connected pc's every day. No real need. Nothing changes unless you install a new program or something. But that's just me.

    Not sure why your WHS won't boot if another pc is left on. My WHS does not seem affected. Are your pc's connected to the net through the WHS instead of a router? Not sure if that could be the issue.

    Just a few thoughts...
    Monday, April 23, 2007 3:15 AM
  • Assuming your hardware supports it, you can use WOL to start the server - validation of a successful boot via a directly attached console should not be required on a routine basis - if you have hardware problems or are doing some sort of an upgrade. then maybe -  I work with servers, that are several miles away, on a daily basis, and think nothing of performing a restart remotely, knowing full well that any failure is going to mean that I have to get up and drive over to the location.


    More than one of the sites run unattended, if there's a power failure, which happens frequently and the genset fails the UPS will shut the servers down before shutting itself off, and when power is restored the system comes back up - I don't have to dispatch an administrator to deal with it


    We're talking mature technology, that, at least in my experience, works.


    As for WHS not booting if a PC is on - I haven't  experienced that - and I'm running four laptops and two desktops with my WHS - and being a fiddler by nature, I've upgraded the hardware a number of times, without shutting down any of the attached systems.  Also since the connector cannot connect until the server is up and running - I am a bit of a disbeliever that that is what's causing it.

    Monday, April 23, 2007 3:44 PM
  •  Judge - I agree concerning backups.  The problem of the server not completing boot if a particluar PC is booted first has not re-occurred and I negelected to specify Beta 2 was in use.


    I considered use of a KVM cable to preclude a separate monitor and keyboard for the server for use when booting the server from shut down status at which time a password would be required. Today (Monday) had  a new expereince  with the same PC which I have entered a new post.

    Monday, April 23, 2007 6:09 PM
  • Still not so sure why you need to see WHS desktop when starting the server from a shut down. I mean, my WHS can be turned off....I reach over and hit the power button and in 90 seconds it's booted all on its own. No password or screen needed.

    Now if I need to get into the WHS desktop, after it's powered on I use Remote Desktop to log in with the password.  Hmm, maybe I'm not understanding what you mean or need. Sorry....

    Still, WHS refusing to boot if another pc on the network is turned on first just defies me. Not sure how that is/can happen.

    For me and for it's intended use, WHS is the nicest thing since sliced bread. LOL. I had to tinker and figure some things out, one complete reinstall,  but it's helped bring backups and a central file storage to my 3 pc household.   Again, thanks guys.

    Anyone have any ideas for Ajroco?

    Monday, April 23, 2007 11:42 PM
  •  AJROCO wrote:
    There seems to be an assumption that the server will be on continously - I have no intention of leaving the network (four computers) on after bedtime or when leaving the house. As a result "headless" operation is not a viable option - a solution may be use of KVM cable.


    I have 18 computers here at home currently running, I downsized from almost 30 recently, and they ALL run 24/7/365. When I go on vacation, they run, when I am sleeping, they run. Computers are not hurt by running al lthe time. In fact I have found that they are 'bothered' by the constant shutdown and restarts alot of people do. My pcs are running a Distributed Computing Project from www.malariacontrol.net that is looking for a cure for Malaria. It self throttles up and down based on whatever you personally are doing with your pc. It will use 100% of the cpu while you are snoozing, but less, all based on settings, whne you are actually using the pc. Anyway I am pleased with the backups and the only issue I have is that the WHS server does something that requires me to log in after some, as yet undetermined, amount of time and the backups stop midstream until I log back in. I use RAdmin, which is like Remote Desktop, to control all of the pcs from one location. This works fine, and I can even log into the WHS server with this when it goes to the ctrl-alt-del screen. I have the screen saver truned off and the power settings set to always on. Any ideas?

    Tuesday, April 24, 2007 1:56 PM