- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
Thank you so much arun, your suggestions helped me: restore didn't work, putting the Workspace in Unhealthy state. Tried to connect, reboot, RDP, no luck. Finally, a rebuild solved my issue.
I don't get why this happened, I use the Workspace few hours per week and without changing anything on its configuration. As a matter of fact, the service looks unstable by itself.
Thank you again.
There is official guidance for such issues. https://aws.amazon.com/premiumsupport/knowledge-center/workspaces-stuck-status https://youtu.be/3m9tl0v579o
If the above steps do not work(as your RDP is inaccessible), I would usually ask to open a Support Case but in your case, that is not applicable.
So, if your WorkSpace can afford lose data up to 12 hours, i will use try Restore and if that doesnt work, I will try a Rebuild. https://docs.aws.amazon.com/workspaces/latest/adminguide/restore-workspace.html https://docs.aws.amazon.com/workspaces/latest/adminguide/rebuild-workspace.html
Hope it helps,
-arun.
Same thing happen with me from last two days when i tried to connect my AWS Workspace it show in starting state for 1 hour or so and end with unhealthy state after that i reboot and i was able to connect it. But not yet got any permanent solution for this issue. If anyone have fix for this please share it with us....thanks in advance.
Sorry to hear about your experience. This is more an exception in my experience. Usually what gets a Windows machine stuck are pending updates, misbehaving applications or the OS waiting for something to complete. Hopefully you could identify the root of the problem.