Topic: My registry changes for improving Windows XP Sp3 on our network

[purvis]

I thought that I would post some of the changes to our registry for Windows XP PRO SP3 workstations.
I am not suggesting others to use these settings but they maybe these setting may be of interest for other people.
We are accessing SAM type databases on a shared directory of a SME 8.1 server with multiple workstations and multiple users.

Code: [Select]

Windows Registry Editor Version 5.00
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\RemoteComputer\NameSpace\{D6277990-4C6A-11CF-8D87-00AA0060F5BF}]

[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\MyComputer\NameSpace\DelegateFolders\{59031a47-3f72-44a7-89c5-5595fe6b30ee}]

[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\RemoteComputer\NameSpace\{2227A280-3AEA-1069-A2DE-08002B30309D}]


[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer]
"NoRecentDocsNetHood"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib]
"Disable Performance Counters"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSMQ\Parameters]
"TCPNoDelay"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSMQ\Parameters\Security]
"SecureDSCommunication"=dword:00000000

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\AFD\Parameters]
"DefaultReceiveWindow"=dword:0000ffff
"DefaultSendWindow"=dword:0000ffff
"FastSendDatagramThreshold"=dword:000005dc
"FastCopyReceiveThreshold"=dword:000005dc

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters]
"EnableSecuritySignature"=dword:00000000
"RequireSecuritySignature"=dword:00000000
"SizReqBuf"=dword:00004470
"Size"=dword:00000002

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters]
"MaxCollectionCount"=dword:00000064
"MaxThreads"=dword:00000064
"MaxCmds"=dword:00000064
"EnableSecuritySignature"=dword:00000000
"RequireSecuritySignature"=dword:00000000
"ScavengerTimeLimit"=dword:00000001
"DisableByteRangeLockingOnReadOnlyFiles"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MRxSmb\Parameters]
"CscEnabled"=dword:00000000


[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]
"DefaultTTL"=dword:00000040
"MaxConnectiondelsPerServer"=dword:00000000
"TcpWindowSize"=dword:0000ffff
"GlobalMaxTcpWindowSize"=dword:0000ffff
"DefaultWindowSize"=dword:0000ffff
"Tcp1323Opts"=dword:00000001
"SackOpts"=dword:00000000
"TcpMaxDupAcks"=dword:00000002
"EnablePMTUBHDetect"=dword:00000001
"EnablePMTUDiscovery"=dword:00000001
"TCPNoDelay"=dword:00000001
"DisableTaskOffload"=dword:00000001


[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Performance]
"Disable Performance Counters"=dword:00000001


also under the [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Performance\{yournetworkinterace}]
I have these two setting.

Code: [Select]

"TcpDelAckTicks"=dword:00000001
"TcpAckFrequency"=dword:00000001



[purvis]

Code: [Select]

Also I suggest turning off Opportunity Oplocks on the workstations where again you are accessing shared database files with the SMB/CIFS/SAMBA protocols.

[code
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MRxSmb\Parameters]
"OplocksDisabled"=dword:00000001

Where turning off Oplocks has decreased performance to an extreme undesirable effect on certain routines.
We have those routines run only on a single machine where Oplocks is allowed and tune the SME server's SAMBA settings
of veto oplocks to not allow certain files to be accessed in a Oplock state.


For Windows OS above XP, meaning Vista, Windows 7, and Windows 8.1
In my testing, if SMB version 1 is used to access the SME shared files. By making the above setting. It will turn off Oplocks for files on a SME server if the Samba is set to allow files only with the SMB1 protocol while preserving Oplocks to other connections where SMB2 is the protocol used.

Now Microsoft has started using the word Lease with SMB2 and up rather than Oplock.

Oplock is where a client makes use of file cache on the workstation with files opened on a network SMB share.
This is typically bad where networked type files are opened in a shared state where a write to an open shared file takes place.

[purvis]

On all network devices in Windows.
We are turning off any Green setting under the network card setting if they are found listed.

On Vista, Windows 7, Windows 8.1.
We are also turning off any setting under the network card that have to do with Large Task Send offload.
We use VNC a lot and these settings have been helpful in performance on our Window machines too.
These setting can be found under properties of the device manager.

These setting may not be for best for other net environment setups.

Once again, our machines make use of a lot of networked database file sharing.

[stephdl]

Hi Purvis

May I suggest You to set up a wiki Page to share your setup

for example you could do a page Windows_8_Support:trick_registry and Windows_7_Support:trick_registry

[purvis]

stephdl

There is much information on the internet and to many different setups.
The operating system operator will have to test things to find what works better.
I am not sure you can ever find what works the best just better on network parameters.
Microsoft has scattered the setting in so many different areas of the registry and even dropped settings,
moved,  and even renamed setting.

I am no expert and I am even sure Microsoft is.

[purvis]

I have not tested much on Windows Vista.
There are plenty of performance tweaks listed on the internet.
Where tweaks from the internet are given for Vista, I have applied any that seem to work on Windows 7 and/or 8.

For releasing open files on a server where oplocks are concerned.
The files are closed only after a specific number of seconds if oplocks is turned on unless you specify those files with "veto oplocks" in samba on the sme server.
Oplocks are turned on by default on a newly installed Windows NT OS.



Under HKLM\System\CurrentControlSet\Services\LanmanWorkstation\Parameters.
-----------------------------------------------------------------------------
ScavengerTimeLimit will have no effect on windows 7 or 8., not tested under Vista.
I have found CacheFileTimeout to have the similar affects of  ScavengerTimeLimit in Windows XP.

DisableBandwidthThrottling maybe worth setting also.

[Stefano]

vista "doesn't exist"
XP is  EOL
we should look to W7 and W8

[purvis]

XP is has matured.
Windows 8 is just getting out of the crib.
Windows 7 is I only have one on a test machine.
Windows XP is running on 100 machines here. Maybe EOL but not End of Usefulness.

[stephdl]

XP is has matured.
......Maybe EOL but not End of Usefulness.

Hi Purvis

I cannot state on window's registry hack, it is really not my cup of tea, but I feel that the wiki is always the good place to save informations and allow others to enhance it. If you are not sure, You can add warnings. Of course it is just my 2C, have a good day