ansible --version
ansible 2.0.0
configured module search path = None
I receive this error when attempting to use wincopy.
But I do see win_copy in modules
ls /usr/lib/python2.7/site-packages/ansible/modules/core/windows/
copy.ps1 setup.ps1 win_copy.pyo win_feature.pyo win_get_url.pyo win_group.pyo win_msi.pyo win_ping.pyo win_service.pyo win_stat.pyo win_user.ps1
init.py slurp.ps1 win_feature.ps1 win_get_url.ps1 win_group.ps1 win_msi.ps1 win_ping.ps1 win_service.ps1 win_stat.ps1 win_template.py win_user.py
init.pyc win_copy.py win_feature.py win_get_url.py win_group.py win_msi.py win_ping.py win_service.py win_stat.py win_template.pyc win_user.pyc
init.pyo win_copy.pyc win_feature.pyc win_get_url.pyc win_group.pyc win_msi.pyc win_ping.pyc win_service.pyc win_stat.pyc win_template.pyo win_user.pyo
its win_copy, not wincopy.
That was a typo I am using win_copy
soo, win_copy is not in ansible (yet) but you seem to have python
versions of the file (which is only for doc, actual file is .ps1)
Is it possible to get an early release. If not how do you copy files and templates to a windows machine?
win_copy and win_template ARE in the works, currently only the common
code is in the repo, we hope to have the plugins soon.
OK moved them to my library path:
And got this
failed: [ntdvwqwebpcp02b] => {“failed”: true, “parsed”: false}
ConvertTo-Json : Could not load file or assembly ‘System.Web.Extensions,
Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’ or one of
its dependencies. The paging file is too small for this operation to complete.
(Exception from HRESULT: 0x800705AF)
At C:\Users\testaccount\AppData\Local\Temp\ansible-tmp-1430444421.11-4114021981
1126\setup.ps1:85 char:17
- echo $obj | ConvertTo-Json -Depth 99
-
- CategoryInfo : NotSpecified: (
[ConvertTo-Json], FileLoadExce
ption
- FullyQualifiedErrorId : System.IO.FileLoadException,Microsoft.PowerShell
.Commands.ConvertToJsonCommand
I also get this error if I disable the win_copy so MS Error.
Anyone else see this there is a hot fix
https://support.microsoft.com/en-us/kb/2842230/en-gb
More to come.
Another possible solution though I have failed to find a good one.
As a note if you are using 64 bit windows then the path might be windows.powershell32
http://blogs.technet.com/b/heyscriptingguy/archive/2013/07/30/learn-how-to-configure-powershell-memory.aspx
Hi,
What version of Windows are you targeting?
Is it a fresh image? Is it up to date with windows updates?
What version of Powershell is running on the windows host?
Can you run any Powershell directly on the windows machine (using the same user that you are connecting as)?
Jon
Is a win_copy (and win_file / win_template) plugin anticipated for the v2 launch?