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 all1/18
1
answers
0
votes
3
views
asked 4 hours ago
1
answers
0
votes
14
views
asked 7 days ago
2
answers
0
votes
33
views
asked 16 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!
Accepted AnswerAmazon AppStream
2
answers
0
votes
41
views
asked 18 days ago
AWS Workspace Image and bundle creation - original workspace question
Dumb Question: Once you create an image and a bundle from a workspace, can you safely delete that original workspace without affecting the image and bundle you created?
Accepted AnswerAmazon WorkSpaces
2
answers
0
votes
23
views
asked 21 days ago
Popular users
see all1/18