1 Answer
- Newest
- Most votes
- Most comments
0
I assume you have gone through the steps listed in https://docs.aws.amazon.com/appstream2/latest/developerguide/troubleshooting-notification-codes.html for DOMAIN_JOIN_INTERNAL_SERVICE_ERROR
If not for the usual suspects as documented previously, this is likely due a Microsoft Security update. Please follow the guidance in the link here https://support.microsoft.com/en-gb/topic/kb5020276-netjoin-domain-join-hardening-changes-2b65a0f3-1f4c-42ef-ac0f-1caaf421baf8
If you are using Managed AD and cannot implement the suggestions in the link, i would suggest the following:
- Power down the fleet
- Delete all the Computer Objects in the AppStream OU.
- Power On the fleet and let the configured AppStram Service Account create objects. What this does is to satisfy the condition in the article "The user attempting the operation is the creator of the existing account" which will help mitigate this issue.
- Dont change the Service Account.
If the above doesnt work, please contact AWS Support
answered a year ago
Relevant content
- asked 2 years ago
- asked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 20 days ago