Two days ago I was handed a Wyse device and told to find a way to manage it remotely. This was also the first time I had seen such an innocuous looking device. Needless to say I have as yet been unable to get it to work, and I’m now relatively convinced that it’s something simple, and amazingly daft that I am not doing.
So here’s the deal: I have a Wyse C30LE device, plugged into a network. I then have a virtual machine, running Windows XP, on which WDM 4.8.5 is installed.
WDM does not speak to the C30LE device. I’ve added the subnet and the IP range. They’re both on the same subnet, the same network, but they aren’t speaking.
I need help, and I don’t know where to start. So remember, I saw this for the time on Friday, HELP!
I’ve tried to install the WDM on Windows Server 2008R2, which was successful, but then read in the Installation guide that I may need to upgrade the HAgent on the Wyse device, which I have no idea how to do, or how to even find out the version number of the HAgent on the device.
Can anyone assist a person who is about to run repeatedly into a brick wall to make the frustration stop?
There’s a WDM applet in the Control Panel of your C30LE. Check it for the right WDM IP inside. If it is empty or wrong (should point to your virtual XP with WDM server) – hard code this IP into it. Reboot C30. Take a look at WDM server – C30 should be there. If not: 1)turn off firewall on WDM VM 2)Take a look at WDM server log (WDM icon in the WDM XP VM tray) – it will give you a lot of info. You can setup logging preferences in the WDM configuration Just drag and drop HAgent package (WDM packages branch) to the device manger brach of the WDM when C30 is in the WDM. This will pop up wisard window – everything is stright forward further.