Forum Discussion
Error code 0x3000047 for one of the VM -Users not able to connect VDI Session Host
Hi , Last week we had some issues reported by VDI Users ,they got 0x3000047 message and not able to start any of the session host ,we have VM connect enabled in host pool ,while analysing we ha...
Thanks for the tips.
This is really a bit of a mystery occurrence, however.
Tried various fixes suggested from Microsoft forums and from other sites, including this registry fixes that worked for a couple (on top of removing it from host pool, rejoin domain, uninstalled all RDAgents software, re-register with new token, etc.), but then it does not for a few others. But then next day or so, things are ok again without any other fixes added. Would really love to know the root cause of this to better support the mass audience.
This is really a bit of a mystery occurrence, however.
Tried various fixes suggested from Microsoft forums and from other sites, including this registry fixes that worked for a couple (on top of removing it from host pool, rejoin domain, uninstalled all RDAgents software, re-register with new token, etc.), but then it does not for a few others. But then next day or so, things are ok again without any other fixes added. Would really love to know the root cause of this to better support the mass audience.
Hey Vu_Hoang. What was the root cause and the solution?
Hi, karthik1012
Apologies, i missed this message..
But the fix was that we found the legacy domain (post-migration) was still associated with the tenant/subscription for authentication. Once all strings-attached (with the legacy domain name) has removed (with the help from server team), the VMs were able to authenticate properly with the new domain now.
Key is to check from server side (domain controller), to ensure that nothing is tying with the legacy domain (especially, there's a change in domain name (e.g., post-migration). Look into domain trust config in Azure side, DNS server config/records, to remove all legacy domain name as needed.
