I have created a modified version that will use a batch file instead of just one command... I did this becuase i noticed that alot of my servers werent mapping as they should because I was staticly mapping the interface i was using like I explained to FrankW

((my own advice cought up with me))

soo what this does is runs the command tcpdump.exe -D on the remote computer this will give you a list of interfaces found on that computer. You will be prompted to enter 1 - X you can reference the wake on lan interface if you dont know which interface is active. then it will take your response and append it in the batch file. and will get the desired ports info.
the custom action command is
cmd.exe /K "{actionpath}PortMapper.bat {actionpath} {ipaddress} {actionpath} {actionpath} {ipaddress}"
you will want to please this inside the batch file PortMapper.bat
@echo off
%1psexec.exe \\%2 taskkill /F /IM tcpdump.exe
%1psexec.exe \\%2 -c -f %3tcpdump.exe -D
%1psexec.exe \\%2 ipconfig /all
:input
set INPUT=
echo.
echo.
echo.
set /P INPUT=Type Interface: %INPUT%
%1psexec.exe \\%2 -c -f %3tcpdump.exe -i %INPUT% -nn -v -s 1500 -c 1 ether[20:2] == 0x2000 | findstr "Device-ID Address Port-ID Platform" & %4psexec \\%5
cmd DEL c:\Windows\System32\tcpdump.exe"
and that should solve the issue with some computers not working and others working.