Windward Software Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
See also
[[https://support.windwardsoftware.com/en/support/solutions/articles/66000485987-remote-desktop-connection-guidelines]]

THIS DOCUMENT IS A GUIDELINE FOR A NETWORK ADMINISTRATOR PROVIDED BY WINDWARD AS A GUIDELINE TO SETUP 
STABLE WINDWARD ENVIRONMENT IN TERMINAL SERVICES 
WINDWARD IS NOT RESPONSIBLE FOR NETWORK SETUP 


The end product of proper TS usage for System5 is each physical machine logging into TS has its own forced terminal number to system5  using the forcmachine=X on the REMOTE-STNx’s Desktop.


===== Setup =====


* Each terminal needs to have their own unique login on the server. If each user has their own specific terminal at the remote location, then using their proper name would be sufficient. If multiple users are using a specific terminal, setup  users such as: REMOTE-STN1, REMOTE-STN2, etc. 

* For each of the individual TS Login accounts, one will need to set the parameters for the System Five shortcut on each accounts desktop so that they are unique (the main thing we are concerned about here is the station ID). We set parameters on the System Five shortcut so that the correct station ID is used. To set the parameters of the System Five shortcut, rt. click and choose properties.

{{ts-setup1.jpg|}}  {{ts-setup2.jpg|}}


/smallsplash - displays a small-splash screen upon loading System Five. Not necessary, but will speed up the login process over the remote connection

/forcemachine=X -  user is not able to change the terminal ID at the login screen for System Five**

The Start In parameter, f:\data\windward - This forces the user to only login to that particular data set. Can be useful if there are multiple data sets which have been linked in System Five, i.e. training data, etc.



Setup 2)

If you currently run a roaming profile TS with specific setup you consider using scripting user/group profiles that makes the desktop icon with a forcemachine parameter. 

THIS IS ONLY AN EXAMPLE AND IS UP TO YOU TO HAVE YOUR ADMINISTRATOR CREATE THE PROPER SCRIPT WE DO NOT WORK ON NETWORK CUSTOMIZATION

You should be able to use the wscript.network object and get the
computername.

set objNetwork=CreateObject("wscript.network")
if objNetwork.computername="TERMINAL" then
'map drives or whatever
end if







Setup 3)

Using the “remote desktop connection” to launch the software with the proper parameters

Setup a remote desktop icon on each physical machines desktop that opens TS specifically launching System Five with the forcemachine option 

{{ts.jpg|}}






===== PRINTING IN TERMINAL SERVICES =====
 

The easiest way to print in Terminal Services is to setup a VPN and use windows printer sharing, which also makes it easy to transfer and setup drivers on the server.  This ensures that the printer names do not change on the server so that System Five printing preferences do not break, if you prefer to use TS printing you must make sure the printer names are not dynamic if
Printer1 session1 changes to session2 printing will break.  

With the forced machines being specific to the station and the static named printing we ensure System Five Hardware preferences do not break.

===== Do not run PIN Pads over Wireless Terminal Services networks =====

 Ensure your a not running your PINPAD over wireless. We support Terminal Services via wireless, because there is not data being transmitted, just screen and keyboard, however PINPADs transmit data. Wireless networks will drop or delay data much more often than wired networks.