AFAIR there weresome for Workstation, but the server ones were the important ones.
But even if the registry settings are corrected, they can be reset to bad values during MS updates
"optimizing" your machine. As security gets beefed up all the time, checking those settings from a vfp app
is a PITA, as server should be off limits to the app ;-)


>What is not clear to me in all this documentation, when it comes to registry changes, are they to be done on the workstations or on the server or both?
>
>>Try this thread and sub-posts:
>>
>>http://www.levelextreme.com/DataEntryThreadView.aspx?ID=1430067
>>
>>Also, Google for - disable smb2 - to turn it off is a registry entry change
>>
>>
>>>Many thanks Thomas.
>>>
>>>Any link to "SMB2 for the rest of us"? :)
>>>
>>>
>>>>>After I read this ... ftp://ftp.alaska-software.com/documents/OPLocking-Overview.pdf and knowing that most of our "writes" are done under a transaction both in dbc/dbf and jet databases, is it just me, or should I be worried. We've been running in Vista and Windows 7 for some time without any remarkable problems.
>>>>>
>>>>>Thanks for any light you could shed on this.
>>>>
>>>>If you have write heavy multi-user tables, this will touch you - but you should not be worried about your data, mostly for perf.
>>>>Read up on SMB2 on those newer OS to give you even more stomach acid - this time on data itself.