If set, the client is requesting an oplock. This flag is as specified in [CIFS] section 4.2.1.

If set, the client is requesting a batch oplock. This flag is as specified in [CIFS] section 4.2.1.

If set, the client indicates that the target of the open is a directory. If the target does exist, it might require a delete access check for parent directory.

If set, the client is requesting extended information in the response.

Indicates the right to read data from the file or named pipe.

Indicates the right to write data into the file or named pipe beyond the end of the file.

Indicates the right to append data into the file or named pipe.

Indicates the right to read the extended attributes of the file or named pipe.

Indicates the right to write or change the extended attributes to the file or named pipe.

Indicates the right to execute the file.

Indicates the right to read the attributes of the file.

Indicates the right to change the attributes of the file.

Indicates the right to delete or to rename the file.

Indicates the right to read the security descriptor for the file or named pipe.

Indicates the right to change the discretionary access control list (DACL) in the security descriptor for the file or named pipe. For the DACL data structure, see ACL in [MS-DTYP].

Indicates the right to change the owner in the security descriptor for the file or named pipe.

SHOULD NOT be used by the sender and MUST be ignored by the receiver.

Indicates the right to read or change the system access control list (SACL) in the security descriptor for the file or named pipe. For the SACL data structure, see ACL in [MS-DTYP].

If the SE_SECURITY_NAME privilege is not set in the access token, the server MUST fail the open with STATUS_PRIVILEGE_NOT_HELD.

Indicates that the client is requesting an open to the file with the highest level of access that the client has on this file. If no access is granted for the client on this file, the server MUST fail the open with STATUS_ACCESS_DENIED.

Indicates a request for all the access flags that are previously listed except MAXIMAL_ACCESS and ACCESS_SYSTEM_SECURITY.

Indicates a request for the following combination of access flags listed previously in this table: FILE_READ_ATTRIBUTES| FILE_EXECUTE| SYNCHRONIZE| READ_CONTROL.

Indicates a request for the following combination of access flags listed previously in this table: FILE_WRITE_DATA| FILE_APPEND_DATA| FILE_WRITE_ATTRIBUTES| FILE_WRITE_EA| SYNCHRONIZE| READ_CONTROL.

Indicates a request for the following combination of access flags listed previously in this table: FILE_READ_DATA| FILE_READ_ATTRIBUTES| FILE_READ_EA| SYNCHRONIZE| READ_CONTROL.

When set, indicates that other opens are allowed to read this file while this open is present. This bit MUST NOT be set for a named pipe or a printer file. Each open creates a new instance of a named pipe. Likewise, opening a printer file always creates a new file.

When set, indicates that other opens are allowed to write this file while this open is present. This bit MUST NOT be set for a named pipe or a printer file. Each open creates a new instance of a named pipe. Likewise, opening a printer file always creates a new file.

When set, indicates that other opens are allowed to delete or rename this file while this open is present. This bit MUST NOT be set for a named pipe or a printer file. Each open creates a new instance of a named pipe. Likewise, opening a printer file always creates a new file.

If the file already exists, replace it with the file. If the file does not exist, create the file.

If the file already exists, open the file instead of creating a new file. If the file does not already exist, fail the request, and do not create a new file.

If the file already exists, fail the request, and do not create or open the file. If the file does not already exist, create the file.

If the file already exists, open the file. If the file does not already exist, create the file.

If the file already exists, open the file and overwrite it. If the file does not already exist, fail the request.

If the file already exists, open the file and overwrite it. If the file does not already exist, create the file.

The file being created or opened is a directory file. With this option, the CreateDisposition field MUST be set to FILE_CREATE, FILE_OPEN, or FILE_OPEN_IF. When this bit field is set, other compatible CreateOptions include only the following: FILE_WRITE_THROUGH, FILE_OPEN_FOR_BACKUP_INTENT, and FILE_OPEN_BY_FILE_ID.

Applications that write data to the file MUST actually transfer the data into the file before any write request is considered complete. If FILE_NO_INTERMEDIATE_BUFFERING is set, the server assumes that FILE_WRITE_THROUGH is set in the create request.

This option indicates that access to the file may be sequential. The server may use this information to influence its caching and read-ahead strategy for this file. The file may in fact be accessed randomly, but the server may optimize its caching and read-ahead policy for sequential access.

The file SHOULD NOT be cached or buffered in an internal buffer by the server. This option is incompatible when the FILE_APPEND_DATA bit field is set in the DesiredAccess field.

This flag MUST be ignored by the server, and clients SHOULD set this to 0.<51>

This flag MUST be ignored by the server, and clients SHOULD set this to 0.<52>

If the file being opened is a directory, the server MUST fail the request with STATUS_FILE_IS_A_DIRECTORY in the Status field of the SMB header in the server response.

This option SHOULD NOT be sent by the clients, and this option MUST be ignored by the server.

This option SHOULD NOT be sent by the clients, and this option MUST be ignored by the server.

The application that initiated the client's request does not understand extended attributes (EAs). If the EAs on an existing file being opened indicate that the caller SHOULD understand EAs to correctly interpret the file, the server SHOULD fail this request with STATUS_ACCESS_DENIED in the Status field of the SMB header in the server response.

This option SHOULD NOT be sent by the clients, and this option MUST be ignored if received by the server.

Indicates that access to the file may be random. The server may use this information to influence its caching and read-ahead strategy for this file. This is a hint to the server that sequential read-ahead operations may not be appropriate on the file.

The file SHOULD be automatically deleted when the last open request on this file is closed. When this option is set, the DesiredAccess field MUST include the DELETE flag. This option is often used for temporary files.

Opens a file based on the FileId. If this option is set, the server MUST fail the request with STATUS_NOT_SUPPORTED in the Status field of the SMB header in the server response.

The file is being opened or created for the purposes of either a backup or a restore operation. Thus, the server may make appropriate checks to ensure that the caller is capable of overriding whatever security checks have been placed on the file to allow a backup or restore operation to occur. The server may choose to check for certain access rights to the file before checking the DesiredAccess field.

When a new file is created, the file MUST not be compressed even it is on a compressed volume. The flag MUST be ignored when opening an existing file.

This option SHOULD NOT be sent by the clients, and this option MUST be ignored if received by the server.

If the file or directory being opened is a reparse point, this option requests that the server open the reparse point itself, rather than the target to which the reparse point points.

In a hierarchical storage management environment, this option requests that the file SHOULD NOT be recalled from tertiary storage such as tape. A file recall can take up to several minutes in a hierarchical storage management environment. The clients can specify this option to avoid such delays.

This option SHOULD NOT be sent by the clients, and this option MUST be ignored if received by the server.

The server cannot obtain identification information about the client, and it cannot impersonate the client.

The server can obtain security information about the client, such as security identifiers (SIDs) and privileges, but it cannot impersonate the client. This is useful for servers that export their own objects; for example, database products that export tables and views. Using the retrieved client-security information, the server can make access-validation decisions without being capable of using other services that are using the client's security context.

The server can impersonate the client's security context on the server system. The server cannot impersonate the client on other remote systems.

The server can impersonate the client's security context on the server system and on remote systems.

When set, dynamic tracking is requested. When this bit field is not set, static tracking is requested.

Specifies that only the enabled aspects of the client's security context are available to the server. If this flag is not specified, all aspects of the client's security context are available. This flag allows the client to limit the groups and privileges that a server can use while impersonating the client.