[chef] Re: winrm

[Nikhil Shah < >]

Daniel,

I think you got it. I believe when I ported over it messed with the permission of the client key. I was able to deploy a new server, ill try the ones I have been having issues with. 

Nikhil Shah /  System Administrator

nshah " target="_blank" style="color: rgb(17, 85, 204); ">@theorchard.com 

The Orchard® / www.theorchard.com

t (+1) 212.308.5648 / f (+1) 212.201.9203

23 E. 4th St., 3rd Fl / New York, NY 10003

The Daily Rind™ / www.dailyrindblog.com
Facebook / @orchtweets

Privileged And Confidential Communication.
This electronic transmission, and any documents attached hereto, (a) are protected by the Electronic Communications Privacy Act (18 USC §§ 2510-2521), (b) may contain confidential and/or legally privileged information, and (c) are for the sole use of the intended recipient named above. If you have received this electronic message in error, please notify the sender and delete the electronic message. Any disclosure, copying, distribution, or use of the contents of the information received in error is strictly prohibited.

 

On Sep 18, 2013, at 6:16 PM, Daniel DeLeo < "> > wrote:

On Wednesday, September 18, 2013 at 2:03 PM, Paul Morton - BIA wrote:

Nikhil - This typically means that you have the wrong username or password specified. 401 is un-authorized.

On Sep 18, 2013, at 2:03 PM, Nikhil Shah < "> > wrote:

Anyone seen this error message? I had it working (of course with the hosted solution); however, this is the first windows server I'm launching hosting my open source server in house:

ERROR: Failed to authenticate to ["192.168.XX.XX"] as administrator

Response: Bad HTTP response returned from server (401).

DEBUG: Adding 192.168.XX.XX

DEBUG: :session => :init

DEBUG: :relay_to_servers => cmd.exe /C %TEMP%\bootstrap-5449-1379538020.bat

DEBUG: :relayed => 192.168.XX.XX

DEBUG: 192.168.XX.XX => :run_command

ERROR: Failed to authenticate to ["192.168.XX.XX"] as administrator

Response: Bad HTTP response returned from server (401).

Nikhil Shah / System Administrator

To clarify, your authentication credentials are being rejected by the Chef server. So either you have a bad client key or node name.

To test things out with knife, you can try something like `knife node list -s CHEF_SERVER_URL -u CLIENT_NAME -k PATH_TO_CLIENT_KEY`

-- 

Daniel DeLeo