No cursor indicator in Office 2010

  • This topic is empty.
Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • #7289
    aLiE
    Participant
    • Total Post: 320
    • Jacked into The Matrix
    • ★★★★★★

    We have updated our Wyse devices with firmware (for now only the S10) 7.1.122 and now we are facing a weird issue.

    When using XenApp 6.5 and Office 2010 you will notice that the cursor indicator is gone it just stopped blinking (seams tobe disappeared to me), but if you go to notepad or wordpad you notice that the blinking cursor indicator is there.
    We did a rollback to firmware 7.1.033 and all was/is fine again the blinking cursor indicator in Winword is back again, we move back to firmware 7.1.122 and the blinking cursor just disappeared but not in notepad/wordpad.

    For now we did a test with our S10 and using Citrix XenApp 6.5 and Office 2010 fully patched with all hotfixes and needed service pack, if you shadow the user you can see the blinking cursor indicator.

    Anyone got a idea what it could be or can at least confirm to have the same issue ?

    #22170
    Amerist
    Participant
    • Total Post: 61
    • Back Stage Pass
    • ★★★★

    Thanks for the heads up. I’ll make sure we test this firmware on a single device before we update to XA 6.5 in June.

    #22439
    jgrotnes
    Member
    • Total Post: 6
    • Newbie

    aLiE, I can confirm the exact same experience on our system. We have 10000 S50’s and are in a conversion process to make these S10s. The OS we’ve used is WTOS 7.1_122, but we started getting reports that the text cursor would disappear in the free text areas of Word 2010 and Outlook 2010 on our XenApp 6.5 server farm. The text cursor (“caret”) is visible in text fields such as Outlook subject line, but not in the body area. We have created a support case with Wyse. Downgrading the OS to WTOS7.1_033 solved the problem for us until we can get a fix/explanation from WYSE.

    #22440
    aLiE
    Participant
    • Total Post: 320
    • Jacked into The Matrix
    • ★★★★★★

    @jgrotnes wrote:

    …… We have created a support case with Wyse. Downgrading the OS to WTOS7.1_033 solved the problem for us until we can get a fix/explanation from WYSE.

    Great, i also contacted Wyse but as usual they are very slow with their response. Untill then we are using 7.1.033

    #22444
    ConfGen
    Keymaster
    • Total Post: 11485
    • Jedi Master
    • ★★★★★★★

    Looks like this is fixed in the newest HF release 7.1_125.

    CG

    #22449
    aLiE
    Participant
    • Total Post: 320
    • Jacked into The Matrix
    • ★★★★★★

    Got a email notification about the Hotfix release 7.1_125 but guess what, i’m able to download the hotfix for C10LE, V10L, T10 but there is no download available for the S10 …… 🙁

    #22521
    aLiE
    Participant
    • Total Post: 320
    • Jacked into The Matrix
    • ★★★★★★

    Just updating my post, Wyse Support replied to me that there will be no hotfix 7.1.125 available for the S10 which made me very very sad.

    #22681
    theasc
    Member
    • Total Post: 5
    • Newbie

    We have the same problem and received a 7.1.128 Beta from Wyse Support which fixes the problem 🙂

    #22684
    aLiE
    Participant
    • Total Post: 320
    • Jacked into The Matrix
    • ★★★★★★

    Bahh Wyse Support is slow as usual, i’m still waiting for a fix for the S10

    #22741
    aLiE
    Participant
    • Total Post: 320
    • Jacked into The Matrix
    • ★★★★★★

    Problem is solved in firmware 7.1.130, which is available for download.

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