Share via

3.1.4.8.2 Remote Shells

  • Article

To initiate enumeration of the active Shell instances, a wsen:Enumerate message can be sent. This message can be sent asynchronously to any outstanding messages in progress to any of the active Shells.

The value of Resource URI will be different for the Text-based Command Shell and the Custom Remote Shell.<114>

In case of the Text-based Command Shell, the value of Resource URI MUST be as follows. http://schemas.microsoft.com/wbem/wsman/1/windows/shell/cmd

An example of Resource URI for Custom Remote Shell scenario is follows. http://schemas.microsoft.com/wbem/wsman/1/windows/shell/CustomShell

The WS-Management specification defines wsman:Filter as an alternative mechanism to specify filters that are different from that of the wsen:Filter. More details are specified in [DMTF-DSP0226] section 8.3.

Web Services Management Protocol Extensions for Windows Vista clients SHOULD not use the wsman:Filter element when processing the requests against ResourceURI. http://schemas.microsoft.com/wbem/wsman/1/windows/shell/cmd

Web Services Management Protocol Extensions for Windows Vista servers MUST return a wsen:FilteringNotSupported fault if the wsman:Filter element is used against ResourceURI. http://schemas.microsoft.com/wbem/wsman/1/windows/shell/cmd

In order to enumerate the commands in an active shell instance, Web Services Management Protocol Extensions for Windows Vista clients SHOULD<115> include in the Enumerate message a selector set with a selector containing the ShellID of the shell instance. This EPR was obtained from a wxf:ResourceCreated message during Shell instance creation.