Hello Al,

Thanks for the feedback.

My app is accessible through remote desktop. Do you suggest I do those changes right away on my Windows Server 2016 or should I wait to see if I have problems?

>>I read over here that there could be problems running VFP apps on windows server 2012 or windows server 2008. Is it the same with Windows server 2016?
>>
>>I didn't read a lot so I'm not sure what the deal is in those cases where there's an SMB problem. Could you please tell me what would be a cure for that problem and give me informations so I can really understand why this is happening?
>
>Back in the early days of Windows Vista, an issue was found where Vista workstations talking to server computers via the (then-new) SMB2 protocol caused index corruption in native VFP tables under some circumstances.
>
>The best information I've seen is this is caused by certain default networking settings in workstation computer registries. Changing these values in the Registry on all workstations that run VFP apps against shared native data greatly reduces or eliminates this issue.
>
>Note: these changes do NOT have to be applied to servers, unless the VFP apps run locally on the server console, or the server is a Remote Desktop Server (formerly Terminal Server) and runs VFP apps within sessions/desktops.
>
>The Registry settings are explained at http://www.alaska-software.com/community/smb2.cxp . It used to be possible to download an MSI installer to make these changes, I don't know if Alaska Software still has that publicly available. If not you can make the changes in Regedit, or create a .reg file.
>
>The various versions of SMB present in Windows versions can be found at https://en.wikipedia.org/wiki/Server_Message_Block . The changes for Server 2016 look incremental, I wouldn't expect any difference from VFP's point of view from, say, Server 2012 R2. And again, the Registry changes are mainly for workstations.