From a1d240b26deba162327dd6fc9906e8befc03a928 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=E8=B0=AD=E4=B9=9D=E9=BC=8E?= <109224573@qq.com>
Date: Sat, 29 Nov 2025 21:19:43 +0800
Subject: [PATCH] Remove SMB server configuration command

that option doesn't exist
---
 .../file-server/enable-insecure-guest-logons-smb2-and-smb3.md | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/WindowsServerDocs/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3.md b/WindowsServerDocs/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3.md
index e3acea347b..079f87f88d 100644
--- a/WindowsServerDocs/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3.md
+++ b/WindowsServerDocs/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3.md
@@ -85,10 +85,6 @@ Run the following command through an elevated PowerShell prompt:
 Set-SmbClientConfiguration -EnableInsecureGuestLogons $true -Force
 ```
 
-```powershell
-Set-SmbServerConfiguration -EnableInsecureGuestLogons $true -Force
-```
-
 ---
 
 Both SMB signing, and SMB encryption policies must be disabled in Group Policy in order to use guest logons. Doing so can potentially compromise the security of the client and leave users open to credential theft and relay attacks.