RemotingErrorIdStrings.resx

<?xml version="1.0" encoding="utf-8"?>
<root>
  <!-- 
    Microsoft ResX Schema 
    
    Version 2.0
    
    The primary goals of this format is to allow a simple XML format 
    that is mostly human readable. The generation and parsing of the 
    various data types are done through the TypeConverter classes 
    associated with the data types.
    
    Example:
    
    ... ado.net/XML headers & schema ...
    <resheader name="resmimetype">text/microsoft-resx</resheader>
    <resheader name="version">2.0</resheader>
    <resheader name="reader">System.Resources.ResXResourceReader, System.Windows.Forms, ...</resheader>
    <resheader name="writer">System.Resources.ResXResourceWriter, System.Windows.Forms, ...</resheader>
    <data name="Name1"><value>this is my long string</value><comment>this is a comment</comment></data>
    <data name="Color1" type="System.Drawing.Color, System.Drawing">Blue</data>
    <data name="Bitmap1" mimetype="application/x-microsoft.net.object.binary.base64">
        <value>[base64 mime encoded serialized .NET Framework object]</value>
    </data>
    <data name="Icon1" type="System.Drawing.Icon, System.Drawing" mimetype="application/x-microsoft.net.object.bytearray.base64">
        <value>[base64 mime encoded string representing a byte array form of the .NET Framework object]</value>
        <comment>This is a comment</comment>
    </data>
                
    There are any number of "resheader" rows that contain simple 
    name/value pairs.
    
    Each data row contains a name, and value. The row also contains a 
    type or mimetype. Type corresponds to a .NET class that support 
    text/value conversion through the TypeConverter architecture. 
    Classes that don't support this are serialized and stored with the 
    mimetype set.
    
    The mimetype is used for serialized objects, and tells the 
    ResXResourceReader how to depersist the object. This is currently not 
    extensible. For a given mimetype the value must be set accordingly:
    
    Note - application/x-microsoft.net.object.binary.base64 is the format 
    that the ResXResourceWriter will generate, however the reader can 
    read any of the formats listed below.
    
    mimetype: application/x-microsoft.net.object.binary.base64
    value   : The object must be serialized with 
            : System.Runtime.Serialization.Formatters.Binary.BinaryFormatter
            : and then encoded with base64 encoding.
    
    mimetype: application/x-microsoft.net.object.soap.base64
    value   : The object must be serialized with 
            : System.Runtime.Serialization.Formatters.Soap.SoapFormatter
            : and then encoded with base64 encoding.

    mimetype: application/x-microsoft.net.object.bytearray.base64
    value   : The object must be serialized into a byte array 
            : using a System.ComponentModel.TypeConverter
            : and then encoded with base64 encoding.
    -->
  <xsd:schema id="root" xmlns="" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">
    <xsd:import namespace="http://www.w3.org/XML/1998/namespace" />
    <xsd:element name="root" msdata:IsDataSet="true">
      <xsd:complexType>
        <xsd:choice maxOccurs="unbounded">
          <xsd:element name="metadata">
            <xsd:complexType>
              <xsd:sequence>
                <xsd:element name="value" type="xsd:string" minOccurs="0" />
              </xsd:sequence>
              <xsd:attribute name="name" use="required" type="xsd:string" />
              <xsd:attribute name="type" type="xsd:string" />
              <xsd:attribute name="mimetype" type="xsd:string" />
              <xsd:attribute ref="xml:space" />
            </xsd:complexType>
          </xsd:element>
          <xsd:element name="assembly">
            <xsd:complexType>
              <xsd:attribute name="alias" type="xsd:string" />
              <xsd:attribute name="name" type="xsd:string" />
            </xsd:complexType>
          </xsd:element>
          <xsd:element name="data">
            <xsd:complexType>
              <xsd:sequence>
                <xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />
                <xsd:element name="comment" type="xsd:string" minOccurs="0" msdata:Ordinal="2" />
              </xsd:sequence>
              <xsd:attribute name="name" type="xsd:string" use="required" msdata:Ordinal="1" />
              <xsd:attribute name="type" type="xsd:string" msdata:Ordinal="3" />
              <xsd:attribute name="mimetype" type="xsd:string" msdata:Ordinal="4" />
              <xsd:attribute ref="xml:space" />
            </xsd:complexType>
          </xsd:element>
          <xsd:element name="resheader">
            <xsd:complexType>
              <xsd:sequence>
                <xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />
              </xsd:sequence>
              <xsd:attribute name="name" type="xsd:string" use="required" />
            </xsd:complexType>
          </xsd:element>
        </xsd:choice>
      </xsd:complexType>
    </xsd:element>
  </xsd:schema>
  <resheader name="resmimetype">
    <value>text/microsoft-resx</value>
  </resheader>
  <resheader name="version">
    <value>2.0</value>
  </resheader>
  <resheader name="reader">
    <value>System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
  </resheader>
  <resheader name="writer">
    <value>System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
  </resheader>
  <data name="DefaultRemotingExceptionMessage" xml:space="preserve">
    <value>An error of type "{0}" has occurred.</value>
  </data>
  <data name="OutOfMemory" xml:space="preserve">
    <value>Out of process memory.</value>
  </data>
  <data name="PipelineIdsDoNotMatch" xml:space="preserve">
    <value>Pipeline ID "{0}" does not match the InstanceId of the pipeline that is currently running, "{1}".</value>
  </data>
  <data name="PipelineNotFoundOnServer" xml:space="preserve">
    <value>Pipeline Id "{0}" was not found on the server.</value>
  </data>
  <data name="PipelineStopped" xml:space="preserve">
    <value>The remote pipeline has been stopped.</value>
  </data>
  <data name="RunspaceAlreadyExists" xml:space="preserve">
    <value>The session already exists. Trying to create the session again with the same InstanceId {0} is not allowed.</value>
  </data>
  <data name="RunspaceIdsDoNotMatch" xml:space="preserve">
    <value>The specified client session InstanceId "{0}" does not match the existing session's InstanceId "{1}".</value>
  </data>
  <data name="RemoteRunspaceOpenFailed" xml:space="preserve">
    <value>Opening the remote session failed.</value>
  </data>
  <data name="RunspaceCannotBeFound" xml:space="preserve">
    <value>The specified remote session with a client InstanceId of "{0}" cannot be found.</value>
  </data>
  <data name="ResponsePromptIdCannotBeFound" xml:space="preserve">
    <value>Prompt response has a prompt id "{0}" that cannot be found.</value>
  </data>
  <data name="RemoteHostCallFailed" xml:space="preserve">
    <value>Remote host call to "{0}" failed.</value>
  </data>
  <data name="RemoteHostMethodNotImplemented" xml:space="preserve">
    <value>Remote host method {0} is not implemented.</value>
  </data>
  <data name="RemoteHostDataEncodingNotSupported" xml:space="preserve">
    <value>Remote host method data encoding is not supported for type {0}.</value>
  </data>
  <data name="RemoteHostDataDecodingNotSupported" xml:space="preserve">
    <value>Remote host method data decoding is not supported for type {0}.</value>
  </data>
  <data name="NestedPipelineNotSupported" xml:space="preserve">
    <value>Creation of nested pipelines is not supported.</value>
  </data>
  <data name="RelativeUriForRunspacePathNotSupported" xml:space="preserve">
    <value>Relative URIs are not supported in the creation of remote sessions.</value>
  </data>
  <data name="RemoteHostDecodingFailed" xml:space="preserve">
    <value>A failure occurred while decoding data from the remote host. There was an error in the network data.</value>
  </data>
  <data name="MustBeAdminToOverrideThreadOptions" xml:space="preserve">
    <value>Only administrators can override the Thread Options remotely.</value>
  </data>
  <data name="RemoteHostPromptForCredentialModifiedCaption" xml:space="preserve">
    <value>Windows PowerShell Credential Request: {0}</value>
  </data>
  <data name="RemoteHostPromptForCredentialModifiedMessage" xml:space="preserve">
    <value>Warning: A script or application on the remote computer {0} is requesting your credentials. Enter your credentials only if you trust the remote computer and the application or script that is requesting them.

