Network Speed Suggestions

1. Op_locks

This is without a question the most common culprit for errors(90/07) and speed issues as it relates to RTA, and unfortunately Microsoft has it turned on by default on both the server side and client machines. RTA needs this turned "OFF"!!!!!! If you only disable it on the Workstations then any time a new workstation that does not have OpLocks Disabled attaches to the RTA Fleet folder it will re-enable OpLocks for every PC accessing RTA. The easiest way is to disable OpLocks on the server. If you are  using Server 2012 or newer you cannot disable Oplocks but you can force SMB1. (See Below for registry settings)  How to Disable OPLOCKS

2. Virus Scanning Software

You need to make sure that any virus scanning software (either on server or from the client machine) is excluding the files and file extensions below in the Fleet directory from active virus scans. If we have to wait every time you go back into a module to check all the static program files then you might be waiting for upwards of 10 to 15 seconds or more;

*.rta = RTA Database file

*.cob = RTA Cobol Executable

*.rpx = RTA/RPV Report temporary file

*.txt = RTA Report temporary file

*.tmp = RTA Report temporary file

After your upgrade to 7.0 you will need to please add the following specific new 7.0 files to your Antivirus Exclusions list as well. If you do not exclude these files you may run into an “AutoIT- Unable to run script” error attempting to run RTA.exe. They are all in the root of the \Fleet folder;


Activity.exeAlfred.exeDashboard.exeDriverInsp.exeDriverKiosk.exeEmailDshbrd.exeMechInsp.exeMseLClick.exe
NAPAppts.exePapShop.exeScheduler.exerta.exerta_wrun32.exerun32.exeVehStatus.exewrun32.exe


After upgrading to SQL and RTA 7.1.1 you can drop the .rta file extension and only add the following files to the exclusions list;

pullwin.rtasysconfg.rtasyshost.rtasysinit.rta

3. Network Protocols

Check to make sure your client machine doesn't have more protocols turned on then necessary. If you have multiple protocols turned on but the network only uses one primarily at the server level then it tries to navigate each one until it makes the connection.

4. Nework Speed

You may want to disable all power saving features on the NICs themselves. If the PC/Server is powering down the Network Card when the system goes to sleep or is idling with RTA still open and the user comes back then RTA may be looking for an IP path has not been re-established fully from sleep mode and may cause additional slowness while RTA is trying to re-establish its connection to the server. If using WiFi make sure you are using 801.1N protocol or better and are your broadcasting /receive frequency is set to maximum output. The Faster the network connection the better RTA will run.

5.TCP/IP Verson 6.0

Windows 7 and Server 2008 and above have TCP/IP Version 6.0 turned on by default and if you are using an older server you won't have Version 6.0 on it.  This protocol should be disabled if your network doesn’t utilize it.

If your IT person has questions they can email us in support@rtafleet.com or they can call our 800-279-0549 number and ask for Tech Support.

P.S. Please make sure with the Op-Lock Registry settings that your IT person verifies the settings. We have had more follow-up calls where the Op-Locks were supposedly done and were not. It is that important!

Update: I know that Microsoft recently released some patches that re-enabled IPV6 and Oplocks. If you do not lock down Oplocks at the server, I would go back to each workstation and ensure that it is still turned off. Since the release of Windows 10, MS has released multiple patches to make the move to 10 more readily available. Some of those recent patches also re-enable Oplocks on workstations because MS is moving away from SMB1 and moving towards SMB3.1. It might behoove you to make sure all workstations have OpLocks disabled. Remember, any workstation that connects to RTA and does not have OpLocks disabled will cause all workstations to work as if OpLocks is enabled until all workstations have been rebooted at the same time. This is a MS standard operational behavior.

SMB and Opportunistic Locking Info and Settings

Here's how SMB is used when related to SMB versions:

  1. When a Window Server 2012 or newer connects to a 2008/2008R2/Vista/Windows7,8,10 “client” SMB 3/3.1 is used.
  2. When a Windows Server 2008/2008R2/Vista/ Windows7,8,10 "client" connects to a Windows Server 2008/2008R2/Vista/Windows7 "server", SMB 2.1 is used.
  3. When a Windows Server 2008/2008R2/Vista/ Windows7,8,10 "client" connects to a Windows 2000/XP/2003 "server", SMB 1.0 is used.
  4. When a Windows 2000/XP/2003 "client" connects to a Windows Server 2008/2008R2/Vista "server", SMB 1.0 is used.
  5. When a Windows 2000/XP/2003 "client" connects to a Windows 2000/XP/2003 "server", SMB 1.0 is used.

XP and Windows Server 2003 only do SMB 1.0 (Oplocks1), but 2008/2008R2/2012//Vista /Windows7,8, 10 can do either SMB 1.0, 2.0, 2.1, 3 depends on the server O/S, See above.

Websites for additional information about OpLocks

https://support.microsoft.com/en-us/kb/2696547

http://www.danieletosatto.com/2010/11/08/provisioning-services-and-cifs-stores-tuning-for-performance/

Workstation/Client Registry settings:Windows XP and above

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanWorkstation\Parameters]

     EnableOplocks=dword:00000000

[HKEY_LOCAL_MACHINE \SYSTEM\CurrentControlSet\services\LanmanWorkstation\Parameters]

     Smb2 = dword:0×00000000

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MRXSmb\Parameters]

     OplocksDisabled=dword:00000001


When Op-Locks are changed you need to reboot the machine and physically check the registry entries to make sure OPLock is off:

Server Settings you want to use:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters

     EnableOplocks REG_DWORD 0

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters

     Smb2 REG_DWORD 0

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MRXSmb\Parameters\

     OplocksDisabled REG_DWORD 1

Forcing SMB1 on Server 2012/14 SMB2/3 and newer

Use Powershell and run these commands:

Set-SmbServerConfiguration -EnableSMB2Protocol $false

Set-SmbServerConfiguration -EnableSMB1Protocol $true

Set-SmbServerConfiguration -EnableOplocks $false

Server 2012 SMB2/3 Registry Edits:

Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer

     Key - "DependOnService" needs to be set to SamSS Srv

Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\mrxsmb10

     Key - "DependOnService" needs to be set to mrxsmb

Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\mrxsmb20

     Key - "DependOnService" needs to be set to mrxsmb

Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters

     Key - “DisableLeasing" needs to be set to 1

RDP Server 2012/14 Registry Edits:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters

     Key - dword - "FileInfoCacheLifetime"=dword:00000000

     Key - dword - "FileNotFoundCacheLifetime"=dword:00000000

     Key - dword - "DirectoryCacheLifetime"=dword:00000000

Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\mrxsmb20

     Key - "DependOnService" needs to be set to mrxsmb



Search