winrm

Stuck trying to bootstrap Windows server using Chef

巧了我就是萌 提交于 2019-12-03 13:50:58
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-windows I have configured the winrm service. I have set up a rule to allow inbound connections in my

Remote Access with Powershell and Jenkins

雨燕双飞 提交于 2019-12-01 18:13:16
I am trying to run a powershell script on a remote (Windows 2008 Server R2) machine. The following code works great when executed directly from powershell. (I.e. everything is set up correctly, WinRM services are running, Hosts trust each other, login is correct...) However, when I execute the exact same code from a Jenkins instance (running on the same machine where I tested) I get a PSSessionStateBroken connection failure, . (Not posting full error because it is in German on my machine.) I suppose that means Jenkins is using powershell differently or has different powershell/winrm settings

Remote Access with Powershell and Jenkins

扶醉桌前 提交于 2019-12-01 17:41:58
问题 I am trying to run a powershell script on a remote (Windows 2008 Server R2) machine. The following code works great when executed directly from powershell. (I.e. everything is set up correctly, WinRM services are running, Hosts trust each other, login is correct...) However, when I execute the exact same code from a Jenkins instance (running on the same machine where I tested) I get a PSSessionStateBroken connection failure, . (Not posting full error because it is in German on my machine.) I

PowerShell remoting: Controlling what edition is being targeted (PowerShell Core or Windows PowerShell); the state of cross-platform remoting

跟風遠走 提交于 2019-12-01 13:38:48
This self-answered question, which focuses on Windows [1] , addresses the following aspects: Now that there are two PowerShell editions - the legacy, Windows-only Windows PowerShell and the cross-platform PowerShell Core , both may be installed on a given Windows machine: How can I tell which PowerShell edition will execute remote commands , such as via Invoke-Command -ComputerName ? How can I target a specific edition , both ad hoc and persistently , through configuration? Note: For an edition to be targetable via remoting on a given machine, it must be set up for remoting : Only Windows

PowerShell remoting: Controlling what edition is being targeted (PowerShell Core or Windows PowerShell); the state of cross-platform remoting

橙三吉。 提交于 2019-12-01 10:47:26
问题 This self-answered question, which focuses on Windows [1] , addresses the following aspects: Now that there are two PowerShell editions - the legacy, Windows-only Windows PowerShell and the cross-platform PowerShell Core , both may be installed on a given Windows machine: How can I tell which PowerShell edition will execute remote commands , such as via Invoke-Command -ComputerName ? How can I target a specific edition , both ad hoc and persistently , through configuration? Note: For an

How to add more than one machine to the trusted hosts list using winrm

北慕城南 提交于 2019-11-27 17:09:43
To run powershell commands on a machine from a remote machine we have to add the remote machine to the trusted hosts list of the host machine. I am adding machine A to machine B's trusted hosts using the following command : winrm set winrm/config/client ‘@{TrustedHosts="machineA"}’ How to add more machines say machine C, machine D to trusted hosts list of machine B? I prefer to work with the PSDrive WSMan:\ . Get TrustedHosts Get-Item WSMan:\localhost\Client\TrustedHosts Set TrustedHosts provide a single, comma-separated, string of computer names Set-Item WSMan:\localhost\Client\TrustedHosts

Connecting to remote server failed using WinRM from PowerShell

|▌冷眼眸甩不掉的悲伤 提交于 2019-11-27 14:05:46
I am trying to run powershell code from my computer to vm on my computer, but i keep getting this error: Connecting to remote server failed with the following error message : The WinRM client cannot process the request. If the authentication scheme is different from Kerberos, or if the client computer is not joined to a domain, then HTTPS transport must be used or the destination machine must be added to the TrustedHosts configuration setting. Use winrm.cmd to configure TrustedHosts. Note that computers in the TrustedHosts list might not be authenticated. You can get more information about

Connecting to remote server failed using WinRM from PowerShell

最后都变了- 提交于 2019-11-26 18:22:17
问题 I am trying to run powershell code from my computer to vm on my computer, but i keep getting this error: Connecting to remote server failed with the following error message : The WinRM client cannot process the request. If the authentication scheme is different from Kerberos, or if the client computer is not joined to a domain, then HTTPS transport must be used or the destination machine must be added to the TrustedHosts configuration setting. Use winrm.cmd to configure TrustedHosts. Note