On Fri, May 24, 2013 at 5:55 PM, Adam Edwards < " target="_blank"> > wrote:
Thanks for that summary Jeppe. I responded to a related issue on another thread, can you tell me if you've seen the winrm maxmemorypershellmb problem outside of Win2k12? My current theories on that are that it should not happen outside of 2k12, but appearance of it on 2k8r2 or other versions would disprove that.I have just tried on an Amazon image (ami-46908432) that is running Server 2008 R2. The image comes with WinRM 3.0 and I observe the same problems as described in http://tickets.opscode.com/browse/KNIFE-208. So my quick conclusion is that it is not caused by 2008 vs 2012 but rather WinRM 3.0 (which is default in 2k12)
C:\Users\Administrator>systeminfo | findstr /B /C:"OS Name" /C:"OS Version"
OS Name: Microsoft Windows Server 2008 R2 Datacenter
OS Version: 6.1.7601 Service Pack 1 Build 7601
C:\Users\Administrator>winrm id
IdentifyResponse
ProtocolVersion = http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd
ProductVendor = Microsoft Corporation
ProductVersion = OS: 6.1.7601 SP: 1.0 Stack: 3.0
C:\Users\Administrator>winrs -r:127.0.0.1 "powershell -noprofile -noninteractive c:\getjob2.ps1"
...
\\winrs_\\shell_\\j\\o\\b_fac6c27a-cc08-49d1-b889-3178ac800427
SettingId='\\winrs_\\shell_\\j\\o\\b_fac6c27a-cc08-49d1-b889-3178ac800427'
314572800
157286400
C:\getjob2.ps1 : Value is '157286400', should be '314572800'
At line:1 char:1
+ c:\getjob2.ps1
Thanks for the summary on the bugs that are fixed in other releases — I agree that these gem releases should happen as soon as they can. I will get a few more eyes on this so we can figure out how to get this delivered sooner.Sounds good, looking forward to it./Jeppe
Archive powered by MHonArc 2.6.16.