Pavman27

Forum Replies Created

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • in reply to: WMS Move to new server #68098
    Pavman27
    Participant
    • Total Post: 6
    • Newbie

    Let’s say I build a test server and register my thin clients with that WMS instance. Later, when I build a new WMS server, when I change the DHCP options to the new server, will the thins automatically come over to the new server, or do they have to be unregistered first?

    Thanks,

    Dave

    in reply to: Xenith No Operating System Found? #24343
    Pavman27
    Participant
    • Total Post: 6
    • Newbie

    For anyone who is purchasing Xenith thin clients: Make sure it has a drive (memory module, etc). I bought two then found out the DOM’s were missing.

    I purchased two replacement 1GB DOM’s for two Xenith WYSE Pro’s and tried to use the USB download tool to install the Merlin packages.

    One WYSE copies the images, but then craps out during the file copy with what reads like sector issues. It then fails the BIOS update with a image file size mismatch. Through this process, it damages the USB drive, so it can’t boot again and must be re-imaged.

    The other device complains about a security key failure. Interesting, because it is a Xenith Pro. Maybe someone slipped me the JP version??

    Word to the wise: If you buy something used, make sure it boots perfectly the first day. If it doesn’t, you might have bought a brick. ReImaging these devices is a pain, and not very straightforward….

    in reply to: Xenith No Operating System Found? #24316
    Pavman27
    Participant
    • Total Post: 6
    • Newbie

    I fell into the trap. I found two Xenith Pro’s for (what I thought were) a sweet deal. Turns out the sellers yanked the USB ATA Modules, and like your situation, they do not boot.

    Were you able to find a replacement for the modules?

    or is there a PXE method to get the units to boot?

    Thanks.

    in reply to: XenApp6.5 and the Taskbar #24315
    Pavman27
    Participant
    • Total Post: 6
    • Newbie

    Sorry.. Digging for another issue and I found this old post. This turned out to be an issue with 2.0.015 firmware that I was running. It shows a corrected in the next release. A firmware upgrade cleared the issue.

Viewing 4 posts - 1 through 4 (of 4 total)