PowerShell remote management is very powerful, open remote access to the original line of command, but not always downwind. Today to share some of the summary of netizens, sincerely hope that a certain solution to the immediate need.
Statement: The following content from the QQ group of Friends Collective Wisdom, by the old biography collation.
Failed to enable WinRM, report denied access, fix an example.
Keyword WinRM denied access 0x80070005-2147024891
Summary person: Old biography, Love PowerShell, "Pig know silly change" to share.
The problem of denying access when enabling WinRM is discussed in the group today. We worked together to find out where the problem crux, the summary check steps are as follows:
1. to determine the service, the Windows Remote Management (WS man) service has been started.
2. Determine the network access, the use of Classic mode, namely:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa]
"ForceGuest" =dword:00000000
If it is 1, please change to 0, restart the machine. Thanks to old history to provide solutions to problems.
3. determine (current) the account in the Administrators group, all set a password, not a blank password. Let the remote administrator of the null password, login to the machine, this is certainly unreasonable.
This, we and the Group of Friends to experiment with, the empty password will report the error of Access denied. Thanks to the questioner qq=504800471, to help verify.
4. and this key value may also be relevant, namely:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa]
"Limitblankpassworduse" =dword:00000001
Null password account, only log on locally.
5. Determine the right key point PowerShell icon, select the administrator, permissions to run PowerShell.
6. finally run WinRM quickconfig command.