Looking at the Wiki, the script looks for the GC100 at the non-DHCP default address. (Caution: I haven't gotten a chance to go through the actual script yet). A default factory reset for the GC100 with the new firmware puts it in DHCP mode. It will get a valid DHCP IP address from the server, which almost definitely will not be the address where the script is looking for it. I see two options here:
a)Manually (through the GC100 web page) configure the GC100 to the static IP that the LMCE script expects the unit to posess or
b)Power the unit up without it connected to a DHCP server. After some time out, it's supposed to revert to the static IP address that the script tries to find. I haven't tested it yet, so I don't know if you can simply power it up with the ethernet cable unplugged, or whether the timeout period starts when a link is established. If it's the latter, option 1.a becomes the preferred choice
2)The new firmware also includes a tcp beacon that announces the GC100's presence on the LAN. It includes MAC address and GC100 type, as well. If LMCE opened a socket to look for that beacon message, it could autodect a GC100 and announce without having to press the button on the orbiter and go through the contortions of the current script.
I like 2) but that means someone has to do it.