5010 and 5040 AIO Locked on Screensaver

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #51187
    beefy
    Participant
    • Total Post: 37
    • Frequent Flyer
    • ★★★

    We had a few users report that when they arrive to start their shift that the thin client is stuck on the screen saver.  For example, the flying bubbles screen is locked.  The users then have to restart the thin client.  We are using a mixture onf 5010’s and 5040 AIO’s running firmware 8.6_024.

    Here’s part of the INI file that I think is relevant.

    ;*************************************************************
    ;* General 1 *
    ;*************************************************************

    autoload=2 LoadPkg=2 AddPkg=”horizon”
    AdminMode=yes Enc-Username=xxxxxxx Enc-Password=xxxxxx

    ShowAESButton=no

    ;*************************************************************
    ;* General 2 *
    ;*************************************************************

    FormURL=xxxxxxx.png

    ;*************************************************************
    ;* General 3 *
    ;*************************************************************

    Autopower=yes
    SysMode=Classic

    ;*************************************************************
    ;* Privilege *
    ;*************************************************************

    Privilege=High HideConnectionManager=yes CoreDump=Disabled

    ;*************************************************************
    ;* Peripherals *
    ;*************************************************************

    Language=Us ManualOverride=yes
    KeySequence=yes Ctrl+Alt+Left=no Ctrl+Alt+Right=no
    MouseSpeed=1
    Device=audio Volume=25 mic_vol=25 Jack_Popup=no
    Device=Camera format=raw optimize=yes

    ;*************************************************************
    ;* Display *
    ;*************************************************************

    Screen=1 Resolution=1600×900 Refresh=60 Rotate=None
    Screen=2 Resolution=1600×900 Refresh=60 Rotate=None
    Desktop=xxxxxxxxx.jpg Layout=Center IconTextColor=”255 255 255″
    Dualhead=yes Mainscreen=1 Orientation=hort Taskbar=mainscreen Align=Bottom MonitorAutoDetect=yes
    Screensaver=15 LockTerminal=no Type=1

    ;*************************************************************
    ;* Time *
    ;*************************************************************

    Timeserver=0.pool.ntp.org Timeformat=”12-hour format” Dateformat=mm/dd/yyyy
    TimeZone=’GMT – 06:00′ ManualOverride=yes Daylight=yes Start=030207 End=110107 TimeZoneName=”Central” DayLightName=”Central”

    ;*************************************************************
    ;* Network *
    ;*************************************************************

    Device=Ethernet Speed=”Auto”
    TCPTimeout=2
    BootpDisable=yes
    CCMEnable=Yes CCMServer=https://xxxxxxx GroupPrefix=defa GroupKey=xxxxxx MQTTServer=xxxxxxxx CAValidation=no
    SignOn=No DisableEditDomain=yes
    DefaultUser=
    MaxVNCD=1
    VncPassword=”xxxxxxxxxxxx” Encrypt=yes
    VncPrompt=No Accept=10

    #51205
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    Can you try with 8.6_027?

    CG

    #51215
    beefy
    Participant
    • Total Post: 37
    • Frequent Flyer
    • ★★★

    I did upgrade to 8.6_027 earlier this week as a troubleshooting measure on these machines.  I still had the error reported by these users.

    #51259
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    Dell has launched 8.6_206 today. Have a try

    CG

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.