Ive had the OEM version of 2011 running since it first came out, then low and behold a major crash a major upset, To cut to the chase I was frustrated. Grabbed my disk and reinstalled. Then the oh crap moment I don't have the original cd sleeve anymore after all these year and a resident move. I cant find my serial anywhere. And since MS doesn't support it anymore and cant seem to locate anyway of actually buying another serial...
I know its time to move on but not just yet. Is there anyway to get the activation issue resolved thanks in advance.
Yes.. I have both a WHS v1 and a WHS2011 box with the same BIOS... But saying that I need to check and see if they are identical. I had to update the CPU microcode to accommodate Xeon CPU's. I am however running an E8400 in the problem box. an L5430 in another and an E8600 in the last one. Hmm no joy there. But the issue can't be the server as a WOL can wake the server from another PC. This confirms the WOL magic packet works ... its just that the schedule doesn't actually send the magic packet.
The key is here in the Task Scheduler logs but I dont know how to fix it The task isnt running so I am not sure what sleep state the server is being sent into. Although the logs say this after I logon to the the server and manually waking it. :-
The system has returned from a low power state.
Sleep Time: 2016-02-12T22:00:35.529385900Z - Lights out correctly sends it to sleep.
Wake Time: 2016-02-13T10:55:54.837135900Z - I manually generate this by using WOL
Wake Source: Device -Realtek PCIe GBE Family Controller
Task Scheduler did not launch task "\LoS-9ac136bd-9994-416c-b043-5da723eb24d4" as it missed its schedule.
I am going to keep looking.
Tx again for your patience.
I'm having exactly the same problem. To be honest I've only just retrieved the WHS2011 server out of storage as WHS Ver1 is still performing well. I can install the connector on theEl Capitan machine and it does report server errors. I can connect to the server using smb but cannot get access to the shared folders as it fails on username and password even for server admin. It looks like a permissions problem. Not much information about on connecting macs. This is the first post i've seen with exactly the same problem.