I'm upgrading all my lab computers (early 2008) from Snow leopard to El Capitan.
So far the upgrades has had the usual minor glitches, but for the most part everything works.
The major obsticle is getting the ARD wake from sleep function to work.
It worked fine with the old ARD 3.5 server but not with the new ARD 3.8 server.
Is there a change in the way the command is sent?
Mac Pro, OS X El Capitan (10.11), 4
Have you tried disabling and then re-enabling wake for network activity?
After re-setting it, I would suggest a reboot.
When you can't wake a computer, have you checked to see if the computer IP matches the IP in ARD?
Is the ARD server and the ARD client on the same network segment? (what are the local IP address of both computer) How are both computer sconces to the network. (wifi? ethernet? mix?)
What is your DHCP lease time set to?
What is acting as your sleep proxy server? Is your sleep proxy server set to stay awake at all times? How is it connect to the network? (wifi, ethernet, mix)
Thanks TeenTitan,
Yes I have tried most everything (listed below). The only thing I don't have is a proxy server. Is it required when using ARD 3.8 and all the clients are on the same subnet?
On interesting thing is that the new El Capitan server with ARD 3.8 can control and wake the iMacs still running Snow leopard, so I assume the server end is okay. Also the new server can can fully control the upgraded El Capitan computers (I've tried 4 so far) via OD, Server 5 Profile Manager, and ARD 3.8 but not wake them.
So far I have:
-reset Pram, Nvram multiple times,
-Inactivate and reactivate network access with the Gui in system preferences, with the Unix command in ARD, and also via Profile manager in Server 5.
-Disabled the firewall
-manually configured Static IP's (all are on the same subnet)
The thing these computers have in common are that they are all (mid 2007) vintage, and I'm wondering if 'Wake for network access" does not work on them in El Capitan. I have some newer ones (2010) in a lab that is being used right now, so I think as soon as this summer session ends, I will upgrade one to see how it behaves.
However, if a proxy server is required with El Capitan, then I guess that would be it, but it seems odd Apple would require a home peripheral product and not have a server solution.
Onward through the fog.
10.7+ prefers sleep porxy. If you haven't set up a sleep proxy. Then your basically relying on WOMP. (wake on magic packet) If you reset NVRAM then the OS may think WOMP is enabled while it's actually disabled. The easiest way to fix that mismatch would be to turn "wake for network access" off for ethernet, reboot, turn it on, and reboot again. And then verify it still shows as checked.
After re-enabling wake for network access, you can use "pmset -g disk" to see the status of WOMP in NVRAM. Is WOMP set to 0 or 1? (1 is on)
If WOMP is still 0, you could try turning it on with:
sudo peseta -a WOMP 1
(and then reboot)
If your still having the issue, have you tried disabling hibernation?
sudo peseta -a hibernate mode 0
(and then reboot)
If your still having the issue on the client. Have you tried
sudo pmset -a darkwakes 1(and then reboot)
If your still having the issue on the client. Have you tried
sudo defaults write /Library/Preferences/SystemConfiguration/com.apple.Boot.plist 'Kernel Flags' 'darkwake=8'
(and then reboot) Please note this is an advance setting; use at your own risk.
Have you considered turning your ARD server into a bonjour sleep proxy server?
Thanks again TeenTitan,
The PMset command was just the tool I was looking for. It has given me a lot of info, but the clients still refuse to wake for network acess.
client settings show
AC Power:
Sleep On Power Button 0
ttyskeepawake 1
hibernatemode 0
hibernatefile /var/vm/sleepimage
displaysleep 5
womp 1
networkoversleep 0
sleep 10
halfdim 1
autorestart 0
disksleep 180
Note: These iMacs are too old for the Darkwake option.
So it looks like the clients are okay, but they won't wake.
I tried to set up the server as a sleep proxy server, but El Capitan refuses edits on the com.apple.mdnsresponder.plist file even with sudo.
This wake issue looks like its been a problem since lion. Not sure why Apple doesn't show how to set up a mac as a sleep proxy server.
I got it working.
Had to turn off SIP (Boot into recovery mode and type 'csrutil disable' in a terminal) and then I could get bonjour to act as sleep proxy server by adding the lines to com.apple.mDNSResponder.plist as described at http://stuartcheshire.org/sleepproxy/
(Cmon Apple, this should be a checkbox in the ARD 3.8)
It still didn't work so I reset all ARD settings on the cleats with:
sudo /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/k ickstart -uninstall -settings
Then I reconfigure. (I used the ssh and kickstart for three computers and everything worked.
Oddly enough the one that I looked into directly (not remotely) and reconfigured using the GUI failed. On the server I found the log of the server said
6/14/16 3:05:07.937 PM ARDAgent[90742]: Encryption key not found for client.
So inseams like Wake was looking for an encryption key, so I ssh to it and get a ECDSA key and everything worked.
Thanks TeenTitan for pointing me in the right direction
Wow, Lots of Typos,
1)Had to turn off SIP (Boot into recovery mode and type csrutil disable in a terminal) and then I could get bonjour to act as sleep proxy server by adding the lines to com.apple.mDNSResponder.plist as described http://stuartcheshire.org/sleepproxy/
(Cmon Apple, this should be a checkbox in the ARD 3.8)
2)then I reset all ARD settings with sudo /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/k ickstart -uninstall -settings
Then reconfigure. I used the ssh and the command kickstart for three computers that, and everything worked worked.
Oddly enough, one computer that I logged into directly (not remotely) and reconfigured using the GUI failed. On the server I found the log of the server said
6/14/16 3:05:07.937 PM ARDAgent[90742]: Encryption key not found for client.
3)So it seems like Wake was looking for an encryption key, So I ssh-d to it and got a ECDSA key and everything worked.
Spoke too soon.
Today, all 4 computers are back to their old tricks and will not respond to WOMP.
They do see the sleep proxy server, and the log files on the server show the MDSResponder trying to wake them with the Mac address, but nothing happens.
Did a new clean install on one computer, same problem.
If I SSH into any of them and :
sudo /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/k ickstart -uninstall -settings
They will work for a while, but revert back.
They don't respond to the WakeOnLan App while all the computers running Snow Leopard do wake.
However, they will wake just fine with a tap on the keyboard or click of the mouse.
Only solution now is to not allow them to go to sleep.
I have a feeling it's related to El Capitan's implementation of Darkwake not working with older computers that don't support Power Nap (mine are mid 2007).
If anyone has 'Wake for network access" working on a computer that doesn't show the 'Enable Power Nap' option in System Preferences/Energy Saver I would sure like to know.
After spending two weeks trouble shooting, I've com to the conclusion that this is an issue between with certain older iMac models (Mine are MA876LL/A -Mid 2007) and El Capitan.
I submitted bug report 26928188.
To test further:
I installed on a newer Mid 2010 model and it worked.
Then I went back to one of the Mid 2007's and did clean installs of Lion and Yosemite. They both worked, but a clean install of El Capitan failed.
At this point I'll update all to Yosemite and wait to see what Apple says.
Tech support from Apple found the issue in System/Library/Extensions/IOPCIFamily.kext
Security Update 2016-002 solved the problem.
Tech support from Apple found the issue in System/Library/Extensions/IOPCIFamily.kext
Security Update 2016-002 solved the problem.
ARD 3.8 wake from sleep not working on El Capitan