Home

WVD after re-installing AAD DS

%3CLINGO-SUB%20id%3D%22lingo-sub-781280%22%20slang%3D%22en-US%22%3EWVD%20after%20re-installing%20AAD%20DS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-781280%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20the%20following%20situation%3A%20I%20only%20use%20AAD%20DS%20without%20any%20classical%20AD%20involved.%20I%20can%20set%20up%20WVD%20just%20fine%20but%20when%20I%20delete%20everything%20(AAD%20DS%2C%20WVD%20host%20pool%2C%20and%20WVD%20tenant)%20and%20start%20all%20over%20again%2C%20users%20that%20have%20been%20in%20the%20old%20AAD%20DS%20can%20no%20longer%20connect%20to%20WVD%20with%20the%20problem%20of%20having%20a%20different%20SID%20(see%20below).%20This%20is%20probably%20related%20to%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FWindows-Virtual-Desktop%2FAnnouncement-Connectivity-issues-from-synchronized-users-to-VMs%2Ftd-p%2F759642%22%20target%3D%22_self%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FWindows-Virtual-Desktop%2FAnnouncement-Connectivity-issues-from-synchronized-users-to-VMs%2Ftd-p%2F759642%3C%2FA%3Ebut%20not%20the%20same.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20a%20way%20to%20get%20these%20users%20to%20work%20again%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-markup%22%3E%3CCODE%3EErrorSource%20%20%20%20%20%20%20%3A%20RDBroker%0AErrorOperation%20%20%20%20%3A%20OrchestrateSessionHost%0AErrorCode%20%20%20%20%20%20%20%20%20%3A%20-2146233088%0AErrorCodeSymbolic%20%3A%20ConnectionFailedUserSIDInformationMismatch%0AErrorMessage%20%20%20%20%20%20%3A%20OrchestrateAsync%3A%20SID%20value%20in%20the%20database%20is%20different%20than%20the%20value%20returned%20in%20the%20orchestration%20reply%20from%20the%20agent%20for%20user%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%E2%89%A4XXXXX%40YYYYY%E2%89%A5%20with%20Id%20ZZZZZZ.%20This%20scenario%20is%20not%20supported%20-%20we%20will%20not%20be%20able%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20to%20redirect%20the%20user%20session.%0AErrorInternal%20%20%20%20%20%3A%20False%0AReportedBy%20%20%20%20%20%20%20%20%3A%20RDGateway%0ATime%20%20%20%20%20%20%20%20%20%20%20%20%20%20%3A%207%2F31%2F2019%201%3A54%3A33%20PM%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1083896%22%20slang%3D%22en-US%22%3ERe%3A%20WVD%20after%20re-installing%20AAD%20DS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1083896%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F384910%22%20target%3D%22_blank%22%3E%40ChristophB%3C%2FA%3E%26nbsp%3B%3A%20This%20should%20be%20working%20again%2C%20as%20of%20October.%20Are%20you%20back%20up%20and%20running%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1119670%22%20slang%3D%22en-US%22%3ERe%3A%20WVD%20after%20re-installing%20AAD%20DS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1119670%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F305776%22%20target%3D%22_blank%22%3E%40christianmontoya%3C%2FA%3E%26nbsp%3B%20Thanks%20for%20asking.%20Yes%2C%20it%20appears%20to%20work%20now%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
ChristophB
New Contributor

I have the following situation: I only use AAD DS without any classical AD involved. I can set up WVD just fine but when I delete everything (AAD DS, WVD host pool, and WVD tenant) and start all over again, users that have been in the old AAD DS can no longer connect to WVD with the problem of having a different SID (see below). This is probably related to https://techcommunity.microsoft.com/t5/Windows-Virtual-Desktop/Announcement-Connectivity-issues-from... but not the same.

 

Is there a way to get these users to work again? 

 

ErrorSource       : RDBroker
ErrorOperation    : OrchestrateSessionHost
ErrorCode         : -2146233088
ErrorCodeSymbolic : ConnectionFailedUserSIDInformationMismatch
ErrorMessage      : OrchestrateAsync: SID value in the database is different than the value returned in the orchestration reply from the agent for user
                    ≤XXXXX@YYYYY≥ with Id ZZZZZZ. This scenario is not supported - we will not be able
                    to redirect the user session.
ErrorInternal     : False
ReportedBy        : RDGateway
Time              : 7/31/2019 1:54:33 PM

  

2 Replies

@ChristophB : This should be working again, as of October. Are you back up and running?

@christianmontoya  Thanks for asking. Yes, it appears to work now