VMware Horizon Community
BenFB
Virtuoso
Virtuoso
Jump to solution

Skye status intermittently stuck on "Away" with Blast Extreme through UAG

We are seeing an intermittent issue with remote users using Blast Extreme through a UAG where Skype thinks the user is still Away. You can not manually set it to Available and the Skye client must be quit and relaunched to set the status properly.

When a user connects internally with a Dell Wyse P25/5030 zero client using PCoIP it works as expected. Skype properly detects the user is connected and sets the status to Available.

We are running Horizon 7.1, Horizon Agent 7.1 on Windows 7, UAG 3.0, Horizon Client 4.5.1, Lync 2013 Standard Edition and Skype for Business 2016.

Labels (1)
0 Kudos
1 Solution

Accepted Solutions
BenFB
Virtuoso
Virtuoso
Jump to solution

We upgraded to 7.4.0 and confirmed that the bug is resolved. We tried 7.3.2 but had to rollback due to an unrelated bug with zero clients.

View solution in original post

0 Kudos
4 Replies
BenFB
Virtuoso
Virtuoso
Jump to solution

We did some further testing and we are able to consistently reproduce this issue. This only happens when a user has an active PCoIP session and takes over the session on a different device using Blast Extreme. It does not happen when a user has an active Blast Extreme session and takes over the session on a different device using Blast Extreme. When Skype is stuck with a status of "Away" you are able to set other away statuses such as "Be Right Back", "Off Work" and "Appear Away". You have to quit and relaunch Skype for the status to switch back to "Available" which allows the user to set any status.

markbenson​ Are you my guy for Blast Extreme issues or only for UAG?

0 Kudos
BenFB
Virtuoso
Virtuoso
Jump to solution

This has been acknowledged as a bug in 7.1/7.2 and we are awaiting a future release to fix it.

0 Kudos
BenFB
Virtuoso
Virtuoso
Jump to solution

VMware tells us that this is fixed in 7.3.1. We have a scheduled upgrade next week to 7.3.2 to confirm.

0 Kudos
BenFB
Virtuoso
Virtuoso
Jump to solution

We upgraded to 7.4.0 and confirmed that the bug is resolved. We tried 7.3.2 but had to rollback due to an unrelated bug with zero clients.

0 Kudos