Hello Tom,

The current issue with the data corruption in this case was not related to the SMB settings but an issue with a newly changed feature within Adagio Payables related to a
batch optional field feature that is now being used. When system checks were run, the integration setup with the GL caused the posting to fail and data corruption to occur.
This has since been corrected and is no longer an issue.

During the course of the investigation we discuss the network configuration and setup. It was identified that Windows 10 and windows 7 machines were both connected via LAN to the new server. At that time I indicated that in this environment I suggested backing the SMB settings back to SMB2 as I and other dealers had seen disconnect issues under these circumstances (despite Andrew's assertions that "Generally, Adagio works with MS products as configured out of the box").

Your client had experienced data integrity errors on the older server and the new. In most cases the DIC errors were related to a network disconnect from the workstation to the server (most commonly in the accounts payable office). The SMB changes were simply a suggested "best practice" I and other Adagio dealers follow. I agree would be good if I could provide you detailed specs on server and network environments from Softrak, but these are simply not available.

As you know I have long suggest you move this client and RDP Sever for all users to avoid the LAN and the issues this client has been experiencing. The SMB issue would be not be a concern if we transitioned to the RDP environment.