Winrm ошибка неизвестное имя операции

• Remove From My Forums

• Question

• When I try to execute a winrm -qc command on any Windows 7 domain member computer I receive the following response:

  Error: Unknown operation name: »

  How do I resolve this please?

• Remove From My Forums

• Question

• When I try to execute a winrm -qc command on any Windows 7 domain member computer I receive the following response:

  Error: Unknown operation name: »

  How do I resolve this please?

• Remove From My Forums

• Question

• When I try to add a hyper-v host to system center, I get the error:

  Error (421)
  Agent installation failed on hyper-v because of a WS-Management configuration error.

  Recommended Action
  Ensure that the Windows Remote Management service is enabled and running on the server hyper-v. Additionally, in the Local Group Policy Editor (gpedit.msc), navigate to Computer ConfigurationAdministrative TemplatesWindows ComponentsWindows Remote Management
  (WinRM), and then ensure that there are no policy settings configured for WinRM Client or WinRM Service.

  When I install the agent manually on the hyper-v host (vmmagent.msi), I get the error:

  Error (413)
  The files needed to install agent, version , are missing from the Virtual Machine Manager server VMC.

  Recommended Action
  Reinstall the missing files by running Virtual Machine Manager Server Setup.

  ——————-

  Steps that I have taken to troubleshoot this issue:

  • To check integrity of or repair your host WMI repository,
    • run «winmgmt /salvagerepository«.
  • To check your WMI virtualization store,
    • start
      wbemtest by using a local admin account of the host machine and
    • connect to \<host>rootvirtualization
    • Try query «select * from msvm_ComputerSystem» and see if it succeeds.
  • To check your host’s WMI namespace security settings,
    • Go to Server Manager, click on Configuration then right-click on WMI Control and choose Properties
    • Click on Security tab, choose SCVMM and check its Security Settings.
      • Make sure that both Administrators group and Virtual Machine Manager Servers group have the full rights on the namespace.
  • To check your WnRM state,
    • run «winrm qc«.
  • To check if the WinRM listener is running,
    • run «winrm enum winrm/config/listener«, or
    • run «winrm get winrm/config» to get the entire WinRM config.
  • To check if your VMM agent is responding to winrm calls,
    • run «winrm invoke GetVersion wmi/root/scvmm/AgentManagement -r:http://<host> @{}«.
  • To manually restart VMM server service:
    • run «net stop vmmservice«, and run «net start vmmservice«.
  • To manually restart VMM host agent service:
    • run «net stop vmmagent«, and run «net start vmmagent«.
  • To manually restart Hyper-V service:
    • run «net stop vmms«, and run «net start vmms«.

  The only test that has failed is the winrm AgentManagement query. I can connect to wmi/root/scvmm, but AgentManagement does not exist. Does anyone have any ideas? (All other tests passed OK — same result — can’t install agent or add hyper-v host)

• Remove From My Forums

• Question

• When I try to add a hyper-v host to system center, I get the error:

  Error (421)
  Agent installation failed on hyper-v because of a WS-Management configuration error.

  Recommended Action
  Ensure that the Windows Remote Management service is enabled and running on the server hyper-v. Additionally, in the Local Group Policy Editor (gpedit.msc), navigate to Computer ConfigurationAdministrative TemplatesWindows ComponentsWindows Remote Management
  (WinRM), and then ensure that there are no policy settings configured for WinRM Client or WinRM Service.

  When I install the agent manually on the hyper-v host (vmmagent.msi), I get the error:

  Error (413)
  The files needed to install agent, version , are missing from the Virtual Machine Manager server VMC.

  Recommended Action
  Reinstall the missing files by running Virtual Machine Manager Server Setup.

  ——————-

  Steps that I have taken to troubleshoot this issue:

  • To check integrity of or repair your host WMI repository,
    • run «winmgmt /salvagerepository«.
  • To check your WMI virtualization store,
    • start
      wbemtest by using a local admin account of the host machine and
    • connect to \<host>rootvirtualization
    • Try query «select * from msvm_ComputerSystem» and see if it succeeds.
  • To check your host’s WMI namespace security settings,
    • Go to Server Manager, click on Configuration then right-click on WMI Control and choose Properties
    • Click on Security tab, choose SCVMM and check its Security Settings.
      • Make sure that both Administrators group and Virtual Machine Manager Servers group have the full rights on the namespace.
  • To check your WnRM state,
    • run «winrm qc«.
  • To check if the WinRM listener is running,
    • run «winrm enum winrm/config/listener«, or
    • run «winrm get winrm/config» to get the entire WinRM config.
  • To check if your VMM agent is responding to winrm calls,
    • run «winrm invoke GetVersion wmi/root/scvmm/AgentManagement -r:http://<host> @{}«.
  • To manually restart VMM server service:
    • run «net stop vmmservice«, and run «net start vmmservice«.
  • To manually restart VMM host agent service:
    • run «net stop vmmagent«, and run «net start vmmagent«.
  • To manually restart Hyper-V service:
    • run «net stop vmms«, and run «net start vmms«.

  The only test that has failed is the winrm AgentManagement query. I can connect to wmi/root/scvmm, but AgentManagement does not exist. Does anyone have any ideas? (All other tests passed OK — same result — can’t install agent or add hyper-v host)

• Remove From My Forums

• Вопрос

• When I try to execute a winrm -qc command on any Windows 7 domain member computer I receive the following response:

  Error: Unknown operation name: »

  How do I resolve this please?

Enter-PSSession : Сбой подключения к удаленному серверу msk-dp01. Сообщение об ошибке: Клиенту WinRM не удается обработать запрос. Невозможно определить тип содержимого ответа HTTP от компьютера назначения. Тип содержимого не является допустимым или отсутствует. Подробности см. в разделе справки «about_Remote_Troubleshooting».

строка:1 знак:1

+ Enter-PSSession msk-dp01

+ ~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo : InvalidArgument: (msk-dp01:String) [Enter-PSSession], PSRemotingTransportException

+ FullyQualifiedErrorId : CreateRemoteRunspaceFailed

PS C:Windowssystem32> Enter-PSSession msk-dp01

Enter-PSSession : Connecting to remote server msk-dp01 failed with the following error message : The WinRM client received an HTTP bad request status (400), but the remote service did not include any other information about the cause of the failure. For more information, see the about_Remote_Troubleshooting Help topic.

At line:1 char:1

+ Enter-PSSession msk-dp01

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo : InvalidArgument: (msk-dp01:String) [Enter-PSSession], PSRemotingTransportException

+ FullyQualifiedErrorId : CreateRemoteRunspaceFailed

 PS C:Windowssystem32> invoke-command -computername Node1 -ScriptBlock {gsv}
 [Node1] Connecting to remote server Node1 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: (Node1:String) [], PSRemotingTransportException
+ FullyQualifiedErrorId : WinRMOperationTimeout,PSSessionStateBroken

1