Ghost Solution Suite

The scheduler in Ghost (version 11.5.1.2266 currently in use) indicates that a WOL & inventory refresh task I have scheduled for a number of our machines ran (indicates the day and time it ran and the date and time it will next run), but I cannot find a record of it in the Ghost task log. These target machines did not WOL as they are supposed to. I intend to watch them tomorrow morning to see if it was a fluke.

Any ideas why that might have happened?

Thanks,

Tony

Are the target machines in the same subnet as the Ghost server? The WOL packet is not routable so you either need the machines to be in the same subnet or you need a machine in the subnet to act as a relay if you want to send to other subnets.

Yes, the machines are in the same subnet. I should have mentioned that this is an ongoing task that has been working until this one hiccup. My apologies.

Are these machines all the same make/model or are they different?  If all the same, are they running the same BIOS version, and is WOL enabled?

I do recall faultfinding some old machines where WOL was not working although I could pick up the WOL "pulse" generated by the NIC. It appeared that the pulse was not switching the PSU on. This proved to be a hardware issue. For WOL to work, the NIC chipset needs to have power available to it all the time, and the standard AT PSU should be providing a 5V low current supply even when the machine is powered down. This ensures that the NIC chipset can respond to a WOL packet, and generate the switch on pulse that turns on the main part of the PSU.

So do not exclude the possibility that there is a hardware issue, either with the ports that are servicing the failing machines, or with the machines themselves.  If the machines have been switched off at the wall then they will not respond to a WOL packet so make sure the cleaner is not messing with the sockets when plugging in the vacuum cleaner (yes - old joke but it does happen).

Sorry I haven't responded. It's been very busy here this week.

Will look into if the machines simply didn't receive power for WOL to work. As this is an ongoing task that has worked since I set it up some time ago (also since the issue, the task has been working successfully), I'm thinking it must be a power issue.

Thanks