[UPN] UPN (user@domain.) format should work
Local users and groups management should allow adding user by their UPN logon name - Currently seems to require pre-Windows 2000 DOMAIN\username
Karl Fasick
shared this idea
9 comments
-
Dusty
commented
Confirmed that issue persists in WAC version 1910.
-
Dusty
commented
Issue confirmed in WAC version 1910
-
Gustavo Verduzco
commented
Windows Admin Center is currently having issues validating credentials when UPN is used to add a server to WAC. If my forest name is corp.america.mydomain.com but my UPN has been set as username@mydomain.com WAC will give me an access denied error when trying to authenticate against that machine with those credentials. WAC will only accept the credentials if I use username@corp.america.mydomain.com or DOMAIN\username. WinRM authenticates fine via Kerberos with either format, so, it is a problem with WAC parsing credentials using UPN format.
-
Anonymous
commented
I found out the same thing today, too.
-
Eric
commented
This Issue should be combined with https://windowsserver.uservoice.com/forums/295071-management-tools/suggestions/36005389--bug-bug-powershell-when-logon-upn-is-used
-
Eric
commented
Yes, I have this issue on my install too.
-
Vecteur IT
commented
If you are logged with UPN (for exemple administrator@domain.local) and you try to launch PowerShell console, you are disconnected.
WAC try to authenticate with .\administrator@domain.local -
Anton Zimin
commented
If I use user@domain credentials, PowerShell and RDP do not work. They work with domain\user only.
-
D. Müller
commented
When manage as credentials as given as UPN (user@dom.loc) the powershell Login always gets an error. the wrong userlogon is used. It tries .\user@dom.loc.
If managed by credentials are dom\user the powershell Login works