Your credentials didn’t work—try again

%3CLINGO-SUB%20id%3D%22lingo-sub-2091578%22%20slang%3D%22en-US%22%3EYour%20credentials%20didn%E2%80%99t%20work%E2%80%94try%20again%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2091578%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20installed%20this%20week%20Windows%20Admin%20Center%20for%20first%20time.%20I%20managed%20successfully%20to%20control%20Windows%20Server%202016.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%20now%20I%20am%20trying%20to%20add%20on-premise%20Windows%2010%20machine%20without%20success.%3C%2FP%3E%3CP%3EI%20am%20using%20%22Manage%20as%22%20feature%20by%20typing%20machine%20user%20and%20password.%20Results%20into%20following%20error%20%22%3CSPAN%3EYour%20credentials%20didn%E2%80%99t%20work%E2%80%94try%20again%22.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20did%20some%20search%20on%20google.%20Unfortunately%20I%20cant%20resolve%20it%20on%20my%20own.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EWhat%20I%20did%3A%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E-%26nbsp%3B%3CSTRONG%3EEnable-PSRemoting%20-force%3C%2FSTRONG%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E--%20this%20returned%20me%20an%20error%20about%20firewall%20unable%20to%20determine%20if%20there%20is%20valid%20entry..%20so%20I%20added%20manually%20inbound%2Foutbound%205985%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E-%20winrm%20service%20is%20on%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E-%20network%3A%20private%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E-%20not%20domain%20joined!%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E-%20%3CSTRONG%3ETest-WSMan%3C%2FSTRONG%3E%20success%20even%20from%20remote%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E-%26nbsp%3B%3CSTRONG%3EGet-Item%20WSMan%3A%5Clocalhost%5CClient%5CTrustedHosts%3C%2FSTRONG%3E%20returns%20my%20remote%20ip%20address%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EWhat%20should%20I%20try%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThanks%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EEDIT%3A%20Chrome%20devtools%20requests%20show%20me%20detailed%20errors%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E1)%26nbsp%3BThe%20WS-Management%20service%20cannot%20process%20the%20request.%20The%20WMI%20service%20returned%20an%20'access%20denied'%20error.%20hResult%20-2146233088%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E2)%26nbsp%3BConnecting%20to%20remote%20server%20x.x.x.x%20failed%20with%20the%20following%20error%20message%20%3A%20The%20WS-Management%20service%20cannot%20process%20the%20request.%20Cannot%20find%20the%20microsoft.sme.powershell%20session%20configuration%20in%20the%20WSMan%3A%20drive%20on%20the%20x.x.x.x%20computer.%20For%20more%20information%2C%20see%20the%20about_Remote_Troubleshooting%20Help%20topic%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

Hi,

 

I installed this week Windows Admin Center for first time. I managed successfully to control Windows Server 2016.

 

However now I am trying to add on-premise Windows 10 machine without success.

I am using "Manage as" feature by typing machine user and password. Results into following error "Your credentials didn’t work—try again".

 

I did some search on google. Unfortunately I cant resolve it on my own.

 

What I did:

Enable-PSRemoting -force

-- this returned me an error about firewall unable to determine if there is valid entry.. so I added manually inbound/outbound 5985

- winrm service is on

- network: private

- not domain joined!

- Test-WSMan success even from remote

Get-Item WSMan:\localhost\Client\TrustedHosts returns my remote ip address

 

What should I try?

 

Thanks

 

EDIT: Chrome devtools requests show me detailed errors

1) The WS-Management service cannot process the request. The WMI service returned an 'access denied' error. hResult -2146233088

2) Connecting to remote server x.x.x.x failed with the following error message : The WS-Management service cannot process the request. Cannot find the microsoft.sme.powershell session configuration in the WSMan: drive on the x.x.x.x computer. For more information, see the about_Remote_Troubleshooting Help topic

0 Replies