{1}</value>
  </data>
  <data name="RemoteHostReadLineAsSecureStringPrompt" xml:space="preserve">
    <value>A script or application on the remote computer {0} is asking to read a line securely. Enter sensitive information, such as your credentials, only if you trust the remote computer and the application or script that is requesting it.</value>
  </data>
  <data name="RemoteHostGetBufferContents" xml:space="preserve">
    <value>A script or application on the remote computer {0} is attempting to read the buffer contents on the Windows PowerShell host. For security reasons, this is not allowed; the call has been suppressed.</value>
  </data>
  <data name="RemoteHostPromptSecureStringPrompt" xml:space="preserve">
    <value>A script or application on the remote computer {0} is sending a prompt request. When you are prompted, enter sensitive information, such as credentials or passwords, only if you trust the remote computer and the application or script that is requesting the data.</value>
  </data>
  <data name="ReceivedUnsupportedRemoteHostCall" xml:space="preserve">
    <value>Received unsupported remote host call: {0}.</value>
  </data>
  <data name="ReceivedUnsupportedAction" xml:space="preserve">
    <value>Received remoting data with unsupported action: {0}.</value>
  </data>
  <data name="ReceivedUnsupportedDataType" xml:space="preserve">
    <value>Received remoting data with unsupported data type: {0}.</value>
  </data>
  <data name="MissingDestination" xml:space="preserve">
    <value>Remoting data is missing the destination property.</value>
  </data>
  <data name="MissingTarget" xml:space="preserve">
    <value>Remoting data is missing target interface property.</value>
  </data>
  <data name="MissingRunspaceId" xml:space="preserve">
    <value>Remoting data is missing Session InstanceId property.</value>
  </data>
  <data name="MissingDataType" xml:space="preserve">
    <value>Remoting data is missing RemotingDataType property.</value>
  </data>
  <data name="MissingCallId" xml:space="preserve">
    <value>Remoting data is missing CallId property.</value>
  </data>
  <data name="MissingMethodName" xml:space="preserve">
    <value>Remoting data is missing MethodName property.</value>
  </data>
  <data name="MissingIsStartFragment" xml:space="preserve">
    <value>The IsStartFragment flag for the first fragment is not set.</value>
  </data>
  <data name="MissingProperty" xml:space="preserve">
    <value>Remoting data is missing {0} property.</value>
  </data>
  <data name="ObjectIdsNotMatching" xml:space="preserve">
    <value>Unexpected ObjectId received. This can happen if the fragments are not properly constructed by the remote computer, or the data might have been corrupted or changed.</value>
  </data>
  <data name="ObjectIdCannotBeLessThanZero" xml:space="preserve">
    <value>ObjectId cannot be less than or equal to 0. This can happen if the fragments are not properly constructed by the remote computer, or the data has been changed by unauthorized users.</value>
  </data>
  <data name="FragmentIdsNotInSequence" xml:space="preserve">
    <value>The FragmentIDs of the same object must be in sequence, incrementally changing by 1. This can happen if the fragments are not properly constructed by the remote computer. The data might also have been corrupted or changed.</value>
  </data>
  <data name="ObjectIsTooBig" xml:space="preserve">
    <value>Remoting data is too large to be reassembled from the fragments. This can happen if the length of the data in a fragment is greater than Int32.Max. It can also occur if the data was changed by unauthorized users.</value>
  </data>
  <data name="MissingIsEndFragment" xml:space="preserve">
    <value>The IsEndFragment flag is not set for the last fragment. This can happen if the fragments are not properly constructed by the remote computer, or if the data was corrupted or changed.</value>
  </data>
  <data name="DeserializedObjectIsNull" xml:space="preserve">
    <value>Deserialized remoting data is null.</value>
  </data>
  <data name="BlobLengthNotInRange" xml:space="preserve">
    <value>Fragment blob length is out of range: {0}</value>
  </data>
  <data name="DecodingErrorForErrorRecord" xml:space="preserve">
    <value>Error in decoding ErrorRecord.</value>
  </data>
  <data name="DecodingErrorForPipelineStateInfo" xml:space="preserve">
    <value>Error in decoding PipelineStateInfo.</value>
  </data>
  <data name="DecodingErrorForRunspaceStateInfo" xml:space="preserve">
    <value>Error in decoding RunspaceStateInfo.</value>
  </data>
  <data name="ReceivedUnsupportedRemotingTargetInterfaceType" xml:space="preserve">
    <value>Received unsupported RemotingTargetInterface type: {0}</value>
  </data>
  <data name="UnknownTargetClass" xml:space="preserve">
    <value>Remote host method was invoked on an unknown target class: {0}</value>
  </data>
  <data name="MissingTargetClass" xml:space="preserve">
    <value>Remote host method was invoked without specifying a target class.</value>
  </data>
  <data name="DecodingErrorForRunspacePoolStateInfo" xml:space="preserve">
    <value>Error in decoding RunspacePoolStateInfo.</value>
  </data>
  <data name="DecodingErrorForMinRunspaces" xml:space="preserve">
    <value>Error in decoding Minimum runspaces.</value>
  </data>
  <data name="DecodingErrorForMaxRunspaces" xml:space="preserve">
    <value>Error in decoding Maximum runspaces.</value>
  </data>
  <data name="DecodingErrorForPowerShellStateInfo" xml:space="preserve">
    <value>Error in decoding Windows PowerShellStateInfo.</value>
  </data>
  <data name="CantCastPropertyToExpectedType" xml:space="preserve">
    <value>Unexpected type of {0} property (expected {1}, got {2}).</value>
  </data>
  <data name="CantCastRemotingDataToPSObject" xml:space="preserve">
    <value>Unexpected type of remoting data (expected PSObject, got {0}).</value>
  </data>
  <data name="CantCastCommandToPSObject" xml:space="preserve">
    <value>Unexpected type of encoded command (expected PSObject, got {0}).</value>
  </data>
  <data name="CantCastParameterToPSObject" xml:space="preserve">
    <value>Unexpected type of encoded command parameter (expected PSObject, got {0}).</value>
  </data>
  <data name="NotEnoughHeaderForRemoteDataObject" xml:space="preserve">
    <value>An error occurred while decoding data received from the remote computer. At least {0} bytes of data are required to decode a deserialized object that is received from a remote computer. This can happen if the fragments are not properly constructed by the remote computer, or if the data was corrupted or changed.</value>
  </data>
  <data name="RemotingDestinationNotForMe" xml:space="preserve">
    <value>Received packet not destined for logged-on user: user = {0}, packet destination = {1}.</value>
  </data>
  <data name="ClientNegotiationTimeout" xml:space="preserve">
    <value>The client negotiation timer has expired. The negotiation time-out interval is {0} milliseconds.</value>
  </data>
  <data name="ClientNegotiationFailed" xml:space="preserve">
    <value>Windows PowerShell client does not support the {0} {1} negotiated by the server. Make sure the server is compatible with the build {2} and the protocol version {3} of Windows PowerShell.</value>
  </data>
  <data name="ClientNotFoundCapabilityProperties" xml:space="preserve">
    <value>{0}. Negotiation with the server failed. Make sure the server is compatible with the build {1} and the protocol version {2} of Windows PowerShell.</value>
  </data>
  <data name="ServerRequestedToCloseSession" xml:space="preserve">
    <value>The destination server has sent a request to close the session.</value>
  </data>
  <data name="ServerNegotiationFailed" xml:space="preserve">
    <value>The server that is running Windows PowerShell does not support the {0} {1} negotiated by the client computer. Verify that the client computer is compatible with the build {2} and the protocol version {3} of Windows PowerShell.</value>
  </data>
  <data name="ServerConnectFailedOnNegotiation" xml:space="preserve">
    <value>The server that is running Windows PowerShell does not support connect operations on the {0} {1}  that is negotiated by the client computer. Make sure the client computer is compatible with the build {2} and the protocol version {3} of Windows PowerShell.</value>
  </data>
  <data name="ServerConnectFailedOnInputValidation" xml:space="preserve">
    <value>The server that is running Windows PowerShell cannot process the connect operation because the following information is not found or not valid: Client Capability information and Connect RunspacePool information.</value>
  </data>
  <data name="ServerConnectFailedOnServerStateValidation" xml:space="preserve">
    <value>The server that is running Windows PowerShell cannot process the connect operation because the server has either not been started, or it is shutting down.</value>
  </data>
  <data name="ServerConnectFailedOnMismatchedRunspacePoolProperties" xml:space="preserve">
    <value>The server that is running Windows PowerShell cannot process the connect operation because the server runspace pool properties did not match the client computer specified properties.</value>
  </data>
  <data name="ServerNotFoundCapabilityProperties" xml:space="preserve">
    <value>{0}. Negotiation with the client failed. Make sure the client is compatible with the build {1} and the protocol version {2} of Windows PowerShell.</value>
  </data>
  <data name="ServerNegotiationTimeout" xml:space="preserve">
    <value>The server negotiation timer has expired. The negotiation time-out interval is {0} milliseconds.</value>
  </data>
  <data name="ClientRequestedToCloseSession" xml:space="preserve">
    <value>The client computer has sent a request to close the session.</value>
  </data>
  <data name="FatalErrorCausingClose" xml:space="preserve">
    <value>An error has occurred which Windows PowerShell cannot handle. A remote session might have ended.</value>
  </data>
  <data name="ClientKeyExchangeFailed" xml:space="preserve">
    <value>The server did not respond with an encrypted session key within the specified time-out period.</value>
  </data>
  <data name="ServerKeyExchangeFailed" xml:space="preserve">
    <value>The client did not respond with a public key within the specified time-out period.</value>
  </data>
  <data name="ConnectFailed" xml:space="preserve">
    <value>Connection attempt failed.</value>
  </data>
  <data name="CloseIsCalled" xml:space="preserve">
    <value>Attempting to close the session.</value>
  </data>
  <data name="ForceClosed" xml:space="preserve">
    <value>Windows PowerShell cannot close the remote session properly. The session is in an undefined state because it was not opened or connected after being disconnected. Windows PowerShell will try to force the session to close on the local computer, but the session might not be closed on the remote computer. To close a remote session properly, first open it or connect it.</value>
  </data>
  <data name="CloseFailed" xml:space="preserve">
    <value>Could not close the session.</value>
  </data>
  <data name="CloseCompleted" xml:space="preserve">
    <value>The session is closed.</value>
  </data>
  <data name="UnsupportedWaitHandleType" xml:space="preserve">
    <value>The Wait handle type "{0}" is not supported.</value>
  </data>
  <data name="ReceivedDataStreamIsNotStdout" xml:space="preserve">
    <value>Received data has a stream ID index of "{0}". Only a Standard Output stream ID index of "0" is supported.</value>
  </data>
  <data name="StdInIsNotOpen" xml:space="preserve">
    <value>The Standard Input handle is not open.</value>
  </data>
  <data name="NativeWriteFileFailed" xml:space="preserve">
    <value>Native API call to WriteFile failed. Error code is {0}.</value>
  </data>
  <data name="NativeReadFileFailed" xml:space="preserve">
    <value>Native API call to ReadFile failed. Error code is {0}.</value>
  </data>
  <data name="InvalidSchemeValue" xml:space="preserve">
    <value>{0} is not a valid schema value. Valid values are "http" and "https".</value>
  </data>
  <data name="ClientReceiveFailed" xml:space="preserve">
    <value>Client side receive call failed.</value>
  </data>
  <data name="ClientSendFailed" xml:space="preserve">
    <value>Client side send call failed.</value>
  </data>
  <data name="CommandHandleIsNull" xml:space="preserve">
    <value>The command handle returned from the WinRS API WSManRunShellCommand is null.</value>
  </data>
  <data name="StdInCannotBeSetToNoWait" xml:space="preserve">
    <value>The Standard Input handle cannot be set to the 'no wait' state. The system error code is {0}.</value>
  </data>
  <data name="PortIsOutOfRange" xml:space="preserve">
    <value>The port number {0} is not within the range of valid values. The range of valid values is between 1 and 65535.</value>
  </data>
  <data name="ServerProcessExited" xml:space="preserve">
    <value>The server process has exited.</value>
  </data>
  <data name="CannotGetStdInHandle" xml:space="preserve">
    <value>The call to Windows API GetStdHandle to get the Standard Input handle resulted in an error code: {0}.</value>
  </data>
  <data name="CannotGetStdOutHandle" xml:space="preserve">
    <value>The call to Windows API GetStdHandle to get the Standard Output handle resulted in an error code: {0}.</value>
  </data>
  <data name="CannotGetStdErrHandle" xml:space="preserve">
    <value>The call to Windows API GetStdHandle to get the Standard Error handle resulted in an error code: {0}.</value>
  </data>
  <data name="ConnectExFailed" xml:space="preserve">
    <value>Connecting to remote server {0} failed.</value>
  </data>
  <data name="ConnectExCallBackError" xml:space="preserve">
    <value>Connecting to remote server {0} failed with the following error message : {1}</value>
  </data>
  <data name="CloseExCallBackError" xml:space="preserve">
    <value>Closing the remote server shell instance failed with the following error message : {0}</value>
  </data>
  <data name="SendExFailed" xml:space="preserve">
    <value>Sending data to remote server {0} failed.</value>
  </data>
  <data name="SendExCallBackError" xml:space="preserve">
    <value>Sending data to remote server {0} failed with the following error message : {1}</value>
  </data>
  <data name="ReceiveExFailed" xml:space="preserve">
    <value>Receiving data from remote server {0} failed.</value>
  </data>
  <data name="ReceiveExCallBackError" xml:space="preserve">
    <value>Processing data from remote server {0} failed with the following error message: {1}</value>
  </data>
  <data name="RunShellCommandExFailed" xml:space="preserve">
    <value>Starting a command on the remote server failed.</value>
  </data>
  <data name="RunShellCommandExCallBackError" xml:space="preserve">
    <value>Starting a command on the remote server failed with the following error message : {0}</value>
  </data>
  <data name="ReconnectShellCommandExCallBackError" xml:space="preserve">
    <value>Reconnecting to a command on the remote server failed with the following error message : {0}</value>
  </data>
  <data name="CommandSendExFailed" xml:space="preserve">
    <value>Sending data to a remote command failed.</value>
  </data>
  <data name="CommandSendExCallBackError" xml:space="preserve">
    <value>Sending data to a remote command failed with the following error message: {0}</value>
  </data>
  <data name="CommandReceiveExFailed" xml:space="preserve">
    <value>Receiving data for a remote command failed.</value>
  </data>
  <data name="CommandReceiveExCallBackError" xml:space="preserve">
    <value>Processing data for a remote command failed with the following error message: {0}</value>
  </data>
  <data name="GeneralError" xml:space="preserve">
    <value>Error with error code {0} occurred while calling method {1}.</value>
  </data>
  <data name="TroubleShootingHelpTopic" xml:space="preserve">
    <value>{0} For more information, see the about_Remote_Troubleshooting Help topic.</value>
  </data>
  <data name="DisconnectShellExFailed" xml:space="preserve">
    <value>Failed to disconnect from the remote server {0}.</value>
  </data>
  <data name="DisconnectShellExCallBackErrr" xml:space="preserve">
    <value>Disconnecting from the remote server failed with the following error message : {0}</value>
  </data>
  <data name="ReconnectShellExFailed" xml:space="preserve">
    <value>Reconnecting to the remote server failed.</value>
  </data>
  <data name="ReconnectShellExCallBackErrr" xml:space="preserve">
    <value>Reconnecting to the remote server {0} failed with the following error message : {1}</value>
  </data>
  <data name="IPCTransportConnectError" xml:space="preserve">
    <value>Inter-process communication (IPC) transport does not support connect operations.</value>
  </data>
  <data name="NonExistentInitialSessionStateProvider" xml:space="preserve">
    <value>An EndpointConfiguration with Id {0} does not exist on the remote server. Contact your Windows PowerShell administrator, or the owner or creator of the endpoint configuration.</value>
  </data>
  <data name="InitialSessionStateNull" xml:space="preserve">
    <value>The EndpointConfiguration with the {0} identifier is not in a valid initial session state on the remote computer. Contact your Windows PowerShell administrator, or the owner or creator of the endpoint configuration.</value>
  </data>
  <data name="MandatoryValueNotPresent" xml:space="preserve">
    <value>The mandatory value {0} is not specified for the {1} registry key.</value>
  </data>
  <data name="MandatoryValueNotInCorrectFormat" xml:space="preserve">
    <value>The mandatory value {0} is not in the correct format for registry key {1}. The expected format is 'string'.</value>
  </data>
  <data name="StartupScriptNotCorrect" xml:space="preserve">
    <value>"{0}" must specify a Windows PowerShell script file that ends with extension ".ps1".</value>
  </data>
  <data name="DuplicateInitializationParameterFound" xml:space="preserve">
    <value>The {0} parameter is already specified in the {1} section. Contact your administrator to make sure that {0} is specified only once.</value>
  </data>
  <data name="NoAttributesFoundForParamElement" xml:space="preserve">
    <value>Expected "{0}" and "{1}" attributes in the "{2}" element.</value>
  </data>
  <data name="AssemblyLoadAttributesNotFound" xml:space="preserve">
    <value>"{0}", "{1}" must be specified in the "{2}" section to dynamically load the assembly.</value>
  </data>
  <data name="UnableToLoadAssembly" xml:space="preserve">
    <value>Unable to load the assembly "{0}" specified in the "{1}" section.</value>
  </data>
  <data name="UnableToLoadType" xml:space="preserve">
    <value>Unable to load the type "{0}" specified in the "{1}" section.</value>
  </data>
  <data name="TypeNeedsAssembly" xml:space="preserve">
    <value>Both "{0}" and "{1}" must be specified in the "{2}" section.</value>
  </data>
  <data name="RedirectedURINotWellFormatted" xml:space="preserve">
    <value>The destination "{0}" requested the connection to be redirected to "{1}". However "{1}" is not a well formatted URI.</value>
  </data>
  <data name="URIEndPointNotResolved" xml:space="preserve">
    <value>{0}Redirect location reported: {1}.</value>
  </data>
  <data name="URIRedirectWarningToHost" xml:space="preserve">
    <value>Your connection has been redirected to the following URI: "{0}"</value>
  </data>
  <data name="URIRedirectionReported" xml:space="preserve">
    <value>{0} To automatically connect to the redirected URI, verify the "{1}" property of the session preference variable "{2}", and use the "{3}" parameter on the cmdlet.</value>
  </data>
  <data name="ReceivedObjectSizeExceededMaximumClient" xml:space="preserve">
    <value>The current deserialized object size of the data received from the remote server exceeded the allowed maximum object size. The current deserialized object size is {0}. The allowed maximum object size is {1}.</value>
  </data>
  <data name="ReceivedDataSizeExceededMaximumClient" xml:space="preserve">
    <value>The total data received from the remote server exceeded the allowed maximum. The allowed maximum is {0}.</value>
  </data>
  <data name="ReceivedObjectSizeExceededMaximumServer" xml:space="preserve">
    <value>The current deserialized object size of the data received from the remote client computer exceeded the allowed maximum object size. The current deserialized object size is {0}. The allowed maximum object size is {1}.</value>
  </data>
  <data name="ReceivedDataSizeExceededMaximumServer" xml:space="preserve">
    <value>The total data received from the remote client exceeded the allowed maximum. The allowed maximum is {0}.</value>
  </data>
  <data name="StartupScriptThrewTerminatingError" xml:space="preserve">
    <value>Running startup script threw an error: {0}.</value>
  </data>
  <data name="RemoteRunspaceInfoHasDuplicates" xml:space="preserve">
    <value>Specified RemoteRunspaceInfo objects have duplicates.</value>
  </data>
  <data name="RemoteRunspaceInfoLimitExceeded" xml:space="preserve">
    <value>Specified RemoteRunspaceInfo objects have exceeded the maximum allowable limit.</value>
  </data>
  <data name="RemoteRunspaceOpenUnknownState" xml:space="preserve">
    <value>Opening the remote session failed with an unexpected state. State {0}.</value>
  </data>
  <data name="UriSpecifiedNotValid" xml:space="preserve">
    <value>Specified Uri {0} is not valid.</value>
  </data>
  <data name="RemoteRunspaceClosed" xml:space="preserve">
    <value>Remote Session closed for Uri {0}.</value>
  </data>
  <data name="RemoteRunspaceNotAvailableForSpecifiedComputer" xml:space="preserve">
    <value>Remote session is not available for ComputerName {0}.</value>
  </data>
  <data name="RemoteRunspaceNotAvailableForSpecifiedRunspaceId" xml:space="preserve">
    <value>Remote session is not available for {0}.</value>
  </data>
  <data name="StopPSJobWhatIfTarget" xml:space="preserve">
    <value>Remote Command: {0}, associated with the job that has an ID of "{1}".</value>
  </data>
  <data name="NewRunspaceAmbiguousAuthentication" xml:space="preserve">
    <value>A {0} cannot be specified when {1} is specified.</value>
  </data>
  <data name="WildCardErrorFilePathParameter" xml:space="preserve">
    <value>Wildcard characters are not supported for the FilePath parameter. Specify a path without wildcard characters.</value>
  </data>
  <data name="FilePathNotFromFileSystemProvider" xml:space="preserve">
    <value>The path specified as the value of the FilePath parameter is not from the FileSystem provider.</value>
  </data>
  <data name="FilePathShouldPS1Extension" xml:space="preserve">
    <value>The value of the FilePath parameter must be a Windows PowerShell script file. Enter the path to a file with a .ps1 file name extension and try the command again.</value>
  </data>
  <data name="InvalidComputerName" xml:space="preserve">
    <value>One or more computer names are not valid. If you are trying to pass a URI, use the -ConnectionUri parameter, or pass URI objects instead of strings.</value>
  </data>
  <data name="InvalidJobStateGeneral" xml:space="preserve">
    <value>The state of the current job instance is not valid for this operation.</value>
  </data>
  <data name="JobWithSpecifiedNameNotFound" xml:space="preserve">
    <value>The command cannot find the job because the job name {0} was not found. Verify the value of the Name parameter, and then try the command again.</value>
  </data>
  <data name="JobWithSpecifiedInstanceIdNotFound" xml:space="preserve">
    <value>The command cannot find a job with the instance identifier {0}. Verify the value of the InstanceId parameter, and then try the command again.</value>
  </data>
  <data name="JobWithSpecifiedSessionIdNotFound" xml:space="preserve">
    <value>The command cannot find a job with the job ID {0}. Verify the value of the Id parameter and then try the command again.</value>
  </data>
  <data name="JobWithSpecifiedNameNotCompleted" xml:space="preserve">
    <value>The command cannot remove the job with the job ID {0} and the name {1} because the job is not finished. To remove the job, first stop the job, or use the Force parameter.</value>
  </data>
  <data name="JobWithSpecifiedSessionIdNotCompleted" xml:space="preserve">
    <value>The command cannot remove the job with the job ID {0} because the job is not finished. To remove the job, first stop the job, or use the Force parameter.</value>
  </data>
  <data name="JobWithSpecifiedInstanceIdNotCompleted" xml:space="preserve">
    <value>The command cannot remove the job with the job ID {0} and the instance identifier {1} because the job is not finished. To remove the job, first stop the job or use the Force parameter.</value>
  </data>
  <data name="RemovePSJobWhatIfTarget" xml:space="preserve">
    <value>Remote Command: {0}, associated with a job that has an ID of "{1}".</value>
  </data>
  <data name="ComputerNameParamNotSupported" xml:space="preserve">
    <value>The command cannot retrieve the jobs of the specified computers. The ComputerName parameter can be used only with jobs created by using Windows PowerShell remoting.</value>
  </data>
  <data name="RunspaceParamNotSupported" xml:space="preserve">
    <value>The Session parameter can be used only with PSRemotingJob objects.</value>
  </data>
  <data name="RemoteRunspaceNotAvailableForSpecifiedName" xml:space="preserve">
    <value>The remote session with the name {0}  is not available.</value>
  </data>
  <data name="RemoteRunspaceNotAvailableForSpecifiedSessionId" xml:space="preserve">
    <value>The remote session with the session ID {0} is not available.</value>
  </data>
  <data name="ItemNotFoundInRepository" xml:space="preserve">
    <value>{0} does not contain an item with ID of {1}.</value>
  </data>
  <data name="CannotRemoveJob" xml:space="preserve">
    <value>The command cannot remove the job because it does not exist or because it is a child job. Child jobs can be removed only by removing the parent job.</value>
  </data>
  <data name="CSCDoubleParameterOutOfRange" xml:space="preserve">
    <value>{0} is not a valid value for the parameter {1}. The value must be greater than or equal to 0.</value>
  </data>
  <data name="ProxyAmbiguousAuthentication" xml:space="preserve">
    <value>{0} cannot be specified as a proxy authentication mechanism. Only {1},{2} or {3} are supported for proxy authentication.</value>
  </data>
  <data name="ProxyCredentialWithoutAccess" xml:space="preserve">
    <value>Proxy credentials cannot be specified when using the following proxy access type: {0}. Either specify a different access type, or do not specify proxy credentials.</value>
  </data>
  <data name="WrongSessionOptionValue" xml:space="preserve">
    <value>A {0} value must be specified for session option {1}.</value>
  </data>
  <data name="PushedRunspaceMustBeOpen" xml:space="preserve">
    <value>Session must be open.</value>
  </data>
  <data name="HostDoesNotSupportPushRunspace" xml:space="preserve">
    <value>The host does not support Enter-PSSession and Exit-PSSession.</value>
  </data>
  <data name="RemoteRunspaceHasMultipleMatchesForSpecifiedRunspaceId" xml:space="preserve">
    <value>Multiple matches found for session ID {0}.</value>
  </data>
  <data name="RemoteRunspaceHasMultipleMatchesForSpecifiedSessionId" xml:space="preserve">
    <value>Multiple matches found for session ID {0}.</value>
  </data>
  <data name="RemoteRunspaceHasMultipleMatchesForSpecifiedName" xml:space="preserve">
    <value>Multiple matches found for name {0}.</value>
  </data>
  <data name="RemoteRunspaceDoesNotSupportPushRunspace" xml:space="preserve">
    <value>Enter-PSSession failed because the remote session does not provide required commands.</value>
  </data>
  <data name="HostInNestedPrompt" xml:space="preserve">
    <value>You cannot run Enter-PSSession from a nested prompt.</value>
  </data>
  <data name="WsmanMaxRedirectionCountVariableDescription" xml:space="preserve">
    <value>The maximum number of WS-Man URI redirections to allow while connecting to a remote computer</value>
  </data>
  <data name="PSDefaultSessionOptionDescription" xml:space="preserve">
    <value>Default session options for new remote sessions</value>
  </data>
  <data name="PSSessionConfigurationName" xml:space="preserve">
    <value>Name of the session configuration which will be loaded on the remote computer</value>
  </data>
  <data name="PSSessionAppName" xml:space="preserve">
    <value>AppName where the remote connection will be established</value>
  </data>
  <data name="PSSenderInfoDescription" xml:space="preserve">
    <value>Contains information about the remote user starting the remote session. This variable is available only from a remote session.</value>
  </data>
  <data name="CSCmdsTypeNeedsAssembly" xml:space="preserve">
    <value>Either "{0}" and "{1}" must both be specified, or neither must not be specified.</value>
  </data>
  <data name="CSCmdsShellNotFound" xml:space="preserve">
    <value>Session configuration "{0}" was not found.</value>
  </data>
  <data name="CSCmdsShellNotPowerShellBased" xml:space="preserve">
    <value>Session configuration "{0}" is not a Windows PowerShell-based shell.</value>
  </data>
  <data name="CustomShellNotFound" xml:space="preserve">
    <value>No session configuration matches criteria "{0}".</value>
  </data>
  <data name="CSShouldProcessAction" xml:space="preserve">
    <value>{0}</value>
  </data>
  <data name="CSShouldProcessTarget" xml:space="preserve">
    <value>Name: {0}</value>
  </data>
  <data name="CSShouldProcessTargetAdminEnable" xml:space="preserve">
    <value>Name: {0}. This lets administrators remotely run Windows PowerShell commands on this computer.</value>
  </data>
  <data name="NcsCannotDeleteFile" xml:space="preserve">
    <value>Cannot delete temporary file {0}. Reason for failure: {1}.</value>
  </data>
  <data name="NcsCannotDeleteFileAfterInstall" xml:space="preserve">
    <value>The new shell was successfully registered, but Windows PowerShell cannot delete the temporary file {0}. Reason for failure: {1}.</value>
  </data>
  <data name="NcsCannotWritePluginContent" xml:space="preserve">
    <value>Cannot write the shell configuration data into the temporary file {0}. Reason for failure: {1}.</value>
  </data>
  <data name="NcsScriptMessageV" xml:space="preserve">
    <value>Running command "{0}" to create a new session configuration.</value>
  </data>
  <data name="NcsShouldProcessTargetSDDL" xml:space="preserve">
    <value>Name: {0} SDDL: {1}. This lets selected users remotely run Windows PowerShell commands on this computer.</value>
  </data>
  <data name="RcsScriptMessageV" xml:space="preserve">
    <value>Running command "{0}" to remove a session configuration.</value>
  </data>
  <data name="GcsScriptMessageV" xml:space="preserve">
    <value>Running command "{0}" to get Windows PowerShell-based session configurations.</value>
  </data>
  <data name="ScsScriptMessageV" xml:space="preserve">
    <value>Running command "{0}" to update the session configuration properties.</value>
  </data>
  <data name="ScsShouldProcessTargetSDDL" xml:space="preserve">
    <value>Name: {0} SDDL: {1}</value>
  </data>
  <data name="EcsScriptMessageV" xml:space="preserve">
    <value>Running command "{0}" to enable the session configuration.</value>
  </data>
  <data name="EcsWSManQCCaption" xml:space="preserve">
    <value>WinRM Quick Configuration</value>
  </data>
  <data name="EcsWSManQCQuery" xml:space="preserve">
    <value>Running command "{0}" to enable remote management of this computer by using the Windows Remote Management (WinRM) service.
 This includes:
    1. Starting or restarting (if already started) the WinRM service
    2. Setting the WinRM service startup type to Automatic
    3. Creating a listener to accept requests on any IP address
    4. Enabling Windows Firewall inbound rule exceptions for WS-Management traffic (for http only).

