Some Xenith C00X not reading MAC.ini after 2.0_105

This site has given me a lot of help, so I just want to say “THANK YOU!!” in advance. Keep up the good work.

I’m in the process of bringing all 800 of our Xenith C00X devices up to the 2.0_105 firmware. In preparation to deal with the swapping of screens (that was actually introduced in 2.0_104), I automated MAC.ini changes to insert a “Swap=yes” in the “Dualhead=yes” parameter line so that issue would not be experienced by the user. Furthermore, I inserted a “ShowDisplaySettings=yes” if they didn’t have the “Dualhead=yes” parameter so the user could at least have access to check the “Swap dual displays” check box.

Some Xenith C00X devices aren’t reading their MAC.ini file after the firmware flash to 2.0_105. They were reading it previously because they got the Autoload=1 parameter after the reboot from WDM to flash in the first place. But after the flash…about 13 of them on the same VLAN/DHCP scope aren’t reading the automated changes as described above.

Here is a MAC.ini example named like the needed format “0080641a2b3c.ini” of course (where Autoload=1 was scripted in).

Processing > MAC.ini

TerminalName=Foo001

Autoload=1

Privilege=None EnableKeyboardMouseSettings=yes ShowDisplaySettings=yes EnableNetworkTest=yes

DeskColor="0 128 255"

Screensaver="60" LockTerminal=no Type=2 Image=BCBST_screensaver.bmp

Timeserver=ntp.foo.com Timeformat="12-hour format" Dateformat=mm/dd/yyyy

TimeZone='GMT - 06:00' ManualOverride=yes Daylight=yes Start=030207 End=110107 TimeZoneName="Central Standard Time" DayLightName="Central Daylight Time"

Exit=All

I intentionally put the “Processing > MAC.ini” line in the MAC.ini file but it’s not coming up as an invalid parameter in the thin client’s event log. And they don’t have the “Display” menu item available (it’s grayed out). So that would tell me that it’s not reading it now… ❓ I also put “Processing > xen.ini” in the global xen.ini file and “Invalid parameter: Processing > xen.ini” is coming up in the event log.

Here is the kicker…I worked with a tech in that location to swap out one of the Xenith C00X devices that had this issue and the new one (plugged into the same LAN port) flashed from 1.7_122 to 2.0_205 and read the MAC.ini just fine…the automation worked just as intended. ❗ Then he plugged up the original Xenith C00X that wouldn’t read the MAC.ini and it read the MAC.ini this time just fine. 😯 I had already troubleshot this with the user on Tuesday (G key reset/power cycle with power cable out for 30 seconds, etc.) so this makes absolutely no sense to me.

I put a ticket in to Wyse about this on Tuesday, but haven’t had any reply yet. There are about 700 more of these to flash. I had a bout a 13% failure rate on the first rollout, so I’d really like to get that number lower as we hit more devices.

Anyone else seeing this, dealt with it yet?