Forum Discussion
We couldn't connect to the gateway because of an error
ian11230 If you're using Azure Active Directory Domain Services, you need to make sure the deployed servers are in the "AADDC Computers" OU and you log in using an admin account that is in the "AADDC Users" OU. Make sure the admin user is a member of the "AAD DC Administrators" group in Azure Active Directory.
When I did this, I was finally able to Remote Desktop directly into the deployed VM's in the hostgroup.
HIian11230
I had the same problem, and to solve it I raise the word complix
As a :
o minimum length 12 characters
o Capital letters of European languages (A to Z, with diacritics, Greek and Cyrillic characters)
o Tiny letters from European languages (a to z, sharp-s, with diacritics, Greek and Cyrillic characters)
o Figures in base 10 (0 to 9)
o Non-alphanumeric characters (special characters): (~! @ # $% ^ & * _- + = '| \ () {} \ [] :; »» <>,.? /) currency symbols such as l Euro or a British pound are not considered special characters for this policy setting.
o The password should not be in a dictionary (dictionary attack)
o The password should not be a subject known as Christmas, Easter, Carnival, etc.
You mean raise the password complexity yeah? Cause both my test account and the account I used for the UPN have the same password and it is over 12 characters and does contain a + but azure never complained about it while making the WVD.
Hello,
Is there any new info regarding this issue? Or increasing password complexity is solution?
Regards,
- Changing the password complexity did not help.
