reboots on Wyse C10le’s on 7.1_033 (not timezone related!)

  • This topic is empty.
Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #7754
    bspies
    Member
    • Total Post: 18
    • Regular Joe
    • ★★

    We just upgraded the firmware on our C10LE’s
    Units in one particular timezone are rebooting after some random time’s between 5 to 15 minutes of use.

    The timezone is Saskatchewan.

    Also just so you know we are connecting to a XenApp 6 published Desktop, where XA will inherit the timezone of the client device. This was working fine before the firmware upgrade. We also use a Cisco based time server as well that we point to in our wnos.ini file.

    Saskatchewan if I recall was not a timezone we could actually choose prior to the firmware upgrade and because of that we used this setting in the units $mac files:

    TimeZone='GMT - 06:00' ManualOverride=yes Daylight=no Start=030207 End=110107 TimeZoneName="Central Standard Time" DayLightName="Central Standard Time"

    This worked fine – Saskatchewan does not observe daylight savings time, and I could not choose Saskatchewan as a timezone in the ConfGen at the time. (I still cannot using 6.4.05)

    Now if I take a C10LE’s and change its $mac file to use this TimeZone setting I can duplicate the problem.

    If I change it to Mountain Time for example the problem goes away.

    I have been struggling to find the magic string that will give us Saskatchewan time without this reboot occuring and have getting super frustrated. In the Wyse OS GUI I can actually see a Saskatchewan timezone listed but I cannot set it via the $mac file.

    This is the latest attempt, which still gives us the reboot:

    TimeZone='GMT - 06:00' ManualOverride=yes Daylight=no TimeZoneName="Saskatchewan" DayLightName="Saskatchewan"

    I have also tried this

    TimeZone='GMT - 06:00' ManualOverride=yes Daylight=no TimeZoneName="Saskatchewan"

    I should note as well if I check the Wyse unit it still says Central, and in Citrix it also says Central even though I am specifying Saskatchewan.

    I am sure the population of Wyse administrators like me that have to work with Saskatchewan time zones is rather small … but does anyone have a suggestion?

    in the short term I am thinking of setting our units to mountain time as a temporary messure as our user base is getting very frustrated.

    Thanks

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

    What exact timezone is shown in the Citrix session when you correctly select Saskatchewan in the session?
    Use this string in your wnos.ini setting.

    This is from the INI guide:

    TimeZoneName — Display name sent to the ICA/RDP session (such as
    Eastern Standard Time).
    DayLightName — Display name for daylight saving time. If daylight saving
    time is enabled, DayLightName should be named something similar to
    Eastern Daylight Time, otherwise it should be the same as TimeZoneName.

    CG

    #23596
    bspies
    Member
    • Total Post: 18
    • Regular Joe
    • ★★

    Hello

    It has come to my attention that our Wyse terminals are auto rebooting on their own all over and not just in Saskachewan as I thought. Therefore this issue probably has nothing to do with the timezone at all.

    Should I post a new question then or keep this alive?

    I am at a loss – this is difficult to test – and now I am thinking we should roll back.

    Bruce

    #23597
    bspies
    Member
    • Total Post: 18
    • Regular Joe
    • ★★

    This is the first half of our wnos.ini file, minus some names I took out since I am posting this online

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

    ;*************************************************************
    autoload=1
    Fileserver=WDM01.COMPANY.PVT Username=anonymous [email protected]
    Rapportserver=WDM01.COMPANY.PVT Retry=3
    AdminMode=yes Username=wyseadmin Password=xxxxxxxx
    Privilege=None HidePPP=yes EnableNetworkTest=yes ShowDisplaySettings=Yes EnableKeyboardMouseSettings=yes SuppressTaskbar=auto KeepDHCPRequestIP=yes EnablePrinterSettings=no
    MirrorFileServer=yes

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

    FormURL=wyse.bmp
    Inactive=120
    Locale=English
    Device=audio Volume=24 mic_mute=1
    Device=vusb Type=HDX

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

    NoticeFile=Noticefile.txt Resizable=yes Timeout=100
    Autopower=no
    AutoSignoff=yes Reboot=yes
    ShutdownCount=5
    BootOrder=HardDisk;USB;PXE
    SysMode=VDI toolbarclick=yes toolbardelay=1

    ;*************************************************************
    ;* Input Devices *
    ;*************************************************************

    Language=Us

    Is there anything in here that can explain why with the latest firmware a unit might auto restart on its own? the auto restart prompt I am seeing does have a 5 second count down like we set in this ini file. However we never had this issue before when we were on 7.0_113

    Thanks

    #23598
    bspies
    Member
    • Total Post: 18
    • Regular Joe
    • ★★

    Hello – just a quick update – While reseraching this problem I happened across this older forum post http://www.freewysemonkeys.com/modules.php?name=Forums&file=viewtopic&t=6342&highlight=sessionreliability and the symtpoms seemed very similar, except in the OP’s scenerio there is no reboot. We reboot when user sessons end though, which would explain the Auto signoff and 5 second countdown. I also noticed “heavy use” could trigger the auto signoff and subsequent reboot.

    So for now I have turned off SessionReliability and am trying to see if this has resolved our issue. Only time will tell.

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