From c55f4780fab5dc0c7435804642466060b36c6bd3 Mon Sep 17 00:00:00 2001
From: omry99 <43474808+omry99@users.noreply.github.com>
Date: Thu, 3 Jul 2025 23:42:39 +0300
Subject: [PATCH] Removed "Set-SmbServerConfiguration
 -EnableInsecureGuestLogons" command

EnableInsecureGuestLogons  is not a parameter of Set-SmbServerConfiguration (only of Set-SmbClientConfiguration), as can  be seen here https://learn.microsoft.com/en-us/powershell/module/smbshare/set-smbserverconfiguration?view=windowsserver2025-ps
---
 .../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 c1e2d6a0ec..5e00d1042d 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.