Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
tutorial:adm:configuration_-_winrm [2019/06/12 11:31] kucerar debug, erros |
tutorial:adm:configuration_-_winrm [2019/10/08 13:47] fiserp [Common issues] |
||
---|---|---|---|
Line 6: | Line 6: | ||
WinRM is a command-line tool. | WinRM is a command-line tool. | ||
- | ==== Check if Winrm is running ==== | + | ===== Check if Winrm is running |
< | < | ||
Line 16: | Line 16: | ||
Now execute the first command again and it should without error now. | Now execute the first command again and it should without error now. | ||
- | ==== Show current configuration ==== | + | ===== Show current configuration |
Display WinRM listener. It will show useful information about port, address, ... where WinRM is listening for incoming connections. | Display WinRM listener. It will show useful information about port, address, ... where WinRM is listening for incoming connections. | ||
After quick config you will probably see only one listener for HTTP. | After quick config you will probably see only one listener for HTTP. | ||
Line 30: | Line 30: | ||
{{: | {{: | ||
- | ==== Authentications methods ==== | + | ===== Authentications methods |
^ ^ Type of user | **Credential delegation** | ^ ^ Type of user | **Credential delegation** | ||
Line 51: | Line 51: | ||
< | < | ||
* CredSSP | * CredSSP | ||
- | < | + | < |
+ | winrm set winrm/ | ||
+ | Enable-WSManCredSSP -Role Server | ||
+ | </ | ||
- | ==== Permission configuration ==== | + | ===== Permission configuration |
If you want to use user which is not admin then we need a more configuration. If you want to use admin user you should ready to go even without it. | If you want to use user which is not admin then we need a more configuration. If you want to use admin user you should ready to go even without it. | ||
Line 81: | Line 84: | ||
< | < | ||
- | ==== Debug ==== | + | ===== Debugging ===== |
When you need to check if WinRM is ready for connection but you don't have access to the Windows server to check the configuration yourself use this tips. | When you need to check if WinRM is ready for connection but you don't have access to the Windows server to check the configuration yourself use this tips. | ||
Check if port is open and ready to connection, default ports are 5985 (HTTP) and 5986 (HTTPS): | Check if port is open and ready to connection, default ports are 5985 (HTTP) and 5986 (HTTPS): | ||
Linux < | Linux < | ||
- | Windows < | + | Windows < |
+ | or | ||
+ | Test-netConnection HOST -Port PORT | ||
+ | </ | ||
Now we know if we are able to connect to the WinRM port. In case the port is not accessible it can be probably blocked in firewall. | Now we know if we are able to connect to the WinRM port. In case the port is not accessible it can be probably blocked in firewall. | ||
Next we want to try to connect to WinRM. Install [[devel: | Next we want to try to connect to WinRM. Install [[devel: | ||
Open terminal (Linux) or powershell (Windows) | Open terminal (Linux) or powershell (Windows) | ||
- | < | + | < |
> python | > python | ||
>>> | >>> | ||
Line 98: | Line 104: | ||
>>> | >>> | ||
</ | </ | ||
- | After executing " | + | For connecting via HTTPS use this lane. The difference is in URL where we need to use https and port 5986. Then we are using one more argument where we specify path to trust store |
- | {{:tutorial:adm: | + | <code python> |
+ | >>> | ||
+ | </ | ||
- | Now what we did here? We connect | + | Then, execute the winrm call. Followin call simply instructs the remote powershell |
< | < | ||
- | === Commons errors | + | The fact that there were some stacktraces printed does not necessarily mean the call failed. |
- | the specified | + | |
+ | Now simply print the result by calling '' | ||
+ | {{: | ||
+ | |||
+ | |||
+ | |||
+ | ==== Common issues ==== | ||
+ | === Specified | ||
+ | Can be caused by: | ||
* wrong username or password | * wrong username or password | ||
- | * user is not in group | + | * user is not in correct user group on the Windows system |
{{: | {{: | ||
- | Access denied 500 - this error can be caused by: | + | === Access denied 500 === |
+ | Can be caused by: | ||
* wrong username or password | * wrong username or password | ||
* WinRM SDDL is not configured | * WinRM SDDL is not configured | ||
{{: | {{: | ||
+ | |||
+ | |||
+ | === CredSSP handshake error === | ||
+ | If you get this error when you trying to use CredSSP over HTTPS connection, the problem can be that there is configured certificate thumbprint directly in '' | ||
+ | < | ||
+ | Execute this command to delete '' | ||
+ | < | ||
+ | The configuration of certificate thumbprint in the Listener should remain there. | ||
+ | |||
+ | === x509 attribute parsing error === | ||
+ | When calling WinRM over HTTPS, you can encounter following error: | ||
+ | <code python> | ||
+ | Traceback (most recent call last): | ||
+ | File "/ | ||
+ | _lib.X509_up_ref(x509) | ||
+ | AttributeError: | ||
+ | </ | ||
+ | This seems to be caused by older versions of the '' | ||
+ | |||
+ | === Requests using non-urllib3 backend === | ||
+ | <note important> | ||
+ | This affects only '' | ||
+ | < | ||
+ | / | ||
+ | NoCertificateRetrievedWarning) | ||
+ | </ | ||
+ | You can confirm the behavior by: | ||
+ | - Installing '' | ||
+ | - Editing '' | ||
+ | - When running winrm script with NTLM, the warning should no longer pop up. | ||
+ | |||
+ | === HTTPS certificate not trusted === | ||
+ | Python, by default, uses its own certificate truststore located somewhere under ''/ | ||
+ | <code python> | ||
+ | import os | ||
+ | # there, you can explicitly set path to your CA chain | ||
+ | os.environ[" | ||
+ | |||
+ | from winrm.protocol import Protocol | ||
+ | |||
+ | p = Protocol( | ||
+ | endpoint=' | ||
+ | transport=' | ||
+ | username=' | ||
+ | password=' | ||
+ | # | ||
+ | shell_id = p.open_shell() | ||
+ | command_id = p.run_command(shell_id, | ||
+ | std_out, std_err, status_code = p.get_command_output(shell_id, | ||
+ | p.cleanup_command(shell_id, | ||
+ | p.close_shell(shell_id) | ||
+ | |||
+ | # this will output all that returned from the WinRM call | ||
+ | print " | ||
+ | print " | ||
+ | print " | ||
+ | </ | ||
+ | ===== HTTPS support ===== | ||
+ | The best case is to use HTTPS connection to connect to WinRM. To achieve this we need to do some more configuration on the server and on the client. | ||
+ | We need to create HTTPS listener and for this we will need some certificate. In this tutorial we will cover setting up WinRM with self signed certificate. | ||
+ | The configuration will be same if we want to use some other certificate, | ||
+ | |||
+ | The tested way to generate self signed certificate on linux via tutorial which can be found [[https:// | ||
+ | |||
+ | Now we have certificate which is imported in our windows server and now we can configure the HTTP listener | ||
+ | < | ||
+ | for deleting | ||
+ | winrm delete winrm/ | ||
+ | </ | ||
+ | |||
+ | Restart WinRM | ||
+ | < | ||
+ | |||
+ | Next step is to validate if we can connect to HTTPS listener so follow instruction in section debug and validate if HTTPS port is accessible. | ||
+ | Before we try to execute some powershell command via WinRM we need to import this certificate into client trust store and pass the path to this store as parameter - see debug section |