winrm

问题 Using 2 machines, a local and a remote (with an address marked as remoteAddress ), I'm trying to run this on the local machine: Invoke-Command -ComputerName remoteAddress -ScriptBlock { dir c:\ } but I get this error: [remoteAddress] Connecting to remote server remoteAddress failed with the following error message : WinRM cannot complete the operation. Verify that the specified computer name is valid, that the computer is accessible over the network, and that a firewall exception for the

问题 I am testing ansible (developer build) to connect to a windows machine. ansible 2.0.0 (devel d1b98ec776) The following command fails ansible inh-jnambood-dt.india.mentorg.com -m win_ping -vvvv Error is as below bash-4.1$ ansible inh-jnambood-dt.india.mentorg.com -m win_ping -vvvv Using /etc/ansible/ansible.cfg as config file Loaded callback minimal of type stdout, v2.0 <inh-jnambood-dt.india.mentorg.com> ESTABLISH WINRM CONNECTION FOR USER: jnambood@MGC.MENTORG.COM on PORT 5985 TO inh

问题 I followed Matt Wrock's very helpful guide: Understanding and troubleshooting WinRM connection and authentication, (http://www.hurryupandwait.io/blog/understanding-and-troubleshooting-winrm-connection-and-authentication-a-thrill-seekers-guide-to-adventure) and I was able to set up an SSL connection on my remote machine, which I verified using: Test-WSMan -ComputerName "My DNS" -UseSSL ... which returned a non-error message. And I can also connect from powershell: Enter-PSSession -ComputerName

问题 I am a mac girl, working on connecting with knife-windows trough Opscode's managed Chef to my Rackspace Windows servers. (I know, it sounds exotic, but these Windows servers are a customer requirment). I tried to Chef for a spin but I am stuck in trying to bootstrap the Windows 2008 Server on Rackspace with the knife-windows command. I am working on OSX, using rvm, ruby 2.1.0 and a local gemset with chef + knife-windows. I was trying to follow the steps from: https://github.com/opscode/knife

问题 I have a problem to use pywinrm on linux, to get a PowerShell Session. I read several posts and questions on sites about that. But any that can solve my question. The error is in the Kerberos autentication. This is my krb5.conf: 0 [libdefaults] 1 default_realm = DOMAIN.COM.BR 2 ticket_lifetime = 24000 3 clock-skew = 300 4 dns_lookup_kdc = true 5 6 # [realms] 7 # LABCORP.CAIXA.GOV.BR = { 8 # kdc = DOMAIN.COM.BR 9 # kdc = DOMAIN.COM.BR 10 # admin_server = DOMAIN.COM.BR 11 # default_domain =

问题 C:\Users\Administrator>winrm quickconfig WinRM already is set up to receive requests on this machine. WSManFault Message ProviderFault WSManFault Message = Unable to check the status of the firewall. Error number: -2147024894 0x80070002 The system cannot find the file specified. 回答1: I had exactly the same issue, after a lot of reading and going through firewall restarts, service restarts, opening ports and that kind of stuff, the solution was quite easy: Just reboot the server This issue

问题 I have the following code to connect to a remote machine and execute commands.It is working if I create a new session for each Invoke-Command call to the remote machine. I don't want to create a new session each time I use Invoke-Command as that will not scale for thousands of commands on hundreds of machines concurrently and session creation itself is a big overhead. I need a way so that I can reuse the same session object in the $session powershell variable for multiple Invoke-Command calls

问题 I cloned a Windows Server 2012 R2 VM from a VM image. I can: Log in with Remote Desktop. Browse to IIS on port 80 from the Internet. Verify WinRM connectivity with Powershell: "Test-WSMan -ComputerName xyz.westus.cloudapp.azure.com" When I press the connect button in the test tool, the following error is logged: Error in connecting to the VM. Reason for not connecting to the VM : System.Management.Automation.Remoting.PSRemotingTransportException: Connecting to remote server xyz.westus

问题 I faced an issue using packer 1.4.3. At first I faced an issue, which described in #8085 (https://circleci.com/gh/hashicorp/packer/12207#artifacts/containers/0 version) . It was successfully fixed with downloading mentioned packer version. Currently I'm building Windows-2019 and Windows-2016 in Google Cloud Platform with packer. It works in proper way when I mention "winrm_username": "packer_user", if I use "winrm_username": "Adminitstator" or "winrm_username": "administator", I have an error

问题 We are deploying tens of VMs into Azure with VSTS. We now need to execute some scripts on specific VMs. Unfortunately, we can't let out VMs have public IPs. Is it possible to use VSTS tasks that require WinRM and PowerShell on Target Machines without public IP? If not, would would be our best option? 回答1: Is it possible to use VSTS tasks that require WinRM and PowerShell on Target Machines without public IP? It is not possible except you create a VPN tunnel. But it is not necessary and