The MultiPoint Server 2012 installed without error and I verified that the UR2 update is installed. The latest MCT driver installed without error and the Network Stations tab shows in Multipoint Manager. The Wyse E02 client acquires a proper IP address and shows up in the Multipoint Manager under Network Stations and I was able to assign the E02 client to the Multipoint server without error and it shows up under Assigned Clients as "Connected". When starting up, the LCD monitor (Dell 19" 1280x1024 native) connected to the Wyse E02 client works fine and displays the message "Windows Multipoint Server" and some additional text that the client is assigned to the Multipoint server. So far everything is working great.
The problem is that the Wyse E02 client then clears the display, pauses for a couple seconds, and then displays garbage text on the connected monitor. The garbage text on the E02 client monitor almost appears as if the E02 client is outputting the wrong frequency or some unsupported display resolution to the monitor. I have tried connecting other monitors and all display the same garbage text, so I am certain the problem is not in the monitor. I also swapped in different Wyse E02 client devices, with the same result, so I am certain the problem is not in the Wyse E02 client.
When I switch the Multipoint Server to Console mode and run the "USB Display Device" application "MCT Custom Presenter" (as outlined in the MCT documentation that came with the MCT driver), the Wyse E02 client doesn't show up in the application.
Did I miss a Multipoint Server driver update somewhere during the installation process?
Am I using the wrong Multipoint server driver for the Wyse E02 client? Is there a driver other than the MCT driver for the Wyse E02 client?
Any help would be greatly appreciated, as I am in process to finish setting up a new computer lab using Multipoint Server 2012 and Wyse E02 clients for our school.
Thanks.