[chef] Re: Re: Re: knife winrm browsing network shares

[Peter Donald < >]

Hi,

I had a bit of a poke around and found that our scripts often do a bit
more. Typically our "net use" commands are not persistent and at the
start of the script we do something like

net use * /delete /y

followed by

net use \\filer\share mypwd /persistent:no

Also - one thing that we seem to need to do but I am unsure why is
that we can not refer to sub-directories in the net use command. We
tend to interact with the top level shares ala

net use \\filer\share mypwd /persistent:no
dir \\filer\share\subdir

Rather than

net use \\filer\share\subdir mypwd /persistent:no
dir \\filer\share\subdir

Also noticed that we interact directly with the smb server rather than
using DFS ... unclear on the reasoning there

Hope that helps.

On Tue, Jun 11, 2013 at 11:09 AM, Peter Donald 
<
 >
 wrote:
> Hi,
>
> I haven't seen this behaviour as such. We use it for about ~20 VMs
> that run chef-client every 30 minutes and ~30 or so nightly batch
> jobs. While some intermittently fail, we have yet to triage the
> failures to net use although it is possible. We are just at the start
> of our windows automation journey. So we haven't noticed it above the
> noise.
>
> However, we have noticed that sometimes if we rdp into the server that
> winrm will sometimes turn out to be a bit flakey - unsure of the cause
> at this stage.
>
> On Tue, Jun 11, 2013 at 1:55 AM, Grep Juice 
> <
 >
>  wrote:
>> Looks like I spoke too soon, this hack seems to be unreliable, sometimes it
>> works other times I get a
>> System error 67 has occurred.
>> The network name cannot be found.
>> Access is denied.
>> It seems to be at random,and I've seen anecdotal evidence that "net use" is
>> not reliable enough to use in batch files. Have you found a way to make 
>> this
>> reliable?
>>
>> Thanks.
>>
>>
>>
>> On Fri, Jun 7, 2013 at 10:05 AM, Grep Juice 
>> <
 >
>>  wrote:
>>>
>>> Works! Thank you.
>>>
>>>
>>> On Thu, Jun 6, 2013 at 7:44 PM, Peter Donald 
>>> <
 >
>>> wrote:
>>>>
>>>> Hi,
>>>>
>>>> The easiest way I have found is to re-login as part of the winrm
>>>> session. So execute the command
>>>>
>>>> net use \\filer\share mypwd
>>>>
>>>> before you access the dir in the same session. We also had some issues
>>>> around the authentication code and ended  up having to add a patch
>>>> that looks like code in [1]. (We use AD for authentication but all our
>>>> deploy tools run on Linux).
>>>>
>>>> HTH
>>>>
>>>> [1] https://gist.github.com/realityforge/5725935
>>>>
>>>> On Fri, Jun 7, 2013 at 7:00 AM,  
>>>> <
 >
>>>>  wrote:
>>>> > Has anyone successfully used knife winrm for accessing remote shares?
>>>> > I can successfully do a:
>>>> > $ knife winrm -m server.mydomain.local -P 'mypwd' -p 5985 -x
>>>> > 'mydomain\Administrator' dir
>>>> >
>>>> > but get an "Access is denied" when doing dir \\\\filer\\share
>>>> >
>>>> > I have followed this doc and the knife winrm doc to setup the client
>>>> >
>>>> > http://msdn.microsoft.com/en-us/library/windows/desktop/ee309365%28v=vs.85%29.aspx
>>>> > with no luck.
>>>> >
>>>> > I see that the NTLM auth is successful on the windows host logs, but it
>>>> > seems
>>>> > like it's not using the CredSSP correctly. Toggling the CredSSP
>>>> > settings on the
>>>> > windows server has no effect at all.
>>>> >
>>>> > Any help is appreciated thanks!
>>>>
>>>>
>>>>
>>>> --
>>>> Cheers,
>>>>
>>>> Peter Donald
>>>
>>>
>>
>
>
>
> --
> Cheers,
>
> Peter Donald



-- 
Cheers,

Peter Donald