1 Answer
- Newest
- Most votes
- Most comments
1
Please create a support case so AWS can resolve this for you. A support engineer will be able to comb through the logs and pinpoint the exact issue.
Relevant content
- Accepted Answerasked 4 months ago
- asked 2 years ago
AWS OFFICIALUpdated 2 years ago- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
I only have Basic support for my non-profit organization using Workspaces. We can't afford the support fees.
That is why I posted in re:Post instead of just opening a trouble ticket.
@CBaker007 due to the nature of the issue it will be hard to solve it without seeing the logs from the WorkSpaces side. An alternative would be to rebuild the workspace https://docs.aws.amazon.com/workspaces/latest/adminguide/rebuild-workspace.html however if you have installed or made modifications to the C: drive of the WorkSpace, rebuilding will remove them, as it will use the C: drive that is part of the bundle. You can also create a brand new workspace, install your applications on it, create a new image and bundle, and then use the migration feature https://docs.aws.amazon.com/workspaces/latest/adminguide/migrate-workspaces.html which would migrate the user data (D: volume) to the new bundle (C: volume).
The final alternative would be if you are currently using a pcoip based workspace. In this case, you can switch the protocol to the new WSP protocol https://docs.aws.amazon.com/workspaces/latest/adminguide/modify-workspaces.html and see if you are able to connect to it that way. This operation is reversible