Forum Discussion
[Announcement] Connectivity issues from synchronized users to VMs joined to AAD DS
- Nov 04, 2019
Christian_Montoya : A fix has been rolled out to production for this issue.
CraigSmith87 : Where was that recommendation made (to not match your AAD tenant name)?
Christian_MontoyaThank you for the updates. Will there be any additional steps for us to perform if we already have the host pools with validation set to true? Hopefully your target of this month remains on track, I have 2 clients that I would like to migrate to WVD as it, at least from the outset, looks to out perform their existing Citrix environment and a much lower cost.
- Christian_MontoyaOct 14, 2019
Microsoft
No other steps will be necessary, aside from setting the pool to be a validation pool. I will keep you all updated on this thread.- jeffb8Oct 19, 2019Brass Contributor
I'm still encountering the issue. On 9/11, you wrote:
We've completed step #1 completely and #2 is what we're implementing/validating now. We expect this to complete and rollout within the next month.
So, we're 5 weeks out from there now and there is still no fix...and it seems like it's not even available in validation environments yet. Is this correct?
You also decided to go GA with a product that can't support basic usage (deleting a user account and recreating it...or just renaming a user)...
I would really like to understand what's going on here. Is there any update here?
- antonywmOct 23, 2019Copper Contributor
Hi,
would like to add to this thread. I also have deployed WVD in view of rolling it out for our business but when I try and add new user directly to AAD (we have no AADC sync) it is failing with error:
ErrorSource : RDBroker
ErrorOperation : OrchestrateSessionHost
ErrorCode : -2146233088
ErrorCodeSymbolic : ConnectionFailedUserSIDInformationMismatch
ErrorMessage : User xxx@xxx.net: SID information in the database 'S-1-5-21-1382006385-1486747441-1399156625-1111' does not match SID information returned
by agent 'S-1-5-21-1382006385-1486747441-1399156625-1129' in the orchestration reply.. This scenario is not supported - we will not be able
to redirect the user session.
ErrorInternal : False
ReportedBy : RDGateway
Time : 23/10/2019 12:48:50Christian_Montoya: Would appreciate idea of when this will be fixed. Like jeffb8 and others, I've tried everything (even deleting, adding user) but nothing works.