1. Go to and modify the key: HKLM\Software\Policies\Microsoft\Windows NT\Terminal Services\Client with the following values:
   • Name: RedirectionWarningDialogVersion
   • Type: REG_DWORD
   • Data: 1

reg add "HKLM\software\policies\microsoft\windows nt\Terminal Services\Client" /v RdpLaunchConsentAccepted /d 1 /t REG_DWORD

reg add "HKLM\software\policies\microsoft\windows nt\Terminal Services\Client" /v RedirectionWarningDialogVersion /d 1 /t REG_DWORD

Get-Mailbox | ForEach-Object {   $mailbox = $_.PrimarySmtpAddress
Get-InboxRule -Mailbox $mailbox | Select-Object @{Name="Mailbox";Expression={$mailbox}}, Name, Description } | Export-Csv -Path "<OutputFile>" -NoTypeInformation -Append –Force 

https://admindroid.com/how-to-manage-inbox-rules-in-exchange-online

Legacy applications connecting to Windows shares

For legacy applications that need to access file shares on your Windows server, Microsoft suggests configuring those shares with leasing mode using the -LeasingMode None parameter in PowerShell commands like New-SmbShare or Set-SmbShare. This makes the Windows server’s shares behave like SMBv1 (without modern features like oplocks and leases) while still using the more secure SMBv2 or SMBv3 protocols.

Here is an example:

# Create a new share compatible with legacy applications

New-SmbShare -Name “LegacyApp” -Path “C:\LegacyData” -LeasingMode None

# Or modify an existing share

Set-SmbShare -Name “ExistingShare” -LeasingMode None

This allows legacy applications to connect successfully without requiring the vulnerable SMBv1 protoco

https://4sysops.com/archives/windows-september-updates-break-smbv1-shares-workarounds-and-user-feedback/l.

Get-WindowsCapability -Name “Print.Management.Console*” -Online | Add-WindowsCapability -Online

diskshadow

delete shadows all

1. regedit
2. Go to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\OOBE.
3. New > DWORD (32-bit) >BypassNRO.
4. Set its value data to 1.
5. Restart your system

Steps to Bypass Microsoft Account Setup
https://github.com/the-P1neapple/WinJS-Microsoft-Account-Bypass

1. Start Windows 11 Setup

• Begin the Windows 11 Setup Process.
• Select your region and keyboard layout.

2. Stop at the Secondary Keyboard Layout Screen

• When you reach the Secondary Keyboard Layout screen, do not click Skip.
• If you accidentally skipped and reached the Network Setup Screen, don’t stress. I have a guide in the troubleshooting section.

3. Open the Developer Console

• Press Ctrl + Shift + J to open the Developer Console.
• Your screen will go dark and will appear with a prompt (indicated by a > symbol) at the top left of the screen.

4. Enter the Restart Command

• Type the following command exactly as shown:WinJS.Application.restart(“ms-cxh://LOCALONLY”)

Note: This command is case-sensitive. You can use Tab-completion to help:

• After typing WinJS.A, press Tab to auto-complete Application.
• After typing res, press Tab to auto-complete restart.

5. Exit the Developer Console

• After entering the command, press Enter to execute it.
• Press Escape to exit the Developer Console and return to the OOBE interface.

Note: If the Escape key doesn’t close the Console, click anywhere on the screen to ensure the console is focused and then press the key again.

6. Local Account Setup

• The Secondary Keyboard Layout screen will refresh, and a Windows 10-style local account setup screen will appear.
• Enter your desired username, password, and security questions and click Next.

7. Complete the Setup

• The Setup will go black and will then log you in to your newly created account. Allow Windows 11 a few moments to configure the user.
• Continue with the remaining privacy setting prompts.
• Once finished, you will have successfully created a local account in Windows 11.

And another

Shift + F10
regedit
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\OOBE\
HideOnlineAccountScreens 1

Computer Configuration>Administrative Templates>Network>Lanman Workstation

Enabled: Enable insecure guest logons
Disable: Require encryption

Then

Disable SMB Signing:

Set-SmbClientConfiguration -RequireSecuritySignature $false
Set-SmbServerConfiguration -RequireSecuritySignature $false

Reboot

Also good to check with

Get-SmbClientConfiguration

takeown /R /A /F foldername /D N

icacls foldername /grant Administrators:F /T /C

explorer shell:::{A8A91A66-3A7D-4424-8D24-04E180695C7A} 

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power]
“PlatformAoAcOverride”=dword:00000000

Reboot