Unanswered Questions tagged with Amazon WorkSpaces
Content language: English
Sort by most recent
Browse through the questions and answers listed below or filter and sort to narrow down your results.
Directory deregister is not possible even though all workspaces have been deleted
For testing, I registered Directory to Workspaces. After completing the test, I deleted Workspaces and tried Directory deregister. However, deregister failed with the following error message. == An Error Has Occurred. If you continue to experience an issue contact the AWS Support Team on the community forums and via AWS Premium Support at: AWS Support Center. == When checking the corresponding DeregisterWorkspaceDirectory event in CloudTrail's event history, the following error message was confirmed. == "errorMessage": "There are WorkSpaces assigned to this directory. You must remove the WorkSpaces before you deregister the directory.", == Contrary to the error message, all WorkSpaces associated with the directory are in a state of being deleted. Even if I commanded the describe-workspaces command through the AWS CLI, it is confirmed that there are no Workspaces in the current target region. Is there anything else that can be checked in that situation? If the issue you are experiencing is caused by a bug, is there a way to report the bug?
Need help in managing in AWS workspace running mode
Dear Amazonian, I had setup Amazon workspace POC in past & i was able to achieve our requirements. However i will setup another POC this weekend on AWS workspace - what i need to know is : Is it possible to auto stop workspace (ubuntu desktop) of our student after its 3hours of usage in a singel day ? as part of cost consideration - we dont want our students to use the desktop for entire day. I would be grateful if you let me know what options i have to achieve this.
WorkDocs Drive Installation
I am having issue with installing WorkDocs Drive. Initially it was installed and worked for about a week before disappearing. Whenever I try to install again I get the following 2 error codes 2503 and 2502. I have received advice to uninstall WorkDocs Drive however the issue that I have is that the WockDocs Drive is not currently installed. I cannot see it in the program list so therefor I cant uninstall it. If I try to uninstall or repair I get the message that it is not installed. I have rebooted the workspace and confirmed that the latest .net framework is installed. Still receive error code 2503 and 2502. Any advice here would be greatly appreciated.
Amazon Workspaces Client not working
I am using an ARM Linux machine, with which i am trying to access AWS Workspaces Desktop, but the Linux deb file is for amd64 architecture (i am using arm64 architecture). I tried to access via the Amazon Workspaces Client web option, but i get the error - ERROR_TYPE_CONNECTION An error occurred while connecting to your WorkSpace. If the problem persists please contact your WorkSpaces administrator. ERR_SIG_TIMEOUT
Problems using the Amazon Workspaces Client
I am trying to access my workspaces cloud machine via different Workspaces Clients. While using the app on my phone, i successfully get connected and presented with the cloud-machine screen. But, the keyboard of the phone wouldn't show after i pass successfully the login page. So, I tried accessing via the Amazon WorkSpaces Web client, but i get an error saying that it took to long to log in, and log in failed. Iv'e tried a fast 5G internet connection but it failed as well, after attempting to log for a few minutes. I am using an ARM Linux machine to access the AWS services, so installing the Amazon WorkSpaces client as a software on my machine proved impossible by far. Althrough there is an ARM version for the MAC abviously, there is non for linux (the linux amazon workspaces client software is for amd proccessors only). What should i do in order to solve those issues?
Need to login twice to Windows workspaces since update to client version 188.8.131.5223
Since we updated to the Workspaces client version 184.108.40.20623 some of our users now need to log into their machine twice: first with the client and then again to the Windows instance (the remote access is not automatically granted with succesful login thru the client). * This only started after we updated the client to version 220.127.116.1123 * This only affect users which had migrated their machine from Windows Server 2016 to 2019 * Users that are on Windows Server 2016 and did not migrate are not affected * The clients and the AWS workpaces are both on Windows OS. * The workspaces are WSP. Has anyone encountered such scenario and found a fix? It is not a show stopper but it is annoying for the users affected.
WorkSpaces freezing upon WorkSpaces Client screen resize
Has anyone else had issues with WorkSpaces freezing upon dragging to resize the client? I have had this at multiple clients with multiple unrelated AWS environments. Doesn't matter what version of the Amazon WorkSpaces Client software you use. Basically, what happens is: 1. You log on, let's say with the WorkSpaces Client for Windows. Everything is fine. 2. You drag the edge of the WorkSpaces Client to make the window of the application larger, OR let's say you go to Full Screen mode. 3. The client simply freezes. The desktop does not immediately resize, OR the screen goes black. 4. It stays frozen for about 5 mins, then magically the resize "catches up" and everything settles down and goes back to normal. 5. It also happens if you use a zero client, but the WorkSpace was previously running in the WorkSpaces Client software (and sized for the client it was running on) and thus needs to resize again to fit the zero client. Or vice versa. Hope I'm explaining this properly. It does not happen on all WorkSpaces at all times. There does not even need to be any applications open. However, when it does start to happen on a particular WorkSpace, it is very repeatable on that WorkSpace for a considerable amount of time (like all day, or occasionally all week). Multiple reboots and it still recurs. Then on another day it might not do it at all, and resizes work fine on that same WorkSpace. I can't think of any common denominator that these WorkSpaces have. Maybe ScreenConnect? Incidentally, if you view the desktop through ScreenConnect while this is happening, it remains “stuck” - you click on things, nothing happens - you can't really interact with it…but you *can* connect to it. Interestingly, it does not disconnect the session. And if you send a reboot command it immediately restarts the WorkSpace, so it is still "alive" so to speak. I'm curious to hear if anyone else has run into this. Thanks!
Copy / Paste Issue Between Multiple Monitors on Linux Client
Hello, I am using Amazon workspaces on a Linux client. The Linux flavor is Ubuntu. The Amazon workspaces are Windows 10. My issue is that I cannot copy / past anything across multiple monitors. I can copy and paste between the physical machine and the amazon workspaces, but I cannot copy any info from my first monitor to my secondary monitor. I checked to be sure copy and paste was working fine on my Linux machine and it is working just fine. I have been googling solutions but have not had much luck. Anything helps. Thanks!