Beginning in May, a special Today at Apple series titled “Made for Business” will offer small business owners and entrepreneurs free opportunities to learn how Apple products and services can support their growth and success. Learn more >
Beginning in May, a special Today at Apple series titled “Made for Business” will offer small business owners and entrepreneurs free opportunities to learn how Apple products and services can support their growth and success. Learn more >
Looks like no one’s replied in a while. To start the conversation again, simply
ask a new question.
I currently have an energy saver schedule to shut machines down at night and wake them in the morning
Is it kosher for me to create another group with the same machines, but with an energy saver schedule to power on the machines once a week (to do maintenance)
Note that you may only have one pair of repeating events scheduled - a "power on" event and a "power off" event.
Since
pmset settings are global you can't have per-user settings.
The best I think you can do it set the systems to sleep and have them woken remotely (if you have a remote server that can schedule the maintenance tasks).
Note that you may only have one pair of repeating events scheduled - a "power on" event and a "power off" event.
Since
pmset settings are global you can't have per-user settings.
The best I think you can do it set the systems to sleep and have them woken remotely (if you have a remote server that can schedule the maintenance tasks).
Please provide a few details around the "Doesn't work" and a description of what you believe "true wake-on-LAN" might be; these aren't statements that I can address. We could use a few more details around the boxes involved, around what was tried, what particular run-state that the box was in (sleeping, solidly powered down, etc), and then what then did or (most likely) didn't happen here, and around what you expected to happen.
Here's some [Wake On LAN|http://www.macosxhints.com/article.php?story=20020220095929695] and [Apple TA21254|http://support.apple.com/kb/TA21254] and [Wake on LAN for Mac OS X|https://wiki.brandeis.edu/twiki/bin/view/Bio/MacOSXWakeOnLAN] and via [iPhone|http://bendodson.com/blog/2008/09/08/control-mac-mini-from-iphone-with- waking-sleeping-audio-video>.
And yes, the "Wake for Administrator Access" knob is lurking in the Power Saver settings on Leopard.
Xserve is the only box around that (once configured) can inherently do a full cold-start remote power up; Xserve has a LOM module that's always on when the box is plugged in, and the LOM is something which is not present on most other boxes. (It can be easy to get the LOM capabilities mixed up with the Wake On LAN, too.) If you need the remote power-cycle and don't have an Xserve, there are network-capable power switches and less-interruptible power supply (LIPS) devices that offer this (remote management) capability.
HP has called the server version of the management board the iLO or the iLO2, usually. Older management boards for some of the lines were known as the RMC or RCM, depending on the generation.
The box most analogous to what an enterprise might use is the Xserve box, and that has entirely analogous power-management capabilities using what Apple calls the LOM. Or you need to install a network-capable switch or such.
I haven't looked at the HP desktop boxes in a while, but this Wake On LAN (WOL) stuff was usually ACPI state S5 stuff in the HP BIOS. Mac does do an S4-level save but then tends to sit in S3 until the power drops out. (In either case, some chunk of the components of the box have to remain powered up; the NIC and the firmware certainly need to be active, regardless of whether WoL starts from S3, S4 or S5.)
I should go toss the "magic packet" at a Mac box in what passes for S5 state and see if the box responds. I haven't tried that sequence. Based on your comments, I might assume you have tossed that packet, and the box doesn't respond.
AFAIK, Apple isn't catering to the enterprise. Products better targeted for that market might be interesting in some environments, but I don't see Apple having made a big push in that direction as yet. If I really needed S5 prior to replacing my customers' fleets of gear with new and entirely hypothetical S5-capable gear, I'd probably install one of the network-capable power strips; those are around US$150, give or take. Or a network-capable Less Interruptible Power Supply (LIPS) widget. Locally, the S3/S4/S5 WOL distinction hasn't been a deal-breaker.
