Forum Discussion
Azure Virtual Desktop Login Error Code 0x3000047
Hi We have been facing issues with logon to Azure Virtual Desktop Windows machine for couple of users in Personal Hostpool. Users get error when logging on using RDP Client app or the Web Clien...
.png){kind=link}
This has become really annoying now. I have a personal hostpool of 15 users. Every other day I have users complaining of not able to connect and seeing this error.
I have verified the UPNs for all users on AD DS and AAD all good, no Sync issues between DCs. Nothing useful that points to the cause of error in Diagnostics logs.
The only workaround is to RDP to the session host using local admin account and re-join it to Domain.
We have Start VM on Connect implemented for the Hostpool, for past 1 week we haven't shutdown VMs to make sure this login error does not disrupt user work every morning.
Today we shutdown VM to test if this has resolved/changed, but to our disappointment, Error 0x3000047 is back again both for web or RDP client app.
Adding 15 users to Domain everytime we shutdown VM is not a feasible option. Can someone please suggest what can we do to fix it? Or what we are doing wrong?
We have two other Hostpools in same Domain, which work fine with no issues.
Also to rule out if there was a configuration error we have scrapped the hostpool twice now.
Thanks
Kanishka
I have verified the UPNs for all users on AD DS and AAD all good, no Sync issues between DCs. Nothing useful that points to the cause of error in Diagnostics logs.
The only workaround is to RDP to the session host using local admin account and re-join it to Domain.
We have Start VM on Connect implemented for the Hostpool, for past 1 week we haven't shutdown VMs to make sure this login error does not disrupt user work every morning.
Today we shutdown VM to test if this has resolved/changed, but to our disappointment, Error 0x3000047 is back again both for web or RDP client app.
Adding 15 users to Domain everytime we shutdown VM is not a feasible option. Can someone please suggest what can we do to fix it? Or what we are doing wrong?
We have two other Hostpools in same Domain, which work fine with no issues.
Also to rule out if there was a configuration error we have scrapped the hostpool twice now.
Thanks
Kanishka