lolix

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 154 total)
  • Author
    Posts
  • in reply to: Wyse 5070 Extended #107706
    lolix
    Participant
    • Total Post: 218
    • Jacked into The Matrix
    • ★★★★★★

    Anyway, the usual performance tweak is to use UDP, as you do and lower color mode to 16bits

    (BTW, ThinsOS 9 is still a work-in-progress as regards RDP protocol, IMO. For instance there is no RemoteFX)

    in reply to: Wyse 5070 Extended #107705
    lolix
    Participant
    • Total Post: 218
    • Jacked into The Matrix
    • ★★★★★★

    I mean, we’seen devices negotiating 100Mb/ Half-duplex instead of full-duplex. Was a switch issue.

    in reply to: Wyse 5070 Extended #107704
    lolix
    Participant
    • Total Post: 218
    • Jacked into The Matrix
    • ★★★★★★

    Hi,

    There ‘s no reason for ThinOS 8.6 to be laggy on that simple thing. Especially when you have disabled the content when moving windows.

    We have a number (regular) 5070s w/ two 27″ screens. (2560*1440). Which is approx the same order of pixels of a single 4k screen and there’s no such problem.

    It starts being laggy when watching full screen videos.

    Are you sure that the network topology on the 5070 is OK ?

     

    in reply to: ThinOS 9.1.3112 slow direct RDP connection #107549
    lolix
    Participant
    • Total Post: 218
    • Jacked into The Matrix
    • ★★★★★★

    Did you enable AVD AVC/H264 Hardware Decoder ?

    Don’t.

    in reply to: RDP freeze and ThinOS 9.1.6108 #107480
    lolix
    Participant
    • Total Post: 218
    • Jacked into The Matrix
    • ★★★★★★

    During early tests of 9.1, disabling AVC/H264 was the advice of Dell Support to solved (rather workaround) a Green Screen of Death when whatching videos. (Through Bare bone RDP)

    I didn’t try to enable it recently with 9.1.x

    We ‘re still on 8.6 for production devices BTW.

    ThinOS 9 bugs and shortcomings are solved at a slow pace..

    • This reply was modified 3 months ago by lolix.
    lolix
    Participant
    • Total Post: 218
    • Jacked into The Matrix
    • ★★★★★★

    You may try to force low level USB redirection of the device (so it is seen as local on the host) and then you may be able to use the software that drives it… if any.

    In your ini file you add something like

    Device=vusb ForceRedirect=0x0b33,0x1004,0x03,0x01,0x00

    lolix
    Participant
    • Total Post: 218
    • Jacked into The Matrix
    • ★★★★★★

    ThinOS 9 – RemoteFX not available. Confirmed by DELL support.

    Shame on DELL-Wyse

    The weirdest part : Once you have connect an USB drive, the remote drive will *always* be there. USB drive present or not, VM reboot or not, Wyse reboot or not…

    This remote drive is in fact a fake drive and the root for all USB drives. If two drives are plugged, you get two sub-directories under the remote drive.

    Another bad side effect is Camera support. A Camera is now seen as remote camera and not local / RemoteFX. Mine (logitech C270) performs badly. I noticed that the upstream from the Wyse to the VM is ~50Mb/s, whereas it is ~18 Mb/s with a ThinOS 8 /RemoteFX redirection.

    Long life ThinOS 8 !

     

     

    in reply to: Upgrade to WMS 3.6 from 3.5.2 #107189
    lolix
    Participant
    • Total Post: 218
    • Jacked into The Matrix
    • ★★★★★★

    3.5.2 to 3.6-241 went well

    while the previous upgrade from 3.3.1 to 3.5.2 failed. (MariaDB pb..)

    (Why this product needs two databases anyway ? Seems overkill)

    in reply to: WMS 3.5.2 – Devices name #107188
    lolix
    Participant
    • Total Post: 218
    • Jacked into The Matrix
    • ★★★★★★

    Thanks for the clarification.

    I *could* to that for my ~100 devices, even though It will be cumbersome.

    I can’t imagine people managing thousands of devices doing that.

    My questioning remains : Why the default naming scheme isn’t DNS based ? This is flabbergasting.

    in reply to: Wheel mouse scrolling inconsistency (ThinOS 9.1.5 / RDP) #107055
    lolix
    Participant
    • Total Post: 218
    • Jacked into The Matrix
    • ★★★★★★

    Tested with 2 different mice. A Dell Wired and a Logitech wireless. This is definitely a driver issue.

    Of course, ThinOS 8 is OK in that regards (business as usual..)

    in reply to: WMS 3.5.2 – Devices name #107030
    lolix
    Participant
    • Total Post: 218
    • Jacked into The Matrix
    • ★★★★★★

    I’m not sure if you’re talking about WMS 3.5.2. There is no “More action” yes ?

    What I can do, is create an exception to the group policy and name the device there

    But,  I’m not going to change one hundred names manually while there is something called DNS, which is designed to do that automatically.;-/

    There are probably cases for another naming scheme (although I don’t quite find one) , but the obvious naming scheme (DNS) should be the default.

    Worth to note that was the default with ThinOS 8.

    It turns out that the $IP thing worked until ThinOS 9.1.3 / WMS 3.3.1.That couple displayed the DNS name for “compliant”(i.e. powered ON) devices. Even though the actual name of the device is the @IP. But apparently that was not intended according to DELL support.

    I made an enhancement request to get a $DNS variable.

    in reply to: Direct RDP session issue – WMS 3.5.2 THINOS 9.1.5067 #107014
    lolix
    Participant
    • Total Post: 218
    • Jacked into The Matrix
    • ★★★★★★

    Same problem. Ticket open at Dell.

    in reply to: WMS 3.1 to 3.5.2 – Easiest upgrade path? #107002
    lolix
    Participant
    • Total Post: 218
    • Jacked into The Matrix
    • ★★★★★★

    With the help of dell, the upgrade from 3.3.1 to 3.5.2 is achieved. We had to put a bunch of missing MariaDB files within the bin directory

    in reply to: WMS 3.1 to 3.5.2 – Easiest upgrade path? #106999
    lolix
    Participant
    • Total Post: 218
    • Jacked into The Matrix
    • ★★★★★★

    So keep a backup, before any upgrade attempt…

    in reply to: WMS 3.1 to 3.5.2 – Easiest upgrade path? #106998
    lolix
    Participant
    • Total Post: 218
    • Jacked into The Matrix
    • ★★★★★★

    I have a case open at Dell because upgrade from 3.3.1 to 3.5.2 fails…

    After the upgrade, the mariaDB service fails to start (because there is no mariaDB anymore…gone)

Viewing 15 posts - 1 through 15 (of 154 total)