Questions tagged with End User Computing
Content language: English
Sort by most recent
Browse through the questions and answers listed below or filter and sort to narrow down your results.
We recently rolled out 50 WorkSpaces to a division of the company and when things are all working properly, things work great!
However, when there are issues, we struggle so I'm here looking for some best practices.
Due to corporate policies, we only run the WorkSpaces Web Client. The native clients aren't allowed on our corporate machines...
Our most common issue is at the start of the day a user will log in to the web client, their machine will start up (I can verify this at the console) but they'll just go to a spinning "connecting" page forever. There's no apparent reason why. We try a variety of things, but I'm never sure what actually solves the issue:
* Close the browser tab, then close the browser.
* Re-open the browser, try again.
* No luck? Clear cache/cookies in the browser, try again.
* Try another browser!
* Still no luck? Stop the WorkSpaces machine via the AWS console, try again
At some point in this dance, things usually work. And I should be clear. For all users, we're in great shape over 95% of the time. There's no consistency in anyone person having more issues than any other.
What else should we be trying? There's precious little info in the console so we're sort of flying blind here.
This weekend we had an issue where NOBODY could connect. This morning still nobody could connect (35 people all over the city/country). Support, of course, wanted to zero in on one random machine and get network logs from it. We'll never know what the issue was because at 7:30 AM all of the sudden EVERYONE connected. Lol. How do you root cause analyze that? ;-)
I'm investigating a similar approach to [this question](https://repost.aws/questions/QUzVkaMfAfTkO5jXoOWocJnw/app-stream-2-0-with-database-users) on using a custom IdP / authentication process. One thing that isn't clear from the docs is whether the [CreateStreamingURL](https://docs.aws.amazon.com/cli/latest/reference/appstream/create-streaming-url.html) flag for the UserID also propagates through to the persistent storage via S3.
The workflow that I would like is:
1. User logs into my application, and permissions are checked. All authn/authz logic contained here.
2. Application uses an AWS service account to call CreateStreamingURL, with e.g. UserID=user1@example.com and UserID=user2@example.com .
3. Application gives user1 -> url1 and user2 -> url2, such that these sessions are isolated.
4. Next day, user1 logs in again and gets url1_new, and should be able to see whatever settings / persistence as per the previous session.
Is my understanding of the UserID parameter correct?
My customer have the issue with the SSO integration of AppStream2.0 with ADFS. We followed step by step the guide indicated at the following link : https://aws.amazon.com/it/blogs/compute/enabling-identity-federation-with-ad-fs-3-0-and-amazon-appstream-2-0/ with correct settings for ADFS 4.0. However after the user login to ADFS portal, it's always landed in AWS console, not the Appstream 2.0 stack apps catalog. When the user access RelayStateURL directly, it does go to AppStream 2.0 stack apps catalog.
Did anyone encounter the similar issue. Any suggestion what's the cause and how to fix it? Thanks
asked 5 months ago
Good evening to all, when I edit an xml configuration file under path **C:\appname** during the session, when I disconnect this change is lost even if I have enabled in the stack the **application persistance setting** and the **home folder S3** in storage.
Do you have any advice? Thank you!!
Is it possible to have different login URLs for different IAM users or for different stacks of the same root account?
e.g.
user IAM 1 -> linkA
userIAM2 -> linkB
or
Stack1 -> linkA
Stack2 ->linkB
what I need is: to deploy an application with different settings for different end-users, if possible with different login links.
Then give the user a chance to see their stack and fleet belong.
Do you have any suggestions on how to do that?
Thanks in advance.
We have a number of fleets already set up and those are working fine but one of the newer fleets that I have created has an issue when new users try to launch and log into Appstream instances that belong to the said fleet. The password that is used is correct but they sometimes get an incorrect password error and then it pops up "An unknown error occurred (1909)". The strange part about it all is that I encountered a similar problem when I first launched and logged in to an instance on the fleet. It took about four or five attempts before it worked. Since that successful sign in, I only encounter the above error occasionally but it works most of the time. Unfortunately, the same doesn't seem to be happening for the newer users that have been assigned access to it.
So my questions are, why is this happening in the first place and why is it allowing few users that have signed in previously but none of the new users?
FYI, we use Okta as our identity provider.
Any advice you may be able to provide would be most appreciated.
Thanks and regards,
Diem
Under the outbreak of COVID19, we are encouraging work from home model. We are migrating the intranet web servers, and application servers to the AWS EC2. For best protection, I would like to know if there is any solution for WFH user to have remote access (such as VPN) to AWS? If possible, is there any AWS native remote access VPN available rather then using third party Cloud base Firewall?
I created a Dash application that has been deployed to AWS Elastic Beanstalk. The application relies on the user uploading an Excel sheet to get the desired output.
In another Dash application I created previously, there were no problems while uploading the Excel sheet. This time around, I keep getting a PermissionError(13, 'Permission Denied') message.
The platform for my Dash applications are Python. Unfortunately, I haven't been able to see anyone else facing the same problem too.
Just for reference, the value of the PYTHONPATH environment property is "/var/app/venv/staging-LQM1lest/bin".
Moreover, I am using the EB management console and not the CLI.
Any tips on how to solve the problem would be much appreciated.
Thanks.
Hello, I have been experimenting with Workspaces and created an AD connector and an EC2 instance as a Domain controller. The EC2 instance got deleted by mistake and this moved the AD connector to the "Inoperable" state. I cannot delete the AD connector now and when I try, it gives the message "On-premises issue(s) detected by instance 10.101.1.138: Unable to reach DNS port (TCP 53) of on-premises server 10.101.0.37. On-premises issue(s) detected by instance 10.101.2.164: Unable to reach DNS port (TCP 53) of on-premises server 10.101.0.37. How can I delete this AD connector? This was all created via terraform and I am now stuck. Please advise.
I have experimented with the [NICE DCV connection gateway and session manager](https://docs.aws.amazon.com/dcv/index.html). The last step of connecting with a DCV client through the gateway is not working as I thought it should work. The gateway always tries to load web assets from a 'web resources' url, but I am not using a browser to connect. Leaving out the 'web resources' from the gateway configuration is not possible, it won't start without it. I have described my setup and configuration steps [here](http://blog.joustie.nl/images/2022/01/architecture.drawio.png)
Any idea where to look?
Hi, does anyone know of an existing issue with MBP14 M1Pro laptops and AWS Workspaces? If I do the AWS WS app to the full screen, I'm losing part of the upper menu - i.e. MS Outlook search bar not visible, Google Chrome, FF tabs above the address bar aren't visible. Is there a workaround to get rid of it? I already tried to set "scale to fit below built-in camera" - didn't help either.
Thanks for thoughts
I create a virtual machine in Amazon Work Spaces, and I want to send local files to Amazon Work Spaces.
So, I use Work Docs and upload to there, but there have some Time-lag between time when I uploaded and time when I can see file in Amazon Work Spaces. (Time-lag is about few minutes)
Is that behavior happened only my environment?
Is there any way to shorten Time-lag?