Answered by:
WOL!

Question
-
The per-PC backup configuration should have an option to wake up the PC via WOL packet.
Yes, it would not work if the target PC did not support WOL. But then again, not all target PC's have Standby. Case in point, in my place I have several PC' that are not ACPI but do have WOL...
Yes, it may not work at all if the home user is running through a router that dumps these packets, which unfortunately some of older, cheap routers do.But for many users, this would work, and save energy vs. standby modes; especially for PC's that don't have standby.
I understand keeping things simple and all, but given the potential energy savings, it's worth supporting such a useful feature even it can't be used all the time.
- Rhino
Wednesday, January 23, 2008 9:26 AM
Answers
-
Microsoft chose not to support Wake On LAN because it's too unreliable. It requires the right hardware, the right software, and the right configuration to work. Only the software is in Microsoft's control, and it's not easy for a non-technical user to correctly configure WOL in his PC's BIOS.
It would be possible, however, for someone with a bit of motivation to "roll your own" solution, if your client PCs support it. For example, you could create a scheduled job on the server that would sent the appropriate magic packets a few minutes before the backup period begins, then let PCs shut down per their power saving configurations.Wednesday, January 23, 2008 4:33 PMModerator
All replies
-
Microsoft chose not to support Wake On LAN because it's too unreliable. It requires the right hardware, the right software, and the right configuration to work. Only the software is in Microsoft's control, and it's not easy for a non-technical user to correctly configure WOL in his PC's BIOS.
It would be possible, however, for someone with a bit of motivation to "roll your own" solution, if your client PCs support it. For example, you could create a scheduled job on the server that would sent the appropriate magic packets a few minutes before the backup period begins, then let PCs shut down per their power saving configurations.Wednesday, January 23, 2008 4:33 PMModerator -
Yep, I'm aware with what's involved. That's why I said optional. ;-)
As a system builder who will be marketing his own OEM WHS product, I will be implementing this myself among several other add-ins. It would just be nice if we didn't have to. But it's a trivial amount of work; I already have the code in a standalone client to wake up other PC's via WOL; moving it into an add-in is easy.
I understand the reason MS didn't put it in wasn't because it is hard (it's not). It's all about usability. I get that. But as an option that can be safely ignored if you don't know what it is, it would be nice to be there for those who do. As such including it wouldn't affect the overall product negatively if exposed properly. It's called an Advanced button and pop-up dialog. If you aren't "Advanced", you don't belong in there. This metaphor is used throughout Windows.
FYI, most PC's these days that have WOL capability typically have it enabled by default in BIOS. My product line currently leverages 4 motherboards from 2 different manufacturers, and WOL exists and is on by default in all of them. But on the other hand, I know Dell home based PC's for example have it off by default, and turning it on is not easy. But hey...buy a Dell, get what you pay for. ;-P
As far as network configuration, the three cheap home-based routers I have used over the years all pass the magic packet frame across the LAN subnet with no issues, by default (ie no config needed). Since WHS is really designed for single-subnet use on it's LAN, this isn't a problem, as if your local PC's span subnets you're going to have other WHS issues anyway. The vast majority of routers will allow these packets to pass as long as they were generated within the subnet. They would techically be broken not to. If you get into larger home network using older routers, you again run into problems. But again this would be a minority of users.But by far the biggest issue is getting WOL to work remotely, as it would require advanced undertaking and confguration of the router, and depending upon the router, may not even be possible (likely for dirt-cheap home-market routers). This is the other sub-feature that will be in the add-in: you will be able to remotely turn on computers on your home network indireclty through WHS by having it send the WOL packet on your behalf.
Today, WHS can't do this. If my computer at home is dead-cold and I forgot to copy something off it before I left for work, I'm hosed. With this add-in, you'll be able to turn your computer on at home so you can get that data. I believe that feature is powerful enough that many users (but certainly not all) would go through the hoops necessary to do the configuration steps requred to enable it. But, with stock WHS, they don't have that option.
Ryan
Thursday, January 24, 2008 7:08 PM -
Ryan, go over to the Developers subforum and search for "Wake On LAN". There's a third party add-in that will let you wake up a PC on your network. Microsoft isn't likely to include it any time soon, because there is still too much hardware out there that doesn't support WOL, or supports it only partially (even some modern motherboards only support "Wake on any network traffic" rather than "Wake on magic packet"), so I don't expect to see it in an enhancement to the current version of WHS. Maybe a future version...Thursday, January 24, 2008 8:53 PMModerator
-
Yep already saw that thread and even replied to it. ;-) It's not suprising others have thought about it as well.
Yeah I doubt it'll show up in future WHS versions; but it doesn't hurt to ask. ;-P
Ryan
Friday, January 25, 2008 2:40 AM -
Ryan,
this is a GREAT idea and should have really been implemented from the start - the points made about the hardware and software config are valid, but as you rightly say its pretty trivial to configure and would be of enormous benefit to those users who could implement it.
As a matter of fact the whole WHS box could suspend to RAM only to wake itself at an appointed time, wake the client PCs with WOL packets, undertake the backups and go back to sleep again - If (like me) the WHS is run primarily as a backup device the WHS box itself needn't be up 24/7 - a few hours during the night would solve it,
Lets hope it gets implemented.
Tim.
Thursday, March 13, 2008 12:54 PM