It sits there for a few moments and then moves on.
J
On Tuesday, February 16, 2016 at 4:55:21 PM UTC-6, J Hawkesworth wrote:
>
> The only time I've seen a raw really not produce any output was on ansible
> 1.9.4 where one of the command args contained a > - however the same
> problem doesn't
The only time I've seen a raw really not produce any output was on ansible
1.9.4 where one of the command args contained a > - however the same
problem doesn't occurr in 2.0.
Does it fail instantly or after a second or two?
Only thing other I can think of is to try the update to Windows
Windows 2008R2 is still a mystery. I'm using the stock AWS AMI with all
updates applied and upped the
PS RAM as I did for Windows 2012R2. Still, I get the same thing as before.
How can it just fail with no
output? I don;t see anything in the Windows event logs, but I could be
missing
Glad increasing the quota got you going on S 2012.
You can manually apply the hotfix, although my prefered way of getting
round it was to upgrade to Windows Management Framework 4.0 (which includes
powershell 4) if that's an option for you. I think there's an msi or msu
to run to install it -
Hi Jon,
Thanks so much for your reply. I carefully followed the instructions at
this link to double the amount of winrm ram from 1 gig to 2gig:
https://blogs.technet.microsoft.com/heyscriptingguy/2013/07/30/learn-how-to-configure-powershell-memory/
That solved the out-of-memory problem on
Bit of a guess but I wonder if you are hitting a quota limit in the winrm
configuration on your windows machine?
MaxMemoryPerShellMB looks the most likely - see
https://msdn.microsoft.com/en-us/library/windows/desktop/ee309367(v=vs.85).aspx
Unpatched Server 2008 R2 had a bug that mis-set the
