Sage 100

1. Change the default printer to another physical or network printer and then test/check the performance
   1. Sage 100 Advanced and Premium looks at the default printer on the server every time a task is launched.
   2. Sage 100 Standard edition checks the workstation's default printer.
   3. Make sure all Network Printers are on-line
   4. If a Network Printer is off-line and no longer needed, remove it from Control Panel, Devices and Printers
2. Check the path
   1. For Sage 100 Standard, Workstation Setup should be installed from a mapped drive letter path, such that the shortcut to launch Sage 100 also has the mapped drive letter path. The drive letter must be mapped to a directory above "MAS90"
   2. For Sage 100 Advanced or Premium, Workstation Setup should be installed from a UNC path, such that the shortcut to launch Sage 100 also has the UNC path. The UNC share point must be a directory above "MAS90"
3. Check that the latest Sage Anti-Virus setting exclusions have been applied
4. Consider temporarily disabling anti-virus and malware scans
   1. This is trickier than it should be - and may require uninstalling and rebooting the server
5. Consider setting Sage 100 so that the shortcut always "runs as administrator"
6. Check ping times for Advanced/Premium
   1. PING servername -l 1800 ( Note the -l is lowercase letter L ) 
   2. Anything over 40 ms is slow and may be cause for further investigation
7. Turn off the Sage Product Enhancement Program
   1. Login to Sage as Administrator
   2. Select Sage Product Enhancement Program
   3. Deselect "Participate in the Program" by removing the checkmark
8. Never run Sage over WiFi without use of RDP or Terminal Server/Citrix
   1. Customers may refer to this as "using a VPN" but the VPN does NOT act as a remote desktop
   2. Customers running solely over WIFI or the Internet with RDP will see most pronounced slowdowns in printing

1. Change the default printer to another physical or network printer and then test/check the performance
   1. Sage 100 Advanced and Premium looks at the default printer on the server every time a task is launched.
   2. Sage 100 Standard edition checks the workstation's default printer.
   3. Make sure all Network Printers are on-line
   4. If a Network Printer is off-line and no longer needed, remove it from Control Panel, Devices and Printers
2. Check the path
   1. For Sage 100 Standard, Workstation Setup should be installed from a mapped drive letter path, such that the shortcut to launch Sage 100 also has the mapped drive letter path. The drive letter must be mapped to a directory above "MAS90"
   2. For Sage 100 Advanced or Premium, Workstation Setup should be installed from a UNC path, such that the shortcut to launch Sage 100 also has the UNC path. The UNC share point must be a directory above "MAS90"
3. Check that the latest Sage Anti-Virus setting exclusions have been applied
4. Consider temporarily disabling anti-virus and malware scans
   1. This is trickier than it should be - and may require uninstalling and rebooting the server
5. Consider setting Sage 100 so that the shortcut always "runs as administrator"
6. Check ping times for Advanced/Premium
   1. PING servername -l 1800 ( Note the -l is lowercase letter L ) 
   2. Anything over 40 ms is slow and may be cause for further investigation
7. Turn off the Sage Product Enhancement Program
   1. Login to Sage as Administrator
   2. Select Sage Product Enhancement Program
   3. Deselect "Participate in the Program" by removing the checkmark
8. Never run Sage over WiFi without use of RDP or Terminal Server/Citrix
   1. Customers may refer to this as "using a VPN" but the VPN does NOT act as a remote desktop
   2. Customers running solely over WIFI or the Internet with RDP will see most pronounced slowdowns in printing

1. Change the default printer to another physical or network printer and then test/check the performance
   1. Sage 100 Advanced and Premium looks at the default printer on the server every time a task is launched.
   2. Sage 100 Standard edition checks the workstation's default printer.
   3. Make sure all Network Printers are on-line
   4. If a Network Printer is off-line and no longer needed, remove it from Control Panel, Devices and Printers
2. Check the path
   1. For Sage 100 Standard, Workstation Setup should be installed from a mapped drive letter path, such that the shortcut to launch Sage 100 also has the mapped drive letter path. The drive letter must be mapped to a directory above "MAS90"
   2. For Sage 100 Advanced or Premium, Workstation Setup should be installed from a UNC path, such that the shortcut to launch Sage 100 also has the UNC path. The UNC share point must be a directory above "MAS90"
3. Check that the latest Sage Anti-Virus setting exclusions have been applied
4. Consider temporarily disabling anti-virus and malware scans
   1. This is trickier than it should be - and may require uninstalling and rebooting the server
5. Consider setting Sage 100 so that the shortcut always "runs as administrator"
6. Check ping times for Advanced/Premium
   1. PING servername -l 1800 ( Note the -l is lowercase letter L ) 
   2. Anything over 40 ms is slow and may be cause for further investigation
