Questions in 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.

Appstream 2.0 Mac Microphone Crashes Appstream Connection and does not Work

We have been serving our application (which requires user microphone input) on appstream 2.0 for roughly a year now with few issues. However, at the beginning of November, Mac users began reporting microphone input had stopped functioning in appstream. Our build of our application and our setup in appstream has not changed. Upon testing, we discovered the following issues on Mac (Chrome and Firefox): In both imagebuilder and normal appstream access via user setup- **After enabling microphone(via settings in upper left), the input seems to be registered in Windows sound settings for a moment, then stops showing. Then the VM or Streaming performance rapidly degrades (laggier and laggier input) until finally the instance freezes. Eventually the screen shows the connecting swirl with "Reconnecting to your session…", and after a few seconds the Appstream instance re-appears *with top left Microphone disabled* and the Appstream functioning as normal.** This has been tested across 5 Macs running the latest Apple update. Our image/imagebuilder is running with the following specs: * Microsoft Windows Server 2019 Base * AppStream 2.0 agent version 10-13-2022 * Graphics design XL instance type We also tested a ‘general purpose XL’ instance type imagebuilder and received the same results. Is anyone having similar issues/does anyone know of a fix? Is this a known bug due to an apple update or otherwise?
0
answers
0
votes
8
views
Avi
asked 2 days ago

Amazon WorkSpaces and Trouble Shooting

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? ;-)
1
answers
0
votes
12
views
CKas10
asked 3 days ago

Why AWS is not allowing us to receive client inquiries on our website through emails?

We have recently migrated to AWS from the previous hosting provider. However, since then we have stooped receiving client inquiries put on our website, in the form of emails which we used to get seamlessly earlier. We tried to contact them but were asked to pay for any technical support, so we did. We requested them to enable port 25 and they asked few questions like use-case for sending mail from EC2 and spam prevention mechanisms. After successfully answering both the questions, they said "We have lifted the restriction for your account in the following > region(s): ap-south-1" - we didn't understand what it is. So check if the email function is working. But it wasn't. Therefore, we wore back to them saying that it is still not working. To our surprise, they sent us this "After a thorough review, we confirmed our original finding and cannot grant your request. Please consider looking into the Simple Email Service (SES). We cannot assist you further with this issue and we may not respond to additional messages on this subject" Since then, they are not responding. We are still wondering how can they deny helping us sort out the issue or at least explain properly why certain things are not feasible at their end. It is totally unacceptable to bound customers to keep purchasing additional services by sending such rude emails and poor customer support. Inquiry [xxxxxxx] *Edit: Removed AWS Account ID - Ben G.
1
answers
0
votes
28
views
asked 5 days ago