Do you want to continue?</value>
  </data>
  <data name="EcsWSManShouldProcessDesc" xml:space="preserve">
    <value>Performing operation "{0}".</value>
  </data>
  <data name="EcsShouldProcessTarget" xml:space="preserve">
    <value>Name: {0} SDDL: {1}. This lets selected users remotely run Windows PowerShell commands on this computer.</value>
  </data>
  <data name="DcsScriptMessageV" xml:space="preserve">
    <value>Running command "{0}" to disable the session configuration.</value>
  </data>
  <data name="DcsShouldProcessTarget" xml:space="preserve">
    <value>Name: {0} SDDL: {1}. This denies access to this session configuration for everyone.</value>
  </data>
  <data name="DcsWarningMessage" xml:space="preserve">
    <value>Disabling the session configurations does not undo all the changes made by the Enable-PSRemoting or Enable-PSSessionConfiguration cmdlet. You might have to manually undo the changes by following these steps:
    1. Stop and disable the WinRM service.
    2. Delete the listener that accepts requests on any IP address.
    3. Disable the firewall exceptions for WS-Management communications.
    4. Restore the value of the LocalAccountTokenFilterPolicy to 0, which restricts remote access to members of the Administrators group on the computer.</value>
  </data>
  <data name="EDcsRequiresElevation" xml:space="preserve">
    <value>Access is denied. To run this cmdlet, start Windows PowerShell with the "Run as administrator" option.</value>
  </data>
  <data name="RestartWSManServiceMessageV" xml:space="preserve">
    <value>Restarting WinRM service</value>
  </data>
  <data name="RestartWSManServiceAction" xml:space="preserve">
    <value>"Restart-Service"</value>
  </data>
  <data name="RestartWSManServiceTarget" xml:space="preserve">
    <value>Name: {0}</value>
  </data>
  <data name="RestartWSManRequiredShowUI" xml:space="preserve">
    <value>The WinRM service must be restarted before a UI can be displayed for the SecurityDescriptor selection. Restart the WinRM service, and then run the following command: "{0}"</value>
  </data>
  <data name="ERemotingCaption" xml:space="preserve">
    <value>Registering session configuration</value>
  </data>
  <data name="ERemotingQuery" xml:space="preserve">
    <value>The session configuration "{0}" was not found. Running command "{1}" to create the "{0}" session configuration. Running this command restarts the WinRM service.</value>
  </data>
  <data name="ShowUIAndSDDLCannotExist" xml:space="preserve">
    <value>"{0}" and "{1}" parameters cannot be specified together. Specify either "{0}" or  "{1}" parameter.</value>
  </data>
  <data name="UseSharedProcessCannotBeFalseForWorkflowSessionType" xml:space="preserve">
    <value>The SharedHost attribute cannot be set to false on a workflow session type configuration.</value>
  </data>
  <data name="RestartWinRMMessage" xml:space="preserve">
    <value>This operation might restart the WinRM service. Do you want to continue?</value>
  </data>
  <data name="IPCUnknownNodeType" xml:space="preserve">
    <value>Cannot process an element with node type "{0}". Only {1} and {2} node types are supported.</value>
  </data>
  <data name="IPCInsufficientDataforElement" xml:space="preserve">
    <value>Not enough data is available to process the {0} element.</value>
  </data>
  <data name="IPCWrongAttributeCountForDataElement" xml:space="preserve">
    <value>Expected only two attributes with the names "{0}" and "{1}" in the {2} element.</value>
  </data>
  <data name="IPCOnlyTextExpectedInDataElement" xml:space="preserve">
    <value>Node type "{0}" is unknown in the {1} element. Only the "{2}" node type is expected in the {1} element.</value>
  </data>
  <data name="IPCWrongAttributeCountForElement" xml:space="preserve">
    <value>Expected only one attribute with the name "{0}" in the {1} element.</value>
  </data>
  <data name="IPCUnknownElementReceived" xml:space="preserve">
    <value>An unknown element "{0}" was received. This can happen if the remote process closed or ended abnormally.</value>
  </data>
  <data name="IPCSupportsOnlyDefaultAuth" xml:space="preserve">
    <value>The specified authentication mechanism "{0}" is not supported. Only "{1}" is supported for this operation.</value>
  </data>
  <data name="IPCWowComponentNotPresent" xml:space="preserve">
    <value>The "{0}" executable file was not found. Verify that the WOW64 feature is installed.</value>
  </data>
  <data name="IPCServerProcessReportedError" xml:space="preserve">
    <value>The background process reported an error with the following message: {0}.</value>
  </data>
  <data name="IPCServerProcessExited" xml:space="preserve">
    <value>The background process closed or ended abnormally.</value>
  </data>
  <data name="IPCErrorProcessingServerData" xml:space="preserve">
    <value>There is an error processing data from the background process. Error reported: {0}.</value>
  </data>
  <data name="IPCUnknownCommandGuid" xml:space="preserve">
    <value>Data for an inactive command with the identifier {0} was received. Received data: {1}.</value>
  </data>
  <data name="IPCNoSignalForSession" xml:space="preserve">
    <value>A {0} message to a session is not supported. A {0} message can be sent only to a command.</value>
  </data>
  <data name="IPCSignalTimedOut" xml:space="preserve">
    <value>The client did not receive a response for a signal operation in the specified time interval. This can happen when a command is not responding to a Stop message in a timely manner.</value>
  </data>
  <data name="IPCCloseTimedOut" xml:space="preserve">
    <value>The client did not receive a response for a Close operation in the specified time interval. This can happen when a command is not responding to a Stop message in a timely manner.</value>
  </data>
  <data name="IPCExceptionLaunchingProcess" xml:space="preserve">
    <value>An error occurred while starting the background process. Error reported: {0}.</value>
  </data>
  <data name="ThrottlingJobChildAlreadyRunning" xml:space="preserve">
    <value>The ThrottlingJob.AddChildJob method accepts only child jobs in the NotStarted state.</value>
    <comment>{StrContains="ThrottlingJob.AddChildJob"}
{StrContains="NotStarted"}</comment>
  </data>
  <data name="ThrottlingJobChildAddedAfterEndOfChildJobs" xml:space="preserve">
    <value>The ThrottlingJob.AddChildJob method cannot be called after a call to the ThrottlingJob.EndOfChildJobs method.</value>
    <comment>{StrContains="ThrottlingJob.AddChildJob"}
{StrContains="ThrottlingJob.EndOfChildJobs"}</comment>
  </data>
  <data name="ThrottlingJobStatusMessage" xml:space="preserve">
    <value>{0}/{1} completed</value>
    <comment>{0} is a placeholder for a number of completed child jobs
{1} is a placeholder for a total number of child jobs</comment>
  </data>
  <data name="NestedPipelineMissingRunspace" xml:space="preserve">
    <value>Invoking a nested pipeline requires a valid runspace.</value>
  </data>
  <data name="JobSourceAdapterError" xml:space="preserve">
    <value>A {1} job source adapter threw an exception with the following message: {0}</value>
  </data>
  <data name="PSVersionParameterOutOfRange" xml:space="preserve">
    <value>The value {0} is not valid for the {1} parameter. The available values are 2.0, 3.0, 4.0, 5.0, 5.1.</value>
    <comment>{StrContains="2.0"} {StrContains="3.0"}</comment>
  </data>
  <data name="BlockCannotBeUsedWithKeep" xml:space="preserve">
    <value>The Wait and Keep parameters cannot be used together in the same command.</value>
  </data>
  <data name="WriteEventsCannotBeUsedWithoutWait" xml:space="preserve">
    <value>The WriteEvents parameter cannot be used without the Wait parameter.</value>
  </data>
  <data name="PowerShellNotInstalled" xml:space="preserve">
    <value>Windows PowerShell {0} is not installed. Install Windows PowerShell {0}, and then try again.</value>
  </data>
  <data name="JobManagerRegistrationConstructorError" xml:space="preserve">
    <value>The following type cannot be instantiated because its constructor is not public: {0}.</value>
  </data>
  <data name="JobSourceAdapterNotFound" xml:space="preserve">
    <value>The job operation (Create, Get, or Remove) could not be performed because the JobSourceAdapter type specified in the JobDefinition is not registered. Register the JobSourceAdapter type either by using an explicit call, or by calling the Import-Module cmdlet, and then specifying an assembly.</value>
  </data>
  <data name="NewJobSpecificationError" xml:space="preserve">
    <value>The job could not be created because the JobInvocationInfo does not contain a JobDefinition. Start the JobInvocationInfo with a JobDefinition.</value>
  </data>
  <data name="InvalidJobStateSpecific" xml:space="preserve">
    <value>The state of the current job instance is {0}. This state is not valid for the attempted operation. {1}</value>
  </data>
  <data name="JobConnectFailed" xml:space="preserve">
    <value>Unable to connect job "{0}" to the remote server.</value>
  </data>
  <data name="RunspaceDisconnectFailed" xml:space="preserve">
    <value>The Disconnect-PSSession operation failed for runspace Id = {0}.</value>
  </data>
  <data name="RunspaceConnectFailed" xml:space="preserve">
    <value>The connect operation failed for session {0}. The Runspace state is {1} instead of Opened.</value>
  </data>
  <data name="RunspaceQueryFailed" xml:space="preserve">
    <value>The Disconnected PSSession query failed for computer "{0}".</value>
  </data>
  <data name="RunspaceCannotBeConnected" xml:space="preserve">
    <value>Cannot connect PSSession "{0}", either because it is not in the Disconnected state, or it is not available for connection.</value>
  </data>
  <data name="RunspaceCannotBeConnectedForVMContainerSession" xml:space="preserve">
    <value>Session connect is not supported for PSSession "{0}" on target "{1}" because the target computer type is "{2}".</value>
  </data>
  <data name="RunspaceCannotBeDisconnected" xml:space="preserve">
    <value>Cannot disconnect PSSession "{0}" because it is not in the Opened state.</value>
  </data>
  <data name="RunspaceCannotBeDisconnectedForVMContainerSession" xml:space="preserve">
    <value>Session disconnect is not supported for PSSession "{0}" on target "{1}" because the target computer type is "{2}".</value>
  </data>
  <data name="RunspaceCannotBeReceivedForVMContainerSession" xml:space="preserve">
    <value>Receive-PSSession does not support PSSession "{0}" on target "{1}" because the target computer type is "{2}".</value>
  </data>
  <data name="JobActionInvalidWithNullChild" xml:space="preserve">
    <value>The command cannot finish because the ChildJobs property contains a value that is not valid.</value>
  </data>
  <data name="JobSuspendNotSupported" xml:space="preserve">
    <value>Cannot suspend the job that has an ID of {0}. Suspending jobs is not supported for some job types. For more information about support for suspending jobs, see the Help topic for the job type.</value>
  </data>
  <data name="JobResumeNotSupported" xml:space="preserve">
    <value>Cannot resume the job that has an ID of {0}. Resuming jobs is not supported for some job types. For more information about support for resuming jobs, see the Help topic for the job type.</value>
  </data>
  <data name="AsJobAndDisconnectedError" xml:space="preserve">
    <value>You cannot use the Invoke-Command cmdlet with both the AsJob and Disconnected parameters in the same command.</value>
  </data>
  <data name="QueryForRunspacesFailed" xml:space="preserve">
    <value>The remote session query failed for {0} with the following error message: {1}</value>
  </data>
  <data name="JobIdNotYetAssigned" xml:space="preserve">
    <value>Attempted to create a job with ID {0}. A job with this ID cannot be created now. Verify that the ID has already been assigned once on this computer.</value>
  </data>
  <data name="JobSessionIdLessThanOne" xml:space="preserve">
    <value>Cannot create a job with an ID of {0}; this is not a valid ID. Provide an integer for the job ID that is greater than 0.</value>
  </data>
  <data name="JobIdentifierNull" xml:space="preserve">
    <value>The JobIdentifier provided must not be null. Please provide a valid JobIdentifier.</value>
  </data>
  <data name="InvokeDisconnectedWithoutComputerName" xml:space="preserve">
    <value>No computer names or connection Uris were specified.  You must provide a computer name or connection Uri when invoking a command with the -Disconnected switch.</value>
  </data>
  <data name="JobBlockedSoWaitJobCannotContinue" xml:space="preserve">
    <value>The Wait-Job cmdlet cannot finish working, because one or more jobs are blocked waiting for user interaction.  Process interactive job output by using the Receive-Job cmdlet, and then try again.</value>
  </data>
  <data name="RemoveRunspaceNotConnected" xml:space="preserve">
    <value>Remote session {0} could not be connected and could not be removed from the server. The client remote session object will be removed from the server, but the state of the remote session on the server is unknown.</value>
  </data>
  <data name="RunspaceDisconnectFailedWithReason" xml:space="preserve">
    <value>Disconnect-PSSession operation failed for runspace Id = {0} for the following reason: {1}</value>
  </data>
  <data name="StopJobNotConnected" xml:space="preserve">
    <value>Job "{0}" could not be connected to the server and so could not be stopped.</value>
  </data>
  <data name="SessionIdMatchFailed" xml:space="preserve">
    <value>The command cannot find a PSSession with an InstanceId value of "{0}".</value>
  </data>
  <data name="SessionNameMatchFailed" xml:space="preserve">
    <value>The command cannot find a PSSession that has the name "{0}".</value>
  </data>
  <data name="WinPERemotingNotSupported" xml:space="preserve">
    <value>Windows PowerShell remoting is not supported in the Windows Preinstallation Environment (WinPE).</value>
  </data>
  <data name="WinRMRequiresRestart" xml:space="preserve">
    <value>Changes made by {0} cannot take effect until the WinRM service is restarted.</value>
  </data>
  <data name="WinRMRestartWarning" xml:space="preserve">
    <value>{0} may need to restart the WinRM service if a configuration using this name has recently been unregistered, certain system data structures may still be cached. In that case, a restart of WinRM may be required.
