Invoke-command works on VM Win 8 32 bits but doens't on VM Wind 8 64 bits

Viewing 1 reply thread
  • Author
    Posts
    • #1562937
      Bruno Bernardi
      Participant
      Member Points: 364
      Rank: 2

      Hello, all of Powershell forum members.

      I meet a problem with “Invoke-Command” powershell command : I send exactly the same command on two Windows 8 Hyper-V Virtual Machines but the result is different.

      Here is a screenshot of the powershell command prompt :

      I follow the Michael Pietroforte recommendations on https://4sysops.com/wiki/enable-powershell-remoting/ on both VM.

      Could you give some suggestions to solve my problem ?

      Best regards.

      0
    • #1562940
      Michael Pietroforte
      Keymaster
      Member Points: 31,742
      Author of the year 2018
      Rank: 4

      What is the error message in English?

      0
      • #1562951
        Bruno Bernardi
        Participant
        Member Points: 364
        Rank: 2

        Hello Michael.

        I have found a english translation of the error message :

        [remoteAddress] Connecting to remote server remoteAddress failed with the
        following error message : WinRM cannot complete the operation. Verify that
        the specified computer name is valid, that the computer is accessible over
        the network, and that a firewall exception for the WinRM service is enabled
        and allows access from this computer. By default, the WinRM firewall exception
        for public profiles limits access to remote computers within the same local
        subnet.
        For more information, see the about_Remote_Troubleshooting Help topic.
        + CategoryInfo : OpenError: (remoteAddress:String) [], PSRemotingTransportException
        + FullyQualifiedErrorId : WinRMOperationTimeout,PSSessionStateBroken

        Do you think the roots cause could be the NetConnectionProfile setting ?

        Regards.

        0
        • #1562953
          Michael Pietroforte
          Keymaster
          Member Points: 31,742
          Author of the year 2018
          Rank: 4

          Seems as if remoting is not configured properly or that a firewall is blocking the remoting port. Read this.

          0
Viewing 1 reply thread
  • You must be logged in to reply to this topic.
© 4sysops 2006 - 2021

CONTACT US

Please ask IT administration questions in the forums. Any other messages are welcome.

Sending

Log in with your credentials

or    

Forgot your details?

Create Account