We faced this issue too.
Our officebuilding is going through a big renovation and because of that many networkdevices like computer, printer and so on are moving round and round and from port to port.
Because of those hardwaremovements the Cisco ISE had to be ready for productive use so that we won´t have to configure the V-LAN on every port for every movement per hand.
After some hundred movements the numbers of reports about PCs starting softwareupdates and installations on monday morning after the user bootet them and not on the weekend, rose up.
The following is what we figured out:
The ISE + WOL-config was right, like yours.
Our softwaremanagement- and installation tool sends magic packets that don´t get to most of the PCs that were moved.
We tested and found out, if PC thath was moved to another port had another V-LAN than the Port had set he would boot and get his IP when started per hand, when started per WOL nothing will happen.
Sp long story short end: The thing was that the installation-software only sent the magic packets to the MAC-Adress. A Subnet-Mask had to be added ( f.e. 184.108.40.206 or 255.255.255.255). Somehow the reports then dropped but problem wasn´t 100% finished.
After some tests we also came to the conclusion that the UDP-Port which the software uses had to be put configured in the V-LAN where the software-server is resides because the software uses a non-standard-port for WOL.
The last change was adding the UDP-Port to the V-LAN of the software-server and couldn´t be testet yet.
So one can say, it isnßt the ISEs fault but the ISE is involved.
... View more