Adagio and Terminal Services

Transcription

1 This document will describe some best practices to follow when installing Modules in a Terminal Server Environment. First, let s look at a Basic Network configuration as shown in Diagram 1: Basic Network Diagram 1 Network Printer Data Flow Workstation install required For EACH module For Each Station (and Each User*) File Server Data Network Desktop / Laptop Workstations Network Firewall * If multiple Users share the same station using different Logons This configuration is characterized by: 1. All programs and Data reside on the File Server s drive 2. Backup is centralized on the File Server 3. data travels across the network to each user station on demand 4. Hard copy Report printing is achieved through any or all of the following a) Shared Network printer b) Shared local printer c) Private (non-shared) local printer Installation A workstation install is required for each module on each workstation. If two or more users sharing the same workstation (different logins), then workstation install(s) must be performed for each user for each module -TerminalServer.DOC Page 1 of 8

2 Diagram 2a shows the Basic network with a Windows Server 2003 Terminal Server This configuration is characterized by: 1. All programs and Data still reside on the File Server s drive 2. Backup is centralized on the File Server 3. data travels across the network to each user station on demand 4. data travels across the network to the Terminal server on demand 5. Hard copy Report printing is achieved through any or all of the following d) Shared Network printer e) Shared local printer f) Private (non-shared) local printer Installation Network Stations A workstation install is required for each module on each workstation. If two or more users sharing the same workstation (different logins), then workstation install(s) must be performed for each user for each module -TerminalServer.DOC Page 2 of 8

3 Windows 2003 Terminal Server Clients A workstation install is required for each module for each USER who is connection to the terminal server, regardless of which client station they use. Note the following: 1. When installing from a Terminal Server Client, it is no longer a requirement to use the Control Panel Add/Remove Programs facility just install as normal 2. Prior to doing the workstation install(s), each user MUST be temporarily added to the Domain Admin group, or the Terminal Server s local Administrators group. When the Workstation installs are complete, remove the User from the Domain Admin or Administrators group -TerminalServer.DOC Page 3 of 8

4 Diagram 2b shows a variant of the Basic network with a Windows Server 2003 Terminal Server Basic and Terminal Services Network Diagram 2b Network Printer Workstation install required For EACH module For Each Station (and Each User*) File Server Data Flow Network Desktop / Laptop Workstations * If multiple Users share the same station using different Logons Other Data Network Firewall Terminal Server Workstation Install For each Module For each USER Data ** ** Ensure your daily backup process includes the Data files!!! Terminal Server Clients This configuration is characterized by: 1. All programs and Data reside on the Terminal Server s drive 2. Other Data reside on the File Server s drive 3. Backup must be performed on the File Server and the Terminal Server 4. data travels across the network to each user station on demand 5. data is on the local drive for all Terminal Server users thus no network traffic this would improve performance for the Accounting Department, while still providing access to data for other users 6. Hard copy Report printing is achieved through any or all of the following g) Shared Network printer h) Shared local printer i) Private (non-shared) local printer Installation Network Stations A workstation install is required for each module on each workstation. -TerminalServer.DOC Page 4 of 8

5 If two or more users sharing the same workstation (different logins), then workstation install(s) must be performed for each user for each module Windows 2003 Terminal Server Clients A workstation install is required for each module for each USER who is connection to the terminal server, regardless of which client station they use. Note the following: 1. When installing from a Terminal Server Client, it is no longer a requirement to use the Control Panel Add/Remove Programs facility just install as normal 2. Prior to doing the workstation install(s), each user MUST be temporarily added to the Domain Admin group, or the Terminal Server s local Administrators group. When the Workstation installs are complete, remove the User from the Domain Admin or Administrators group -TerminalServer.DOC Page 5 of 8

6 Diagram 3a shows scenarios for excellent Remote Access Excellent Remote Access Diagram 3a File Server Data (if Not on Terminal Server) Network Printer Network Firewall Data Flow (File Server Based) Remote Control Path To Terminal Server (No Data) Data Flow Terminal Server Based Terminal Server (Optional) Data (if NOT on File Server) Remote Control Path To User s Desktop Station (No Data) In Office Out of Office Travelling Laptop or Home Desktop This configuration reflects Diagram 1, 2a or 2b with remote access via the internet added. Configuration Issues for the Remote Units 1. The external Laptop or Home desktop DO NOT require any installation. 2. They should be configured to securely connect via the internet (using a VPN tunnel or equivalent) to the Terminal Server (if present) or the user s in office Desktop unit and use an appropriate remote control technology (such as Microsoft s Remote Desktop Connection) to initiate a session on the Terminal Server or In Office workstation. Thus only screen changes, Keyboard and Mouse clicks are sent across the - all data is kept on the normal office network 3. Even if the laptop has modules installed for use when in the office, connect to an In Office Terminal Server or Workstation, and use a remote control program to launch on the In Office unit see Diagram 3b (next). -TerminalServer.DOC Page 6 of 8

7 Diagram 3b shows scenarios for VERY POOR Remote Access Poor Remote Access Diagram 3b Network Printer File Server Data (if NOT on Terminal Server) Terminal Server Data (if NOT on File Server) In Office Network Firewall Out of Office Data Flow ( Traffic requirements too high, performance VERY slow) Travelling Laptop or Home Desktop with Installed This configuration reflects Diagram 1, 2a or 2b with remote access via the internet added. In addition: 1. modules have been installed on the Out of Office units Laptop or Home Desktop. 2. The remote stations connect to the office internet, then launch from their LOCAL unit, thus causing all the data to be transferred across the WHY this should NEVER be done 1. First of all speed data rates across the internet are far slower than on a wired (or wireless) office network - so you will find that response ranges from excruciatingly slow on downward. 2. Second data integrity internet connections are notoriously unreliable and can unexpectedly drop at any time for a variety of reasons. If this occurs during a posting then your Database files will be corrupted. -TerminalServer.DOC Page 7 of 8

8 Diagram 4 shows a scenario which is NOT recommended Unsupported Configuration Diagram 4 depicts a network where Terminal Services has been installed on the file Server itself. At first glance this may seem like a reasonable option, however it is NOT recommended by Softrak or Microsoft [see ]: 1. A Terminal Server is emulating 1 or more workstations running interactive programs be they, or Office Productivity suites, access etc. Because of their interactive nature, they tend to be computing intensive. 2. A File Server on the other hand is typically running a variety of non-interactive tasks, such as securely storing and retrieving data, providing access security, acting as a Domain Controller, performing anti-virus scans, managing the database and so on. These functions tend to be (mostly) disk intensive, but with processor spikes 3. Combining these functions into one unit puts an undue load on the file server resources, and can cause processes to fail during peak activity loads thus leading to data corruption or worse a complete server failure. Given today s cost of hardware, putting all your eggs in one basket does not make sense from a reliability perspective a failed file server means the entire organization is stopped. -TerminalServer.DOC Page 8 of 8