Browse through the questions and answers listed below or filter and sort to narrow down your results.
Is there any workaround to imaging an encrypted workspace?
So I am new to AWS workspaces and I thought I was following security best practices by encrypting both the workspace volumes. However, the hope was that the work that went into configuring the workspace could be reutilized for imaging and other employees. I now realized that encrypted volumes cannot be imaged and I was hoping that someone might a solution or a work around? Is it possible to unencrypt the volumes? Could I migrate such an image to another service such as EC2 as a work around? II suspect that there is no solution and I will have to re-do the configuration in a non-encrypted volume, however I wanted to ask here, before I spend several more hours re-doing the work. Also it seems that this feature might be supported in the future. If so, does anyone know of any timeline of that possibility? Thank you for your time, Mz
Why is my WorkDocs storage smaller than the user volume of my Workspace?
I have a single Workspace with a single user. The Workspace has a root volume of 80GB and a user volume of 100GB. When I access the user volume through WorkDocs from my own computer not all the data appears. Under "My account" in the WorkDocs web view storage is listed as "50 GB of 50 GB used." In Windows Explorer the My Documents folder has 26.3 GB (?!) and Shared With Me has 0 GB. Why does WorkDocs not accommodate the full 100 GB and how can I make it so?
Enable BYOL for my account in Amazon WorkSpaces
Hello I want to use my own Windows 10 Professional license with Amazon WorkSpaces. I was going through [this documentation](https://docs.aws.amazon.com/workspaces/latest/adminguide/byol-windows-images.html?icmpid=docs_console_unmapped#windows_images_eligibility_byol), which says > To get started, contact your AWS account manager or sales representative, or contact the AWS Support Center. Your contact will verify your eligibility for BYOL. I do not have a sales representative and my Basic Support plan is not eligible for Technical Support. The billing team has suggested to communicate via this community channel so that someone from AWS team can help me in this regard. Can you please suggest how I can verify my eligibility and use my own Windows 10 Professional on Amazon WorkSpaces?
Program running on Workspace stops running when disconnected
I have an excel spreadsheet that collects data via a webservice and then saves it in an access database. The program is written in VBA. The program runs fine when I am connected to the workspaces session but appears to stop running when I am disconnected. It starts again when I reconnect. Workspace running mode is Always On Compute Type is Standard Hardware Power Option is set to High Performance I have rebooted the workspace and created a Custom Power Plan with the High Performance settings Does anyone know how I can get the program to continue running when I am not connected? Many Thanks Mike
Does Workspace use Internet from AWS or local Internet?
Greetings! Just started playing with Workspaces and I'm curious if the Internet in Workspaces is from my local ISP or from AWS? I noticed it has a different IP so not really sure. If I log in now, I can browse the Internet, but again not sure if it's using mine that I connect to or from AWS. I also have the running mode in "Autostop" but I want to change it to "Always On" with the expectation that I can log in from anywhere and see my desktop in the last state it was in using the same Internet. Any confirmation or clarification on this would be appreciated!
Workspace date & time whilst having the instance open
Hello. Having the Amazon Workspace application open on my running ( 24/7 ) machine, shows the right time in Excel formula =NOW(), however, if I do not have the application open, the time inside excel shows 1 hour behind, each time my script is running on the virtual machine, although the published sheets ( as html ) time save shows the right one. Any idea what's going on or why is this happening? Pictures attached to see the time when the script was running, what excel file shows inside of =NOW() and time & date of saved files from excel. ![Date & time showed in task scheduler](/media/postImages/original/IMXxYkV0HhQnqOavZSNnrIKg) ![Date & time showed in excel sheet with forumula =now() ](/media/postImages/original/IM1Mk9hwdVRnCkFG7SGwM7ew) ![Saved excel sheets as html date & time ](/media/postImages/original/IMnEIbL04CQoOIe41pnlbDhQ) Any help is appreciated! I need the time to show right even if I m logged in on my personal laptop to that application and if I m not.
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
Newest Amazon Workspaces app 126.96.36.19923 not keeping login name even after enabling "Keep me logged in"
Since the latest Amazon Workspace App for Windows 64bit 188.8.131.5223 update all of our users are prompted each time they login for Username and Password, it used to save the username but it is no longer.
Caps Lock and Num Lock keys not working in Workspace since 184.108.40.20623 update
Since the Workspace Client Update to version 220.127.116.1123 my num lock and caps lock keys on the keyboard are not working correctly in the workspace. They are opposite on the workspace and local machine. For example - I log onto my workspace with the num lock off and turn it on once I am on my workspace it will work on my workspace but be off on my local machine. If I enable it while working on an application on my local machine it will not work on an application on the workspace. The same thing with the CAPS Lock This is causing users to enter incorrect passwords and not be able to access their workspaces or applications and get locked out. Anyone else experience this since the most recent Workspace client update? We have clients running the older workspace client who do not have this issue.
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?
Workspaces RDP connection failure
I've signed up for the first time to AWS a few days ago. I have no knowledge regarding AWS. I've tried to connect to the Workspaces via the AWS free tier using this article - https://aws.amazon.com/premiumsupport/knowledge-center/connect-workspace-rdp/ It seems I've done everything well according to the article 1-7 steps, but I failed to understand how to configure according to the 8th step (the last one). The problem is that I fail to figure out which public IP should I set, and with which user should I sign in with via the RDP Iv'e tried to connect to the Workspaces Desktop via different RDP softwares, but all seemed to fail What should I do? How do I connect successfully via the RDP?
Need to login twice to Windows workspaces since update to client version 18.104.22.16823
Since we updated to the Workspaces client version 22.214.171.12423 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 126.96.36.19923 * 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.