Moopere
commented
3 years ago It can be a challenge to shutdown machines that are not in a domain thats for sure.
I don't believe that shutdown problems are NIC specific, assuming that the NIC works properly. They key is probably this from your post:
"Run secpol.msc. Go to Local Policies > User Rights Assignment > Force shutdown from a remote system and add the same admin user you used in Shutdown for the properties for that box."
The system being shutdown has to actually allow remote shutdown (thus the GPO setting) and of course one needs to actually have permission to complete the shutdown, thus using the correct 'admin' user on the machine to be shutdown.
The shutdown command:
/s = shutdown (as opposed to /r for reboot ... or other options) /m = specify the machine. In this case its not being specified, and there is a trailing \ ... I suspect both are ignored /t 3 = force a shutdown after 3 seconds /f = force shutdown (ie, don't wait for apps to respond) - this is redundant as its implied when you use /t 3 (or /t with any number)
I tried many of the solutions I found online and none worked, e.g. add WMI to Firewall, use admin login, set to Legacy, etc. I did find something that did work, and it's worked with a number of different mfr NICs that would never shutdown at all on W10 boxes. I already had WMI allowed through Firewall so I left it for the first couple. Didn't seem to change things one way or another. YMMV. 1 - Run secpol.msc. Go to Local Policies > User Rights Assignment > Force shutdown from a remote system and add the same admin user you used in Shutdown for the properties for that box. 2 - Under Shutdown Properties in WOL, change dropdown to Custom. 3 - Add this command line to the 'Shutdown command line: (optional)' box shutdown /s /m \ /t 3 /f
As I said, this has worked on boxes with Realtek, Intel, and Qualcomm NICs I have on my network 100% of the time.
Best of luck!