Share via

3.1.4.2.11 Receiving an EfsRpcNotSupported Message (Opnum 11)

  • Article

On receiving the EfsRpcNotSupported method call, an EFSRPC server SHOULD implement the EfsRpcNotSupported method as specified in this section and return a nonzero value. However, a server MAY<44> choose to interpret and respond to the arguments as specified in section 3.1.4.2.13.

 DWORD EfsRpcNotSupported(
   [in] handle_t binding_h,
   [in, string] wchar_t* Reserved1,
   [in, string] wchar_t* Reserved2,
   [in] DWORD dwReserved1,
   [in] DWORD dwReserved2,
   [in, unique] EFS_RPC_BLOB* Reserved,
   [in] BOOL bReserved
 );

binding_h: This is an RPC binding handle parameter, as specified, in [C706] and in [MS-RPCE] section 2.

Reserved1: This parameter is not used. It MUST be set to an empty string by the client and ignored by the server.

Reserved2: This parameter is not used. It MUST be set to an empty string by the client and ignored by the server.

dwReserved1: This parameter is not used. It MUST be set to zero by the client and ignored by the server.

dwReserved2: This parameter is not used. It MUST be set to zero by the client and ignored by the server.

Reserved: This parameter is not used. It MUST be set to NULL by the client and ignored by the server.

bReserved: This parameter is not used. It MUST be set to FALSE by the client and ignored by the server.

Return Values: The EFSRPC server SHOULD return a nonzero value. However, the server MAY<45> process this as described in section 3.1.4.2.13.