tag:blogger.com,1999:blog-3920347219421157797.post7227188159809718154..comments2024-03-27T21:55:28.163-07:00Comments on Clint Boessen's Blog: What is WinRM?Clint Boessenhttp://www.blogger.com/profile/11156487394562821934noreply@blogger.comBlogger26125tag:blogger.com,1999:blog-3920347219421157797.post-13466271841329960422016-05-29T11:22:36.687-07:002016-05-29T11:22:36.687-07:00Thanks Clint, this really helped me wrap my head a...Thanks Clint, this really helped me wrap my head around WinRM. An android app (<a href="https://play.google.com/store/apps/details?id=com.abians.exam70_410&referrer=utm_source%3D18" rel="nofollow">https://play.google.com/store/apps/details?id=com.abians.exam70_410&referrer=utm_source%3D18</a>) showed me that I need to up my game for topic 2 of the MCSA exam. Your explanation was much clearer than the ones I found in my books.Anonymoushttps://www.blogger.com/profile/08576586348078202877noreply@blogger.comtag:blogger.com,1999:blog-3920347219421157797.post-714594111533752622015-01-07T02:45:38.877-08:002015-01-07T02:45:38.877-08:00Thanks Clint, winrm things getting clear for me fi...Thanks Clint, winrm things getting clear for me finally ;-)Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3920347219421157797.post-32249416792084545782014-10-15T18:56:57.041-07:002014-10-15T18:56:57.041-07:00You can enable it via Group Policy anonymous http:...You can enable it via Group Policy anonymous http://www.briantist.com/how-to/powershell-remoting-group-policy/Clint Boessenhttps://www.blogger.com/profile/11156487394562821934noreply@blogger.comtag:blogger.com,1999:blog-3920347219421157797.post-84308880266048484852014-10-15T04:24:33.188-07:002014-10-15T04:24:33.188-07:00if WinRM is not enabled and configured by default,...if WinRM is not enabled and configured by default, you'll be in a catch-22 situation. how do you remotely enable and configure WinRM when you rely on WinRM for remote command execution?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3920347219421157797.post-86820644024315556612014-05-23T18:25:21.185-07:002014-05-23T18:25:21.185-07:00Now I get it, Thanks!Now I get it, Thanks!Anonymoushttps://www.blogger.com/profile/07125470062327858802noreply@blogger.comtag:blogger.com,1999:blog-3920347219421157797.post-61913469793599414172013-03-05T11:18:44.772-08:002013-03-05T11:18:44.772-08:00http://blog.powershell.no/2010/03/04/enable-and-co...http://blog.powershell.no/2010/03/04/enable-and-configure-windows-powershell-remoting-using-group-policy/<br />This article may help for the above postAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-3920347219421157797.post-51153605891021135832012-09-05T00:45:13.957-07:002012-09-05T00:45:13.957-07:00Good post. Out of interest you perform some action...Good post. Out of interest you perform some actions on your remote machines with PowerShell commands. Just wondered what the advantages would be. As for port 80, I am trying unsuccessfully to get my XAMP (Apache) server to listen on port 80 ( after turning off IIS7 ) - it will of course work on port 8080.westerdaledhttps://www.blogger.com/profile/04978235432543060653noreply@blogger.comtag:blogger.com,1999:blog-3920347219421157797.post-38601431256812386192012-05-21T17:01:28.990-07:002012-05-21T17:01:28.990-07:00SCVMM 2008 R2 SP1 reconfigures the WinRm port to 8...SCVMM 2008 R2 SP1 reconfigures the WinRm port to 80 using a standard install.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3920347219421157797.post-65341872094946022022012-05-04T12:42:25.795-07:002012-05-04T12:42:25.795-07:00hacker's wet dream!hacker's wet dream!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3920347219421157797.post-17540646796945081412011-12-20T08:41:19.281-08:002011-12-20T08:41:19.281-08:00Note: To remotely manage a non-winrm system you ca...Note: To remotely manage a non-winrm system you can use the traditional "Computer Management" instead of "Server Manager" MMCAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-3920347219421157797.post-28448852584114009032011-11-30T01:16:58.617-08:002011-11-30T01:16:58.617-08:00Hi Clint ! Kunal here :- Thanks for your reply ......Hi Clint ! Kunal here :- Thanks for your reply ... It was very helpful to me :-)Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3920347219421157797.post-67118066129539371112011-11-29T19:11:08.000-08:002011-11-29T19:11:08.000-08:00WinRM 1.1 listens on port 80/443 by default. WinRM...WinRM 1.1 listens on port 80/443 by default. WinRM 2.0 on Windows 2008 R2 and Windows 7 use 5985 by default and 5986 for SSL based encryption.<br /><br />WinRM 1.1 had some smart code which allowed port 80/443 to be shared with the IIS. However when implementing network load balancing, as NLB takes control over the network stack it breaks this smart code. As a result MS had to move the WinRM ports to 5985 and 5986 for SSL in version 2.0Clint Boessen [MVP]http://clintboessen.blogspot.comnoreply@blogger.comtag:blogger.com,1999:blog-3920347219421157797.post-58503510020359881132011-11-29T03:48:16.926-08:002011-11-29T03:48:16.926-08:00Hi Clint ! Kunal here :- Thanks for reply ... But ...Hi Clint ! Kunal here :- Thanks for reply ... But can you just detailed me about this ?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3920347219421157797.post-14299677619680454362011-11-29T02:54:56.355-08:002011-11-29T02:54:56.355-08:00Check port 5985 by default and 5986 for SSL based ...Check port 5985 by default and 5986 for SSL based encryption... WinRM v2Clint Boessen [MVP]http://clintboessen.blogspot.comnoreply@blogger.comtag:blogger.com,1999:blog-3920347219421157797.post-898877674795669142011-11-28T23:04:55.417-08:002011-11-28T23:04:55.417-08:00Hi Clint ! I am Kunal , i am working as Software E...Hi Clint ! I am Kunal , i am working as Software Engineer and i am having a problem of port no 443[https] access for my windows 2003 r2 machine ... I need your help , How can i make work HTTPS SSL access in windows 2003 r2 machine ? Please reply me the procedure should be take for it and also the syntax line to invoke it ...<br /><br />Any help is Highly Appreciated ....<br />Special Thanks !!!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3920347219421157797.post-11851249037643918202011-11-28T22:18:22.009-08:002011-11-28T22:18:22.009-08:00Can you help me please ...Can you help me please ...Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3920347219421157797.post-34892005863335788022011-10-12T21:35:33.933-07:002011-10-12T21:35:33.933-07:00Very Helpful, Thanks a lot!!!Very Helpful, Thanks a lot!!!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3920347219421157797.post-34591157720814870612011-09-21T11:56:35.775-07:002011-09-21T11:56:35.775-07:00good postgood postAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-3920347219421157797.post-7529288634569511052010-09-09T23:57:13.920-07:002010-09-09T23:57:13.920-07:00Please see the following blog post, I shed some li...Please see the following blog post, I shed some light on it there:<br /><br /><a href="http://clintboessen.blogspot.com/2009/11/wmi-error-invalid-class-0x80041010-fix.html" rel="nofollow">http://clintboessen.blogspot.com/2009/11/wmi-error-invalid-class-0x80041010-fix.html</a>Clint Boessenhttps://www.blogger.com/profile/11156487394562821934noreply@blogger.comtag:blogger.com,1999:blog-3920347219421157797.post-82841706109591794462010-09-09T05:52:38.144-07:002010-09-09T05:52:38.144-07:00The above is seen in windows server 2008 R2 too.,
...The above is seen in windows server 2008 R2 too.,<br />Only windows server 2008 seems to work for me :(Manojhttps://www.blogger.com/profile/04943241605595446013noreply@blogger.comtag:blogger.com,1999:blog-3920347219421157797.post-38077708577425842042010-09-09T05:51:44.403-07:002010-09-09T05:51:44.403-07:00I have a windows 2003 R2 and in installed winrm.
I...I have a windows 2003 R2 and in installed winrm.<br />Its working perfectly for <br />winrm e wmi/root/cimv2/WIN32_NetworkAdapter<br />but not working for <br />winrm e wmi/root/wmi/MSFC_FibrePortHBAAttributes<br />any reason why its not working?<br /><br />Any help is highly appreciated.<br />ThanksManojhttps://www.blogger.com/profile/04943241605595446013noreply@blogger.comtag:blogger.com,1999:blog-3920347219421157797.post-82343355196886952052010-08-25T04:50:28.376-07:002010-08-25T04:50:28.376-07:00Any solutions to the above error? I have winrm li...Any solutions to the above error? I have winrm listening and did winrm quickconfig on the Vista and Server 2008 which I am trying to get to communicate with each other and am still getting this error.Unknownhttps://www.blogger.com/profile/16422823830886354739noreply@blogger.comtag:blogger.com,1999:blog-3920347219421157797.post-42226675973113026312010-07-06T21:12:53.322-07:002010-07-06T21:12:53.322-07:00great feature, great article!great feature, great article!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3920347219421157797.post-30468389760620882132010-07-03T03:47:16.488-07:002010-07-03T03:47:16.488-07:00I was also getting the same errors, any idea how i...I was also getting the same errors, any idea how it is mended?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3920347219421157797.post-2128996111526601232010-06-28T02:59:33.562-07:002010-06-28T02:59:33.562-07:00After running the winrm quickconfig command i get ...After running the winrm quickconfig command i get the exact same error as before:<br /><br />WSManFault<br />Message = The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig".<br /><br />Error number: -2144108526 0x80338012<br />The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consultthe logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig".<br /><br />not sure how to solve this issue.Anonymousnoreply@blogger.com