White Papers

15 Lifecycle Controller Integration Best Practices Guide
winrm set winrm/config @{MaxBatchItems="50"}
Additionally, increasing the allotted maximum envelope size and timeout can also increase performance.
winrm set winrm/config @{MaxEnvelopeSizekb="150"}
winrm set winrm/config @{MaxTimeoutms ="60000"}
Other optional WinRM configuration commands are listed below for convenience. To get the current WinRM
configuration settings, execute the following command.
winrm g winrm/config
By default, the client computer requires encrypted network traffic. To allow the client computer to request unencrypted
traffic, execute the following command:
winrm s winrm/config/Client @{AllowUnencrypted="true"}
TrustedHosts is an array that specifies the list of remote computers that are trusted. Other computers in a workgroup or
computers in a different domain should be added to this list.
Note: The computers in the TrustedHosts list are not authenticated.
Execute the following command to allow all computers to be included in TrustedHosts.
winrm s winrm/config/Client @{TrustedHosts="*"}
Basic authentication is a scheme in which the user name and password are sent in clear text to the server or proxy. This
method is the least secure method of authentication. The default is True.
Execute the following command to set client computer to use Basic authentication.
winrm s winrm/config/Client/Auth @{Basic="true"}
1.4 Client Timeout Settings
WINRM tool sets a default response timeout of 60 seconds for all WSMAN commands. WINRM does not allow for
varying this timeout interval. Using “winrm set winrm/config @{MaxTimeoutms ="80000"}” does not actually change
the timeout due to a bug in the WINRM tool. It is therefore recommended to not use WINRM for commands that may
take more than 1 minute to complete execution. Example: Enumerate of Lifecycle Logs typically takes 90 seconds or
more to complete.
The use of libraries that create SOAP-XML packets is highly recommended because the user can configure the timeout
duration using these libraries. Microsoft recommends the use of Powershell for limitations with WinRM. Refer to the
following Microsoft blog for further details: http://blogs.msdn.com/b/wmi/archive/2015/04/01/move-to-powershell-for-
winrm-management.aspx