Questions tagged with Amazon WorkSpaces
Content language: English
Sort by most recent
Unable to create Workspace
After creating several workspaces, today I am getting the 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." Not much info here. Does anyone have any tips on where to look for the error? Or what it might be?
Measuring throughput while checking network health
I just wonder why network health feature is only checking round trip time. On the below screenshot I **know** I have network issues, the bandwidth is rate limited to 0.7 Mbps, still I get reassuring 'No problem here' answer when checking network health. ![Enter image description here](/media/postImages/original/IMq95kjGfLQlGS6u3FSKK7Sw) IMO, network health depends on more factors than just solely round trip time.
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.
How to Access Administration Account On Workspace to Admin Simple AD.
I want to admin a Simple AD for Workspace (windows). However I can't seem to find the answer I'm looking for. Has anyone got any personal experience with this? I've had lots of people say that I just need to be logged in with the correct credentials. I have the correct credentials, what I lack is the ability to access Workspaces with those credentials. I just want global admin access to the AD in order to manage all the users. My notes of what I have tried below * 1stly, I'm logged in as the main admin for AWS. I have access to everything. * When you create a Workspace, you can add a single user to a workspace and they act as a Local Admin. They can not administer the AD. The options are greyed out. * When you set up Simple AD, you create a admin password. However, there is no way of accessing Workspace with the Administrator and password. When you try to create a Workspace with the Administrator profile, i get an error saying you can do that on a service account. * The user guides say that you need to connect an EC2 instance to the domain, But When I do that, I am unable to see the domain in AD tools, despite being part of the domain. I've added all the correct Features (AD DS and AD LDS Tools & DNS Server Tools) but the domain does not show up and there is no way of accessing the domain via this route. The error you get is "To Manage User, Groups and computer in a domain, log on a as a user with domain administrator rights". Can someone please let me know how to administrate Simple AD? I've spent all week researching and experimenting and I'm completely stumped. Thanks
AWS Workstation Admin
I am struggling to figure out how administrate a SIMPLE AD from within a Workspace. I have created a workspace with a new domain, and run up a Windows instance. When I added the AD DS and AD LDS Tool & DNS Server Tools, I was unable to edit any of the Users. Reading the help guides, it mentioned that you need to manage it via an EC2 instance. So, I Run up an EC2 instance on the same domain, but now when I look at changing it tells me I need to be a domain admin, as I'm logged in as a local user. None of my user log ins work with EC2, and i'm completely locked out from being able to manage the AD. How do I gain access to Admin the SIMPLE AD on a Workspace domain?
Amazon Workspace Client crashes before connecting to server
Hi, I cannot access our workspaces VM with the desktop client I installed on my IMac. The client works well in Windows, no problem with the server. However, on my Imac, I downloaded the client, I log in with the credentials, everything is ok, the wheel is spinning, [see screenshot here](https://screencast-o-matic.com/i/c3Xj16VusxJ). And then, just at the end when the connection needs to be established, it crashes and [it gives me this error code (google doc link).](https://docs.google.com/document/d/1_lx-LiYS4AytV7hDJnbslwkPSPZeEM-xFSGY0sgA5gs/edit?usp=sharing) I am using IMac mi 2011 with High Sierra 10.13.6 installed. Can anyone help? Thanks.
Upgrading Graphics.g4dn to GraphicsPro.g4dn fails with empty error message
I built a new Windows 10 Graphics.g4dn workspace, logged into it, and successfully installed and ran various software. After trying it out, I determined that I need more than 16GB of RAM for my task. The "Modify compute type" tab in the WorkSpaces console purports to let me upgrade the existing stopped instance to GraphicsPro.g4dn (64GB of RAM), but trying to save that change just gives me an empty error message of "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." There's no other context explaining what the problem might be. I did find [this support page](https://docs.aws.amazon.com/workspaces/latest/adminguide/modify-workspaces.html). It suggests that what I want to do is possible as long as the workspace is more than 6 hours old, which as of this morning this one is.