7. Turn off the Sage Product Enhancement Program
   1. Login to Sage as Administrator
   2. Select Sage Product Enhancement Program
   3. Deselect "Participate in the Program" by removing the checkmark
8. Never run Sage over WiFi without use of RDP or Terminal Server/Citrix
   1. Customers may refer to this as "using a VPN" but the VPN does NOT act as a remote desktop
   2. Customers running solely over WIFI or the Internet with RDP will see most pronounced slowdowns in printing

1. Change the default printer to another physical or network printer and then test/check the performance
   1. Sage 100 Advanced and Premium looks at the default printer on the server every time a task is launched.
   2. Sage 100 Standard edition checks the workstation's default printer.
   3. Make sure all Network Printers are on-line
   4. If a Network Printer is off-line and no longer needed, remove it from Control Panel, Devices and Printers
2. Check the path
   1. For Sage 100 Standard, Workstation Setup should be installed from a mapped drive letter path, such that the shortcut to launch Sage 100 also has the mapped drive letter path. The drive letter must be mapped to a directory above "MAS90"
   2. For Sage 100 Advanced or Premium, Workstation Setup should be installed from a UNC path, such that the shortcut to launch Sage 100 also has the UNC path. The UNC share point must be a directory above "MAS90"
3. Check that the latest Sage Anti-Virus setting exclusions have been applied
4. Consider temporarily disabling anti-virus and malware scans
   1. This is trickier than it should be - and may require uninstalling and rebooting the server
5. Consider setting Sage 100 so that the shortcut always "runs as administrator"
6. Check ping times for Advanced/Premium
   1. PING servername -l 1800 ( Note the -l is lowercase letter L ) 
   2. Anything over 40 ms is slow and may be cause for further investigation
7. Turn off the Sage Product Enhancement Program
   1. Login to Sage as Administrator
   2. Select Sage Product Enhancement Program
   3. Deselect "Participate in the Program" by removing the checkmark
8. Never run Sage over WiFi without use of RDP or Terminal Server/Citrix
   1. Customers may refer to this as "using a VPN" but the VPN does NOT act as a remote desktop
   2. Customers running solely over WIFI or the Internet with RDP will see most pronounced slowdowns in printing

From reading some of the thread linked below, it appears that this is an issue with the File Cache Manager (FCM) in Server 2019. 

This appears to be a kernel level change that Microsoft has no plans to fix in this version of Windows (at least according to the thread). 

On the link below (Page 5, around mid way down), you will find a few powershell commands that revert some values back to 2016 levels. Not sure if it will make a difference, but probably worth a shot. 

https://community.spiceworks.com/topic/2225989-server-2019-network-performance?page=5&pagination=5

The good news is that this may not be Sage specific. The bad news is... oh no! Deploying 2019 might have just become an expensive ordeal.. or skip it altogether (risky when it comes to considering EOL OS support from Microsoft)

From reading some of the thread linked below, it appears that this is an issue with the File Cache Manager (FCM) in Server 2019. 

This appears to be a kernel level change that Microsoft has no plans to fix in this version of Windows (at least according to the thread). 

On the link below (Page 5, around mid way down), you will find a few powershell commands that revert some values back to 2016 levels. Not sure if it will make a difference, but probably worth a shot. 

https://community.spiceworks.com/topic/2225989-server-2019-network-performance?page=5&pagination=5

The good news is that this may not be Sage specific. The bad news is... oh no! Deploying 2019 might have just become an expensive ordeal.. or skip it altogether (risky when it comes to considering EOL OS support from Microsoft)

From reading some of the thread linked below, it appears that this is an issue with the File Cache Manager (FCM) in Server 2019. 

This appears to be a kernel level change that Microsoft has no plans to fix in this version of Windows (at least according to the thread). 

On the link below (Page 5, around mid way down), you will find a few powershell commands that revert some values back to 2016 levels. Not sure if it will make a difference, but probably worth a shot. 

https://community.spiceworks.com/topic/2225989-server-2019-network-performance?page=5&pagination=5

The good news is that this may not be Sage specific. The bad news is... oh no! Deploying 2019 might have just become an expensive ordeal.. or skip it altogether (risky when it comes to considering EOL OS support from Microsoft)

From reading some of the thread linked below, it appears that this is an issue with the File Cache Manager (FCM) in Server 2019. 

This appears to be a kernel level change that Microsoft has no plans to fix in this version of Windows (at least according to the thread). 

On the link below (Page 5, around mid way down), you will find a few powershell commands that revert some values back to 2016 levels. Not sure if it will make a difference, but probably worth a shot. 

https://community.spiceworks.com/topic/2225989-server-2019-network-performance?page=5&pagination=5

The good news is that this may not be Sage specific. The bad news is... oh no! Deploying 2019 might have just become an expensive ordeal.. or skip it altogether (risky when it comes to considering EOL OS support from Microsoft)