Browse through the questions and answers listed below or filter and sort to narrow down your results.
In workspace, to maintain the timezone as UTC across all workspaces. I created the GPO settings, suggested by the aws. but the gpo rule is applying on few workspaces but it is not working on others
to maintain the desired timezone as UTC across all workspaces. i created the gpo settings suggested by the aws (https://docs.aws.amazon.com/workspaces/latest/adminguide/group_policy.html). but the group policy is working for few workspaces. whereas, for few workspaces its not working. Any suggestions?
Mac Client USB Redirect
Im on a 13in 2020 macbook pro running BIg Sur. Currently using the AWS Workspaces Mac client (v.22.214.171.1248) to start a WIndows 10 streaming OS. Trying to figure out how to get the USB redirect to work for a security key when prompted for 2fa. Currently using a Thetis FIDO2 USB key. Do I need third party software to assist with the passthrough? I know this works when the Local OS hosting the Workspaces client is WIndows OS. Halp
In Appstream, Windows server 2019 base image is available with Office 365 ?
In workspace, windows base image is available with office 365. It reduces the license cost of office 365. would like to know is there is any such option available in appstream, like the windows base image preloaded with office365 ?
Clone a WS to Another Region
We have members that use multiple workspaces in N.Virginia (us-east-1) region. The base configuration includes Simple AD. Initially, workspaces were created in this region, yet staff can be working from other regions. This leads to performance/lag problems. I'd like to clone workspaces to other regions (both preserving the installed apps and user profile on D drive). I've followed the best practices to create an image. Image Checker did not report any problems. Then I used this image, and copied it to another region (Let's say eu-west-1). I created a new bundle with the image. So far no errors. Then, attempting to launch a new WS by using the bundle, I am prompted to create a new directory. If I create a new directory, I'm required to create a new user. (Because directories are different original user is not listed in Show All Users section). Upon launching the new WS using the settings above, indeed I see an emtpy/fresh Workspace with both installed apps lost and user profile does not retain changes in the image. Based on the info above, what could be wrong? Do I need to switch to Active Directory setup? Do we have to use external tools to make a true clone? Please kindly share your knowledge. Thank you for reading. If needed I can provide additional information.
Workspaces MFA setup problem
I am trying to configure Workspaces to use MFA. I have tried setting up MFA in the AD Connector area and then tried in the Workspaces Directory area (not at the same time). In both cases it goes from Creating to Failed. On the MFA server we see a request from our expected AWS external IP with user awsfaketestuser during the MFA creation. The security group used by AD connector has 1812 TCP/UDP allowed inbound and outbound is using a NAT gateway. As we see the request from AWS on our RADIUS server, we don't suspect a network problem. We have also tried creating a user on the RADIUS host called awsfaketestuser and setting it to disabled. I'm not sure how to get more information about the error or how to fix the problem.
How do I reverse Workspace disk performance from deteriorating?
I've had a workspace I've used for the better part of 5 years, and over time I've noticed the disk performance deteriorating to the point of being unusable. For example, I have a piece of software that starts up in 10s under normal disk performance, but has drifted out towards 2,000s because of disk performance being so slow! I'm using the Power Pro bundle AWS Workspace 2.3 GHZ 16GB Windows 10 VM with a 1TB encrypted user volume. When the workspace was new the disk performance was good roughly being comparable to my desktop. However, as time has gone on it has slowly degraded the point of of being unusable. My drives are currently 9% and 7% fragmented, but even after optimizing them it doesn't dramatically change the performance of the disks. I experience more frequent lockups where the client just freezes and doesn't repaint, but if I check my network connection it's sub 10ms which leads me to believe the disk is holding up the OS and the Amazon Workspace client is waiting on it to respond. What can be done to restore the performance back to what I had in the beginning?
Web Access AWS Workspaces Failing - ERR_SIG_TIMEOUT
Web Access AWS Workspaces Failing - ERR_SIG_TIMEOUT. Error An error occurred while connecting to your WorkSpace. If the problem persists please contact your WorkSpaces administrator. ERR_SIG_TIMEOUT I have no issues with the client, only with the web access option.
Workspaces - "An Error Has Occurred" - Message on the Top of my AWS Dashboard
Since the setup of the account a few months ago we have had the "An Error Has Occurred ... Contact Support etc..." error on the top of our AWS Dashboard whenever we go into Workspaces. Everything seems to work fine but we can never get this out of the way, i can close it but every time we log in the issue is there, i am not able to see any logs with errors or anything. We would appreciate your assistance on this issue.
Adding MFA to Workspaces "failed" problem
I have been attempting to add Mult-Factor Authentication to my workspaces account for my user base. I have configured the radius server using Free Radius from this post here: https://aws.amazon.com/blogs/desktop-and-application-streaming/integrating-freeradius-mfa-with-amazon-workspaces/ and all goes according to plan. I have the FreeRadius server using LinOTP running. The problem is in the very last step, when I go to enable MFA in workspace , I put in the information and it just says "failed". Specifically, Step 6: Enable MFA on your AWS Directory Communication between the AWS Managed Microsoft AD RADIUS client and your RADIUS server require you to configure AWS security groups that enable communication over port 1812. Edit your Virtual Private Cloud (VPC) security groups to enable communications over port 1812 between your AWS Directory Service IP end points and your RADIUS MFA server. Navigate to your Directory Service console Click the Directory you want to enable MFA on. Select Network & Security tab, scroll down to Multi-factor authentication, click Actions and Enable. In Enable multi-factor authentication (MFA) configure MFA settings: Display label: Example RADIUS server IP address(es): Private IP of the Amazon Linux 2 instance Port: 1812 Shared secret code: the one set in /etc/raddb/clients.conf Confirm shared secret code: as preceding Protocol: PAP Server timeout (in seconds): 30 Max retries: 3 This operation can take between 5-10mins to complete. Once the Radius status is “completed” you can test MFA authentication from the WorkSpace client. I really have two questions: 1. How do I do this part? Edit your Virtual Private Cloud (VPC) security groups to enable communications over port 1812 between your AWS Directory Service IP end points and your RADIUS MFA server. Maybe I'm not setting up the endpoints correctly ? Do I go to the VPC and add endpoints there? CAn you pleae be specific. 2. How do I get more information from just the "failed" in red --- how do I access the creation logs? Thanks in advance, Jon
How to find your organization and workmail users??
Normally, I know where to find the organization and also my workmail users... However, when I enter to the organization section, I do not have any organization created or on the workmail users any workmail users... This is weird, because our emails that are set up and host in AWS, are working properly... Does someone know what can be happening with my account??