{"id":4801,"date":"2009-01-06T15:57:00","date_gmt":"2009-01-06T15:57:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/powershell\/2009\/01\/06\/manage-winrm-settings-with-wsman-provider\/"},"modified":"2019-02-18T13:12:57","modified_gmt":"2019-02-18T20:12:57","slug":"manage-winrm-settings-with-wsman-provider","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/powershell\/manage-winrm-settings-with-wsman-provider\/","title":{"rendered":"Manage winrm settings with wsman provider"},"content":{"rendered":"

PowerShell remoting is built on top of Windows Remote Management (WinRM), which is Microsoft\u2019s implementation of WS-Management protocol. You can use winrm.cmd command line tool to query and manage winrm settings. PowerShell V2 CTP3 contains a wsman provider for you to manage winrm settings with the standard *-Item cmdlets . Let\u2019s try it out:<\/font><\/p>\n

PS C:\\> cd wsman:
PS WSMan:\\> dir
   <\/span>WSManConfig: Microsoft.WSMan.Management\\WSMan::WSMan
ComputerName                                  <\/span>Type
————                                  <\/span>—-
localhost                                     <\/span>Container
PS WSMan:\\> cd .\\localhost
PS WSMan:\\localhost> dir | ft \u2013auto
   <\/span>WSManConfig: Microsoft.WSMan.Management\\WSMan::localhost
Name                <\/span>Value      <\/span>Type
—-                <\/span>—–      <\/span>—-
MaxEnvelopeSizekb   <\/span>150        <\/span>System.String
MaxTimeoutms        <\/span>180000     <\/span>System.String
MaxBatchItems       <\/span>32000      <\/span>System.String
MaxProviderRequests 4294967295 System.String
Client                   <\/span>      <\/span>Container
Service                        <\/span>Container
Shell                          <\/span>Container
Listener                       <\/span>Container
Plugin                         <\/span>Container
ClientCertificate              <\/span>Container<\/font><\/p>\n

At the top level of the wsman drive, you see a container named localhost, this contains all the winrm settings for the local computer. If you cd into localhost, you have six more containers (I put corresponding winrm command line in parentheses for your reference): client contains client side winrm settings ( winrm g winrm\/config\/client), service contains server side winrm settings (winrm  <\/span>g  <\/span>winrm\/config\/service), shell contains shell settings (winrm  <\/span>g winrm\/config\/winrs), listener contains listener instances (winrm e winrm\/config\/listener), plugin contains  <\/span>winrm plugin instances including the default microsoft.powershell plugin, and clientcertificate contains certificate mappings (winrm e winrm\/config\/service\/certmapping). The *-PSSessionConfiguration cmdlets were actually built on top of wsman provider. Let\u2019s try Remove-Item and New-Item on listener instances. Don\u2019t  <\/span>forget you can use tab completion to find out  <\/span>dynamic parameters of New-Item for specific path in wsman provider.<\/font><\/p>\n

PS WSMan:\\> cd .\\localhost\\Listener
PS WSMan:\\localhost\\Listener> Get-ChildItem
   <\/span>WSManConfig: Microsoft.WSMan.Management\\WSMan::localhost\\Listener
Name                      <\/span>Type                 <\/span>Keys
—-                      <\/span>—-                 <\/span>—-
Listener_98910385         <\/span>Container            <\/span>{Address=*, Transport=HTTP}
PS WSMan:\\localhost\\Listener> Remove-Item .\\Listener_98910385 \u2013Recurse
PS WSMan:\\localhost\\Listener> New-Item . -Port 8080 -Address * -Transport http
   <\/span>WSManConfig: Microsoft.WSMan.Management\\WSMan::localhost\\Listener
Name                      <\/span>Type                 <\/span>Keys
—-                      <\/span>—-                 <\/span>—-
Listener_98910385         <\/span>Container            <\/span>{Address=*, Transport=HTTP}<\/font><\/span> <\/font><\/span><\/p>\n

<\/font><\/span> Now let\u2019s use set-item to change server side  <\/span>winrm settings on a remote computer to allow CredSSP authentication. You can connect to remote winrm service using  <\/span>connect-wsman cmdlet, remote computer name will show up at the top level of the wsman drive if the connection is successful.<\/font><\/p>\n

PS WSMan:\\> Enable-WSManCredSSP *
cfg         <\/span>: <\/font>http:\/\/schemas.microsoft.com\/wbem\/wsman\/1\/config\/client\/auth<\/font><\/span><\/a>
lang        <\/span>: en-US
Basic       <\/span>: true
Digest      <\/span>: true
Kerberos    <\/span>: true
Negotiate   <\/span>: true
Certificate : true
CredSSP     <\/span>: true
PS WSMan:\\> New-PSSession weiwu-lh64.ntdev.corp.microsoft.com -cred $cred -Authentication credssp
<\/font><\/span>[weiwu-lh64.ntdev.corp.microsoft.com] Connecting to remote server failed with the following error message : The WinRM client cannot process the request. The authentication mechanism requested by the client is not supported by the server or unencrypted traffic is disabled in the service configuration. Verify the unencrypted traffic setting in the service configuration or specify one of the authentication mechanisms supported by the server.  <\/span>To use Kerberos, specify the computer name as the remote destination. Also verify that the client computer and the destination computer are joined to a domain. To use Basic, specify the computer name as the remote destination, specify Basic authentication and provide user name and password. Possible authentication mechanisms reported by server:     <\/span>Negotiate Kerberos
    <\/span>+ CategoryInfo          <\/span>: OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [], PSRemotingTransportException
    <\/span>+ FullyQualifiedErrorId : PSSessionOpenFailed<\/font><\/span>
PS WSMan:\\> Connect-WSMan weiwu-lh64
PS WSMan:\\> get-item .\\weiwu-lh64\\Service\\Auth\\CredSSP
   <\/span>WSManConfig: Microsoft.WSMan.Management\\WSMan::weiwu-lh64\\Service\\Auth
Name          <\/span>            <\/span>Value                             <\/span>                 <\/span>Type
—-                      <\/span>—–                             <\/span>                 <\/span>—-
CredSSP                   <\/span>false                                             <\/span> <\/span>System.String
PS WSMan:\\> set-item .\\weiwu-lh64\\Service\\Auth\\CredSSP true
PS WSMan:\\> New-PSSession weiwu-lh64.ntdev.corp.microsoft.com -cred $cred -Authentication credssp Id Name            <\/span>ComputerName    <\/span>State    <\/span>Configuration         <\/span>Availability
 <\/span>— —-            <\/span>————    <\/span>—–    <\/span>————-         <\/span>————
  <\/span>1 Session1        <\/span>weiwu-lh64.n… Opened   <\/span>Microsoft.PowerShell     <\/span>Available
PS WSMan:\\> Disconnect-WSMan weiwu-lh64
PS WSMan:\\> Disable-WSManCredSSP<\/font><\/span><\/p>\n

Enjoy!<\/p>\n

Wei Wu[MSFT]
Visit the Windows PowerShell Team blog at:    http:\/\/blogs.msdn.com\/PowerShell<\/font><\/strong><\/a>
Visit the Windows PowerShell ScriptCenter at:  http:\/\/www.microsoft.com\/technet\/scriptcenter\/hubs\/msh.mspx<\/font><\/strong><\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

PowerShell remoting is built on top of Windows Remote Management (WinRM), which is Microsoft\u2019s implementation of WS-Management protocol. You can use winrm.cmd command line tool to query and manage winrm settings. PowerShell V2 CTP3 contains a wsman provider for you to manage winrm settings with the standard *-Item cmdlets . Let\u2019s try it out: PS […]<\/p>\n","protected":false},"author":600,"featured_media":13641,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[8],"class_list":["post-4801","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-powershell","tag-remoting"],"acf":[],"blog_post_summary":"

PowerShell remoting is built on top of Windows Remote Management (WinRM), which is Microsoft\u2019s implementation of WS-Management protocol. You can use winrm.cmd command line tool to query and manage winrm settings. PowerShell V2 CTP3 contains a wsman provider for you to manage winrm settings with the standard *-Item cmdlets . Let\u2019s try it out: PS […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/posts\/4801","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/users\/600"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/comments?post=4801"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/posts\/4801\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/media\/13641"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/media?parent=4801"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/categories?post=4801"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/tags?post=4801"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}