By using AWS re:Post, you agree to the Terms of Use
/End User Computing/

End User Computing

AWS End User Computing (EUC) services provide secure access to the applications and desktops the workforce needs to get their job done. With AWS EUC services, workers can be productive from any supported device while improving IT agility and organizational security. You can scale up or scale down resources on demand, providing your teams with the resources they need, all without deploying and operating infrastructure.

Recent questions

see all
1/18
2
answers
0
votes
16
views
asked 4 days ago

Amazon Workspaces 5.0 Client issues?

Our organization has recently started deploying the 5.0 release of the Amazon Workspaces Desktop Client (specifically the Windows version, and most if not all of the Workspaces are running on PCoIP, in case it is relevant). Since doing so, we have noticed an increase in users having issues with their USB devices functioning properly in Amazon Workspaces. This primarily is manifesting as issues where their USB headsets will not be recognized after only a few minutes into their session, but we have been noticing it is causing strange issues with users' keyboards as well where the Caps Lock and Num Lock will not behave as expected inside of Amazon Workspaces despite working just fine on the host PC. The keyboard issue has only started cropping up in any sort of noticeable numbers since the 5.0 client has begun deployment in our organization earlier this month. The headset issues are something that we are used to seeing, but have historically been able to resolve with standard troubleshooting methods such as adjusting the audio settings on the host PC, making sure that the user is not muted inside or outside of Amazon Workspaces, repairing the client and driver installations, restarting the Windows Audio Service inside and outside of Amazon Workspaces, rebooting the workspace and/or local PC, etc. Typically, if those steps don't resolve the issue, we can point to a user's slow or unstable internet connection as a likely culprit or narrow it down to a hardware issue with the headset or PC. Since we started deploying the 5.0 Amazon Workspaces client, however, we have seen many more users having issues with their headset dropping out and not being recognized by the workspace client despite us replacing the hardware and confirming that they have exceptional internet speeds. We are starting to roll back users who have issues to the last stable build as a short-term fix, but I haven't seen much being mentioned about this outside of my IT organization and was wondering if others have noticed the same issues? There seem to be some bugs with the USB handling in this release based on the way the problems are manifesting.
1
answers
0
votes
15
views
asked 4 days ago

Appstream Elastic Fleet - Application Not Launching

I have an application being deployed on the "Microsoft Windows Server 2019 Base" platform as an Elastic Fleet deployment. Unfortunately, the application does not launch, it just gives a black screen. I have confirmed that the VHD, deployment script, and icon file are all accessible to the instance from S3. I did this by launching as a Desktop Stream View and downloading the files via S3 pre-signed URL and the file did download. What is odd, is that when I launch the fleet in Desktop-Stream-View, and then click on "Desktop" it takes me to the Windows desktop and I can see the VHD mounted both on the folder path and as a drive. I can navigate to the executable and launch it. But while in this view, if I click on the "4 boxes" icon on the top-left and try to launch my application from it's AppStream catalog link, nothing happens. After logging out and then back in, while still in Desktop-Stream-View, I then clicked directly on the app's AppStream catalog icon (not the "Desktop" icon). It still takes me to the Windows desktop, but the VHD is not mounted! Naturally, the app link in the "4 boxes" icon to load the Catalog still does not work. Now, when launching the fleet in "App-Stream-View", I only get the AppStream catalog icon, so I click on it and it just loads to a black screen, probably since it did not load the VHD nor set everything up. I cannot understand why I can see the mounted VHD and my application files in one instance but not in the other. And no setup has a working AppStream catalog link. Here are my relevant customizations to the "mount-vhd.ps1" script ``` # Specify a folder path to mount to. When specified, the script will check to see if the folder exists, and is empty, before mounting. If the folder doesn't exist, the folder will be created. If the folder exists, and isn't empty, the folder mounting will fail. $MountFolder = "C:\myApps" # Specify a drive letter to mount to. Specify the colon after specifying the drive letter. Note: A-E are reserved for AppStream 2.0. You will need to choose a different drive letter. $MountDriveLetter = "F:" #If $PathToVHD isn't specified, the script will automatically search for the VHDX file in the same directory to mount. $PathToVHD = "" ``` For the "Application" setup, I have the following: Application executable launch path: C:\myApps\TestApp\TestApp.exe Application working directory: C:\myApps\TestApp\ Any assistance would be greatly appreciated, thank you!
2
answers
0
votes
41
views
asked 18 days ago

AWS Workspaces: Problem that uploaded package doesn't appear on validation instance

Hello, I created a new packaging instance to build a new version of my application that I want to deploy (as I always did). I used the Amazon WorkSpaces Application Manager Studio, chose my application and clicked "Update". After my changes I used "Upload". After uploading the status of my application version on "Dashboard" becomes "Upload complete". Then I started my EC2 validation instance and connected to it. In the Amazon WorkSpaces Application Manager I went to "Pending Apps" and clicked "Refresh" but my new version didn't appear. I waited now for more than 1,5 hours and it's still not visible. In my packaging instance I checked the log files but the last steps seemed to be successful: ``` 2022-05-30 07.06.51.944 Info: Writing final package data... 2022-05-30 07.06.51.944 Info: Packaging application... 2022-05-30 07.06.52.382 Info: Writing project file "C:\Users\ADMINI~1\AppData\Local\Temp\2\EBC567BD-A637-4603-AF2C-31D1D7837E4A_15.stw" 2022-05-30 07.06.52.382 Info: Done writing project file "C:\Users\ADMINI~1\AppData\Local\Temp\2\EBC567BD-A637-4603-AF2C-31D1D7837E4A_15.stw" 2022-05-30 07.06.55.415 Info: Done patching in 4.2s 2022-05-30 07.06.55.462 Info: Successfully created package. 2022-05-30 07.06.55.462 Info: Successfully created package. ``` For testing I created another new packaging instance, chose my application in the Amazon WorkSpaces Application Manager Studio and create "Update". I got the following error message: ``` Failed to extract application from the specified appset. Appset file might be invalid. ``` So what went wrong and what can I do to continue? Do you need further information to help me? Thanks a lot in advance, Michaela
1
answers
0
votes
15
views
asked a month ago

Popular users

see all
1/18