Existing AWS Workspace Personal Image deployed to Pooled

It sounds like you're experiencing an issue with your custom WorkSpaces Personal image when deploying it to WorkSpaces Pools. This problem, where users can connect via RDP but not through the WorkSpaces client, suggests there might be a configuration issue specific to the WorkSpaces streaming protocol (WSP) or the image itself.

Here are some steps you can take to troubleshoot and potentially resolve the issue:

1. Ensure that your custom image is fully compatible with WorkSpaces Pools. WorkSpaces Pools requires the use of the WSP 2.0 protocol. Double-check that your image is configured to use WSP 2.0.

2. Review the image creation process. When creating a custom image for Pools, make sure you've followed all the necessary steps, including any required updates or configurations specific to Pools.

3. Check for any recent changes or updates made to the image that might interfere with the WorkSpaces client connection. Sometimes, security software, group policies, or system configurations can cause issues with the final connection step.

4. Enable advanced logging on the WorkSpaces clients to generate diagnostic logs. These logs can provide more detailed information about why the connection is failing at the last step.

5. Verify that all necessary components for WorkSpaces Pools are present in your image. There might be specific components or configurations that Pools requires which are not present in your Personal WorkSpaces image.

6. Consider creating a new image based on a standard WorkSpaces image known to work with Pools, then gradually add your customizations. This can help isolate whether the issue is with your specific customizations or the base image itself.

7. If the issue persists, you may need to collect client and bundle logs and open a support case with AWS. They can provide more specific guidance based on the logs and your particular setup.

Remember that while Personal WorkSpaces and Pooled WorkSpaces share many similarities, there might be subtle differences in how they handle certain configurations. It's possible that an optimization or setting that works well for Personal WorkSpaces might need adjustment for Pools.

If you continue to face difficulties, it might be worth creating a fresh custom image specifically for Pools, ensuring all Pools-specific requirements are met during the image creation process.

Sources
Troubleshoot WorkSpaces performance issues | AWS re:Post
Troubleshoot issues for WorkSpaces Personal - Amazon WorkSpaces
Update a custom bundle for WorkSpaces Personal - Amazon WorkSpaces
Amazon WorkSpaces Pools: Cost-effective, non-persistent virtual desktops | AWS News Blog

Here are some steps you can take to troubleshoot and potentially resolve the issue: Ensure that your custom image is fully compatible with WorkSpaces Pools. WorkSpaces Pools requires the use of the WSP 2.0 protocol. Double-check that your image is configured to use WSP 2.0.

How?