![]() Num lock became permanently inverted somehow between my host computer and AWS workstation. (Deleted my original post because I made a comment instead of an answer. ![]() We are starting to roll back users who have issues to the last stable build as a short-term fix, but I haven't seen much being mentioned about this outside of my IT organization and was wondering if others have noticed the same issues? There seem to be some bugs with the USB handling in this release based on the way the problems are manifesting. Since we started deploying the 5.0 Amazon Workspaces client, however, we have seen many more users having issues with their headset dropping out and not being recognized by the workspace client despite us replacing the hardware and confirming that they have exceptional internet speeds. Typically, if those steps don't resolve the issue, we can point to a user's slow or unstable internet connection as a likely culprit or narrow it down to a hardware issue with the headset or PC. The headset issues are something that we are used to seeing, but have historically been able to resolve with standard troubleshooting methods such as adjusting the audio settings on the host PC, making sure that the user is not muted inside or outside of Amazon Workspaces, repairing the client and driver installations, restarting the Windows Audio Service inside and outside of Amazon Workspaces, rebooting the workspace and/or local PC, etc. The keyboard issue has only started cropping up in any sort of noticeable numbers since the 5.0 client has begun deployment in our organization earlier this month. This primarily is manifesting as issues where their USB headsets will not be recognized after only a few minutes into their session, but we have been noticing it is causing strange issues with users' keyboards as well where the Caps Lock and Num Lock will not behave as expected inside of Amazon Workspaces despite working just fine on the host PC. Since doing so, we have noticed an increase in users having issues with their USB devices functioning properly in Amazon Workspaces. See PCoIP Connection Manager for Amazon WorkSpaces Administrators' Guide.Our organization has recently started deploying the 5.0 release of the Amazon Workspaces Desktop Client (specifically the Windows version, and most if not all of the Workspaces are running on PCoIP, in case it is relevant). You have a PCoIP® Connection Manager for Amazon WorkSpaces appliance installed and configured.Your network has full connectivity to your Amazon WorkSpaces.You have an AWS account with Amazon WorkSpaces up and running.You are using a Tera2 PCoIP Zero Client (TERA2321 or TERA2140 processor) to connect.This topic includes information on the following sections:įor the best user experience, Teradici recommends using firmware version 6.0 or later with Amazon WorkSpaces (hourly pricing).īefore connecting a Tera2 PCoIP Zero Client to an Amazon WorkSpaces desktop, ensure that the following prerequisites are in place: Tera2 PCoIP Zero Clients together with Amazon WorkSpaces provide a secure, easy to manage solution for delivering users with a rich desktop experience. Connecting to Amazon WorkSpaces Desktops ¶Īmazon WorkSpaces is a fully managed cloud-based desktop service that enables end users to access their documents, applications, and resources. Teradici PCoIP Hardware Accelerator (APEX 2800) Requirements for Trusted Server Connections Viewing Hardware and Firmware InformationĬonfiguring 802.1x Network Device Authorization Viewing Information About Attached Devices Viewing Information about your Zero Client Staging Clients Using an Endpoint Manager OSD View Connection Server + Imprivata OneSign Session SettingsĪWI Direct to Host + SLP Host Discovery Session SettingsĪWI PCoIP Connection Manager Session SettingsĪWI PCoIP Connection Manager + Auto-Logon Session SettingsĪWI View Connection Server Session SettingsĪWI View Connection Server + Auto-Logon Session SettingsĪWI View Connection Server + Kiosk Session SettingsĪWI View Connection Server + Imprivata OneSign Session SettingsĬonnecting to PCoIP Remote Workstation CardsĬonnecting to Teradici Cloud Access SoftwareĬonnecting to Amazon WorkSpaces using the PCoIP Connection Manager for Amazon WorkSpacesĬonnecting Using PCoIP Connection ManagerĬonnecting Using PCoIP Connection Manager + Auto-LogonĬonnecting to VMware Horizon Desktops and ApplicationsĪbout Tera2 PCoIP Zero Client Security Levels OSD View Connection Server + Kiosk Session Settings ![]() ![]() OSD View Connection Server + Auto-Logon Session Settings OSD View Connection Server Session Settings OSD PCoIP Connection Manager + Auto-Logon Session Settings OSD PCoIP Connection Manager Session Settings OSD Direct to Host + SLP Host Discovery Session Setting What Can You Connect to Using Your Tera2 PcoIP Zero ClientĬonnecting your Zero Client to the Network PCoIP Zero Client Firmware 6.3 Administrators Guide ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |