- 1. Create a share SMBBasic
It's basic file share to test SMB2 cases.
a. Create a share SMBBasic on node01.
b. Share with read/write access to Admin User.
- 2. Create a share with Encrypt data enabled
It's used to test Encryption feature of SMB2 protocol.
a. Create share SMBEncrypted on node01.
b. Share with read/write access to Admin User.
c. Enable share folder with Encrypt data which indicates that the server requires messages for accessing this share to be encrypted.
- 3. Create a share with Oplock Force Level 2 enabled
It's used for some cases when testing Oplock feature of SMB2 protocol.
a. Create a share ShareForceLevel2 on node01.
b. Share with read/write access to Admin User.
c. Enable FORCE_LEVELII_OPLOCK on this share.
- 4. Create a share SameWithSMBBasic
It's used for some negative cases when testing AppInstanceId feature of SMB2.
If AppInstanceId is not supported, this section can be ignored.
Add a share named SameWithSMBBasic, this share should have the same local path with SMBBasic share.
Summary of the negative cases:
a. The case creates an open under the share SMBBasic. There's an AppInstanceId in the Create Request.
b. The case sends a second Create Request to SUT with the same AppInstanceId.
c. Verify the open is not closed if the case uses this share SameWithSMBBasic, not share SMBBasic.
- 5. Create a share different from SMBBasic
It's used for some negative cases when testing AppInstanceId feature of SMB2.
If AppInstanceId is not supported, this section can be ignored.
a. Create a share named DifferentFromSMBBasic on node01. The local path of this share should be different from SMBBasic share.
b. Share with read/write access to Admin User.
- 6. Create Symbolic Links
It's used for some negative cases when testing Create/Close feature of SMB2. Details see section 3.3.5.9 in [MS-SMB2].
If AppInstanceId is not supported, this section can be ignored.
a. Add a Symbolic Link to SMBBasic
In share SMBBasic, add a symbolic link named Symboliclink, which links to SMBBasic.
b. Add a new folder Sub under SMBBasic, add another symbolic link named Symboliclink2 under Sub folder, and links to SMBBasic.
- 7. Create a share on volume supporting integrity
If integrity is not supported by file system, this section can be ignored.
The share is used to test IoCtl codes FSCTL_GET_INTEGRITY_INFORMATION and FSCTL_SET_INTEGRITY_INFORMATION.
a. Create a share named SMBReFSShare on node01.
The file system of the volume containing the specified share should support the use of integrity.
b. Share with read/write access to Admin User.
- 8. Modify the Signing configurations
If Signing is not supported by file system, this section can be ignored.
The configuration is used to test the Signing function.
In order to run Signing cases, you need to do:
a. Open the ptf config file under the location:
C:\MicrosoftProtocolTests\FileServer\Server-Endpoint\<version#>\Bin\MS-SMB2Model_ServerTestSuite.deployment.ptfconfig
b. If SigningRequired is enabled on SUT, set the property value of IsRequireMessageSigning to true in the above file.
c. If SigningRequired is disabled on SUT, set the property value of IsRequireMessageSigning to false in the above file.
If DFS is not supported, this part can be ignored.
If RSVD is not supported, this part can be ignored.
If SQOS is not supported, this part can be ignored.