wsman file not found RRS feed

  • Question

  • Hello

    I'm using MS-WSMV to remote interact with a server and run some commands on it.

    To send wsman requests , I need to access these files from microsoft.com:


    But the file "http://schemas.microsoft.com/wbem/wsman/1/windows/shell/cmd" is not available and returns an error like "The resource you are looking for has been removed, had its name changed, or is temporarily unavailable."

    Is there any problem with this file?



    Tuesday, July 3, 2018 12:48 PM

All replies

  • Hello AlPayDev,

    Thank you for posting your question regarding MS-WSMV specification. A member of the Open Specifications team will be following up with you regarding your question.

    Will Gregg | open specifications

    Tuesday, July 3, 2018 2:27 PM
  • Hi A.P,

    I will be assisting you with this issue. I will investigate the missing file, and let you know what I find.


    Jeff McCashland | Microsoft Protocols Open Specifications Team

    Thursday, July 5, 2018 6:22 PM
  • Hi A.P,

    I am working with the WSMV team on the missing links.


    Jeff McCashland | Microsoft Protocols Open Specifications Team

    Thursday, July 12, 2018 6:01 PM
  • We are in a hurry and our development is stopped because of this. Could you please give me an ETA on when it becomes available agian?
    Sunday, July 15, 2018 11:35 AM
  • Hi A.P,

    Could you contact us at our DocHelp email alias (@microsoft.com)? We would like to know what repro steps can be used to produce the blocked scenario. Also, does the missing file cause errors in an equivalent Windows-to-Windows scenario?


    Jeff McCashland | Microsoft Protocols Open Specifications Team

    Monday, July 16, 2018 8:38 PM
  • Hi A.P,

    The documentation [MS-WSMV] states how the various requests associated with ResourceURI: http://schemas.microsoft.com/wbem/wsman/1/windows/shell/cmd are to be formulated and how the responses are to be understood. 

    WSDLs for generic WinRM/WSMan operations are published here https://msdn.microsoft.com/en-us/library/dd644706.aspx. These WSDLs only define the types of “Actions” (or high level service functions) and do not provide any detail on how the requests/responses are to be made and understood.

    [MS-WSMV]: Web Services Management Protocol Extensions for Windows Vista


    As for your issue described above:

      • What SOAP messages are to be exchanged:
          • Parse out the ShellID from CreateResponse
        • Command using section
          • Parse out CommandId from CommandResponse
        • Receive on <ShellID, CommandId> using section
          • Parse command output from ReceiveResponse
        • Signal on <ShellID, CommandId> using section
      • Delete on ShellID using section

    If you need further assistance on this issue, please contact us at our DocHelp (@microsoft .com) alias. Let us know more about what you're implementing, and what specific questions we can help answer.


    Jeff McCashland | Microsoft Protocols Open Specifications Team

    Friday, July 27, 2018 6:38 PM