All WinRM sessions connected to Windows PowerShell session configurations, such as Microsoft.PowerShell and session configurations that are created with the Register-PSSessionConfiguration cmdlet, are disconnected.</value>
  </data>
   <data name="WinRMForceRestartWarning" xml:space="preserve">
    <value>You are running in a remote session and have selected the Force option which means the WinRM service may restart.If the WinRM service restarts then this remote session will be terminated and you will need to create a new session to continue</value>
  </data>
  <data name="JobSourceAdapterCannotSaveNullJob" xml:space="preserve">
    <value>The job was null when trying to save identifiers. Specify a job to save its identifiers.</value>
  </data>
  <data name="NoPowerShellForJob" xml:space="preserve">
    <value>A running command could not be found for this PSSession.</value>
  </data>
  <data name="NetFrameWorkV2NotInstalled" xml:space="preserve">
    <value>The Microsoft .NET Framework 2.0, which is required for Windows PowerShell 2.0, is not installed. Install the .NET Framework 2.0 and retry.</value>
  </data>
  <data name="PipelineFailedWithoutReason" xml:space="preserve">
    <value>The remote pipeline failed.</value>
  </data>
  <data name="PipelineFailedWithReason" xml:space="preserve">
    <value>The remote pipeline failed for the following reason: {0}</value>
  </data>
  <data name="ResumeJobInvalidJobState" xml:space="preserve">
    <value>One or more jobs could not be resumed because the state was not valid for the operation.</value>
  </data>
  <data name="RemoteHostNullClientHost" xml:space="preserve">
    <value>No client computer was specified for the remote runspace that is running a client-side method.</value>
  </data>
  <data name="DisableRemotingShouldProcessTarget" xml:space="preserve">
    <value>Name: {0} SDDL: {1}. This denies remote access to this session configuration.</value>
  </data>
  <data name="SetEnabledFalseTarget" xml:space="preserve">
    <value>Enabled: False. This configures the WS-Management service to deny the connection request.</value>
  </data>
  <data name="SetEnabledTrueTarget" xml:space="preserve">
    <value>Enabled: True. This configures the WS-Management service to accept the connection request.</value>
  </data>
  <data name="PSJobProxyInvalidReasonException" xml:space="preserve">
    <value>Reason in a deserialized Job object is not valid.</value>
  </data>
  <data name="DISCAliasDefinitionsComment" xml:space="preserve">
    <value>Aliases to be defined when applied to a session</value>
  </data>
  <data name="DISCAssembliesToLoadComment" xml:space="preserve">
    <value>Assemblies to load when applied to a session</value>
  </data>
  <data name="DISCAuthorComment" xml:space="preserve">
    <value>Author of this document</value>
  </data>
  <data name="DISCCLRVersionComment" xml:space="preserve">
    <value>Version of the CLR to use when applied to a session</value>
  </data>
  <data name="DISCCompanyNameComment" xml:space="preserve">
    <value>Company associated with this document</value>
  </data>
  <data name="DISCCopyrightComment" xml:space="preserve">
    <value>Copyright statement for this document</value>
  </data>
  <data name="DISCDescriptionComment" xml:space="preserve">
    <value>Description of the functionality provided by these settings</value>
  </data>
  <data name="DISCEnvironmentVariablesComment" xml:space="preserve">
    <value>Environment variables to define when applied to a session</value>
  </data>
  <data name="DISCExecutionPolicyComment" xml:space="preserve">
    <value>Execution policy to apply when applied to a session</value>