Set-WSManInstance doesn't work as expected #26647
Replies: 2 comments 2 replies
-
|
I honestly haven't looked into the WSManInstance cmdlets to see what exactly broke and whether there are workarounds but in this case if you are trying to set this value on the local service/client you can just use the Set-Item -Path WSMan:\localhost\MaxEnvelopeSizeKb -Value 200 |
Beta Was this translation helpful? Give feedback.
-
|
This is working but for my script i prefer to use WSMAN Management module which is more reliable and work good for remote servers, and MS has the example above in their documentation as well and it is working in PowerShell 5(that i used to change the value one time), so it should work in PowerShell 7 as well. thanks anyway :) |
Beta Was this translation helpful? Give feedback.
-
|
I decided to take a look to see what actually was wrong and it turns out that with the move from 5.1 -> 7 the COM interface that resolves the By making sure the order is correct this cmdlet and |
Beta Was this translation helpful? Give feedback.
-
|
Great! Thanks Jordan |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
Set-WSManInstance -ResourceURI winrm/config -ValueSet @{MaxEnvelopeSizekb = "200"} is a cmdlet that exist in Set-WSManInstance Microsoft Documentation.
This Cmdlet is working fine on "Powershell 5.x", but it gives an error on "Powershell 7.x".
Error message:
Beta Was this translation helpful? Give feedback.
All reactions