vanyouss

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 30 total)
  • Author
    Posts
  • in reply to: Disable or Hide the float bar floating bar during login #107204
    vanyouss
    Participant
    • Total Post: 41
    • Frequent Flyer
    • ★★★

    still the same problem here and I’m running WMS cloud version: 3.6 241

    in reply to: Disable or Hide the float bar floating bar during login #107096
    vanyouss
    Participant
    • Total Post: 41
    • Frequent Flyer
    • ★★★

    I still get annoyed with this floating bar, I will contact our Dell rep to address this.

    in reply to: How to Disable VDI Menu on 9.1 #106380
    vanyouss
    Participant
    • Total Post: 41
    • Frequent Flyer
    • ★★★

    Thanks migeauxy for sharing this, with this version I started realizing that even changing devices to a different Group will initiate a reboot and will move it to the designated group but then move it back to the source group after the reboot.

    the funny thing is the device name will be reset to default 🙁

     

     

    in reply to: How to Disable VDI Menu on 9.1 #106372
    vanyouss
    Participant
    • Total Post: 41
    • Frequent Flyer
    • ★★★

    Hi Jim,

    unfortunately the Right-Click on desktop to access admin mode is not working because of Imprivata taking over the logon screen. is there any other way?

     

    Thank you,

    in reply to: WMS and ThinOS 9.X #105517
    vanyouss
    Participant
    • Total Post: 41
    • Frequent Flyer
    • ★★★

    I just bought 5470 AIO and updated FW to 9.1, things are a little different than the previous setup, now I’m not getting connected to VMware Broker, I get error: Failed

    in reply to: HOW TO UPGRADE THINOS CORRECTLY #105346
    vanyouss
    Participant
    • Total Post: 41
    • Frequent Flyer
    • ★★★

    I’m having the same problem here, I got the 5470 AIO with 8.6_412 FW, when I setup a policy to upgrade FW from 8.6 to 9.1 it wouldn’t take it not take the latest 8.6 FW version (8.6_710)

     

     

    in reply to: WMS not updating Checked-in Clients #105259
    vanyouss
    Participant
    • Total Post: 41
    • Frequent Flyer
    • ★★★

    I think you are right, that’s exactly what happened to me, somehow you should never use your licenses at 100% otherwise you will get some TCs not checking in properly because of the WMS license.

     

    in reply to: WMS not updating Checked-in Clients #105228
    vanyouss
    Participant
    • Total Post: 41
    • Frequent Flyer
    • ★★★

    did you check the logs to see what’s causing this? is it licensing or ports been blocked?

    I had to open a port and re-register the non-compliant TCs.

    in reply to: WMS not updating Checked-in Clients #104941
    vanyouss
    Participant
    • Total Post: 41
    • Frequent Flyer
    • ★★★

    I’m using all my licenses ( I have 300 seat)

    in reply to: WMS not updating Checked-in Clients #104922
    vanyouss
    Participant
    • Total Post: 41
    • Frequent Flyer
    • ★★★

    I’m using WMS Cloud

    in reply to: WMS not updating Checked-in Clients #104891
    vanyouss
    Participant
    • Total Post: 41
    • Frequent Flyer
    • ★★★

    I was also thinking it may happen because of my WMS licensing, I already reached 100% of TC seats, I checked few thin clients they are showing this message:

    WMS Failed to register (Server License is invalid).

     

    any thoughts?

     

    in reply to: WMS not updating Checked-in Clients #104890
    vanyouss
    Participant
    • Total Post: 41
    • Frequent Flyer
    • ★★★

    Yes I still can access the WMS web GUI, I will look into the port 443 and get back to you

     

    Thank you

    in reply to: BIOS Settings on WMS not working #52666
    vanyouss
    Participant
    • Total Post: 41
    • Frequent Flyer
    • ★★★

    If I use the Legacy Wyse Bios I get :

    CMOS: failed to set BIOS password

    in reply to: BIOS Settings on WMS not working #52665
    vanyouss
    Participant
    • Total Post: 41
    • Frequent Flyer
    • ★★★

    I used both ini parameters for both: Dell Bios and Legacy Wyse Bios:

    Device=CMOS AutoPower=yes BootFromUSB=no CurrentPassword=Password1 NewPassword=Password2

    Device=DellCmos CurrentPassword=”Password1″ NewPassword=”Password2″ ACRecovery=PowerOn USBBootSupport=no

     

     

    in reply to: Invalid CONNECTIONBROKER parameter: PCoIP #52655
    vanyouss
    Participant
    • Total Post: 41
    • Frequent Flyer
    • ★★★

    I noticed that Teradici PCoIP did not get install, I tried another FW with PCoIP and failed because it’s not the right one.

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