Network Install Guide

Transcription

1 131 Hartwell Avenue Lexington, MA (800) Network Install Guide Overview and Installation Information for Wrightsoft Right-Suite Universal Network Version 1 Introduction 1.1 Wrightsoft Files Types 1.2 Network Types 1.3 Floating Licenses 2 File Locations 2.1 Program File Location 2.2 Data File Location 2.3 Project File Location 2.4 License File Location 3 Installation 3.1 Installation Requirements 3.2 File Server Installation Overview 3.3 Terminal Services Installation Overview 3.4 Reinstalling 4 Custom Configurations and Support 5 Typical Uses and Installation Examples 5.1 Sales Team and Supervisor 5.2 College Campus with File Server 5.3 One-Man Band with Peer-to-Peer Network 5.4 Terminal Services Network Group 1 Introduction Nearly every small business has multiple computers with some level of internal network and many are connected to the Internet via permanent connections. Microsoft and other manufacturers have made networking the most common and accessible way to connect computers together and hardware to do so via Ethernet or via wireless has become so inexpensive that any cost barriers have been eliminated. Keeping identical software synchronized and updated on separate computers is itself a maintenance headache, and networking software can help to reduce that maintenance. Also, in situations where multiple people need to share information, a network is the only real path to make sharing convenient. Wrightsoft has developed a networking capability for Right-Suite Universal that can function in several ways. This memo describes how Wrightsoft s software can work on a File Server or Terminal Services type network. 1 of 12

2 1.1 Wrightsoft File Types There are four types of files stored either on a server (shared) or on a workstation (not shared): File Type Description Program files Executable files these files run in RAM. Data files Weather data, proposal database, libraries, and others. Project files HVAC system designs, one file per project. Licensing files Manage module and concurrent user licensing. 1.2 Network Types There are two basic kinds of networks serviced by Wrightsoft s network configurations: File Server, in which one computer serves as a central file server, and Wrightsoft s software runs on each Windows workstation. The central file server can be one of several operating systems, although Windows Server is our only tested system to date. In this arrangement, programs actually run in the RAM of each workstation, and the server can be a central depository for project files, libraries, databases, and license control. This type of network uses the server only to store data, and not to operate programs. Even if the programs are stored on the server, they are loaded over the network to the workstation, and then operated in the RAM of the workstation. This type of network system requires that each workstation must have enough power to run Wrightsoft applications. Please refer to the System Requirements on the Wrightsoft web site for details. Terminal Services, in which all programs run in the RAM of the Windows Server using Microsoft s Terminal Services program, and the workstations are just screen display and entry devices. A workstation is used to display the screen of a virtual PC, which is really in the server. That is, each workstation is allocated RAM in the server and programs actually run in the server RAM. The network is used to send keyboard and mouse inputs and screen display information back and forth, but all the workstation does is to display the screen of the virtual PC in the server. This configuration requires a minimum workstation computer and a maximum server computer. The workstation is frequently a Windows PC, with a special Terminal Services Client software that shows the desktop of the virtual PC on the workstation. Terminal Services systems usually store all files on the server. Citrix operating system is another Terminal Services network type. Wrightsoft has tested Windows Terminal Services, but not Citrix. However, several Wrightsoft customers are using Citrix systems. 1.3 Floating Licenses In all network configurations, Wrightsoft s licensing is centralized, and uses the floating license idea. In this approach, the number of simultaneous users is tracked by the server, and is limited to the number of purchased licenses. Floating licenses operate in either Terminal Services or Server/Workstation networks. For example, a company might have 20 workstations, and has purchased a five-user license so that their five person sales team might use Right-Suite Universal from any of the 20 workstations, depending on where they happen to be in the company. Right-Suite Universal would allow any combination of (up to) five simultaneous users, regardless of which five of the 20 workstations were used. Whether used in a campus environment, where there may literally be hundreds of workstations, or in a single-license world, in which a designer roams around the building, it s very convenient to install Wrightsoft s floating license system. 2 of 12 November 20, 2007

3 2 File Locations 2.1 Program File Location For File Server networks, Wrightsoft s program files can be stored either on each workstation, or on the server. When programs are installed on the server, they must load over the network, which causes a few seconds delay in program startup, but once they have loaded into the workstation RAM, the program functions with the same speed as a locally stored program. The advantage of central program location on the server is simpler maintenance. If program files are stored on the server, one installation of a service pack automatically updates every workstation because workstations only run programs stored on the server. Sharing program files will: Insure that all users are running the same version of the program. Reduce the total amount of hard drive space required to run the program on several computers. Simplify installing service packs. When you update the server, all of the workstations are updated. The advantage of installing programs on workstations is faster program loading. If the network and server cannot load the workstation fast enough, then the program must be installed on the workstations. In both cases, data and project files can be stored with total flexibility wherever needed. In both cases, workstation capabilities are identical, since programs run in the workstation RAM. NOTE: Do not choose to share program files to laptops or other computers that will not always be attached to the network. In such cases, you will want to install as a single computer with a standalone license and not use the network install option. Speak with your sales representative if you have any questions about which license you have purchased. For Terminal Services installations, programs are stored and run on the server. This system also has the benefit of simpler maintenance, with the added benefit of fast load times. The principal trade-off is that, since all programs run in the same server RAM, the server itself has to have enough RAM to easily accommodate the required number of users, without degrading individual workstation performance. Of course, the major advantage of Terminal Services installations is the reduced cost and longer useable life of the workstation computers, which do not need to have as much power as the File Server network systems. 2.2 Data File Location You can choose to share data files when you want all users get the same results when using Right- Suite Universal on the same project. If users have different copies (when they are stored locally) of the databases or libraries, they may obtain different results for pricing, calculations, takeoffs, and proposal data for the same project, resulting in confusion and perhaps incorrect information. There are several kinds of data used by Right-Suite Universal, and these are: Program libraries, such as weather data, or proposal databases. These files are usually stored centrally, but can also be stored locally if necessary. Templates, which are usually stored centrally for common use. Wrightsoft s network version supports file locking, so that the first user to open a file locks out other users for writing to the file until the first user is done. The second and higher users can open files as read-only. For example, if when Jim runs the program, he can make changes to the proposal database 3 of 12 November 20, 2007

4 file in a shared configuration, other users will only be able to open that file in read-only mode. Once Jim has exited from the program, then others may re-run the program and edit the proposal database. This system prevents users from losing changes that others may make. In most network installations, Wrightsoft recommends all data files are stored centrally. 2.3 Project File Location When several program users need to be able to view each other s projects, then using a central project file area will be very useful. Even though users may use different sub-folders, the fact that project files are in the same data area on the server will make it easy for them to view each other s work. There may be times when storing projects on workstations is desirable. In the File Menu, a user can open and save project files anywhere on the network or on their own workstation. This system provides enough flexibility to roam the network as required. File locking is especially valuable when using a central project file area, since project files are constantly being opened and updated. For example, if Jim opens a project, no one else may open or view the project. When Jim makes changes and saves the project, the project can be opened by someone else. 2.4 License File Location Normally, the network license files are located on the server, regardless of what other components are on the server or on workstations. You can override this behavior and store the licensing somewhere else. For example, a very large network might have separate workgroups at different physical sites with each site connected to one another. In this situation, each site can install the program and other data files on their local server but store the licensing to a server that is available to all of the sites. 3 Installation 3.1 Installation Requirements You should be familiar with general network administration operations. Users need to have read, write, and create permissions to every folder that the program uses even if the files are read only. When installed, all folders are relative to the Server Root Folder. You select this folder when you install the shared files onto the server. The system clocks for the server and workstations need to be set to the same date and time. Before you begin installing, you should take a moment to plan which files you want to share between all users and which you want to be unique to each user. If a previous (non-network) version of the program is installed on a workstation, it should be uninstalled before performing a network installation. 3.2 File Server Installation Overview There are three steps to installing to a File Server network: 1. Install shared files to the network server. 2. Install non-shared files to each workstation and 'attach' each workstation to the network installation. 3. Install licensing from one workstation. Once you have decided which files you want to share, you can proceed with the installation. You will need to run the install program once to install the shared files to the server and once for each workstation that 4 of 12 November 20, 2007

5 you want to have access to the program. You can install the shared files to the server from a workstation as long as the workstation has write privileges to the server's drive. You must install the non-shared files at each workstation, however. When you uninstall the shared files, you must do so from the same workstation that you used to install Installing the Shared Files to the File Server 1. Put the Wrightsoft program CD in the drive on the server or a workstation that has write privileges to the server's drive. 2. When the install program starts, select Network and click Next. 3. Select Install to a Network Server and click Next. 4. If you want to store licensing files on the same server as the shared files, select Typical. If you want to store licensing files on a different server, select Custom. Click Next. 5. Select the files that you want to share. Check the ones you want to share and un-check the ones you do not want to share. 6. Enter the complete drive and path where the shared files are to be copied and click Next. This is the Server Root Folder. Note that users need read, write, and create permission to this directory even if the files are read only. 7. If you selected Custom in Step 4 above, enter the complete drive and path where the license files are to be stored. Click Next. 8. You can copy the workstation installation files to the server so that you do not have to use the CD to install each workstation. The advantage of doing this is that it makes installing to workstations much easier. The disadvantage is that the files use up space on your server's drive. If you do not copy the installation files to the server, you can still install the workstations using the CD. Select whether you want to copy the workstation installation files to the server and click Next. 9. If you elected to copy the workstation installation files to the server, you can either install the entire installation program as it appears on the CD or just the 'stub' installation program that will install from the Internet. It is important to note the name and location of the workstation installation shortcut. If you are installing to the server from the Internet, the Internet install will be copied to the server. This relatively small program will download the files that need to be installed during the workstation install. If you elect to install to the workstation using this method, keep in mind that the workstation will need access to the Internet during the install. You can elect to copy the entire installation as well. If you are installing to the server from a CD, the entire installation will be copied to the server. Click Next. 10. When network-related errors occur, a message will be displayed with Administrator contact information so whoever is using the workstation knows who to contact to solve the problem. For example, if you are licensed for only 2 users, when a 3rd user runs the program, a message will be displayed explaining this. The Administrator will know how many licenses you have. Enter the Administrator name and contact information here and click Next. 5 of 12 November 20, 2007

6 11. Review the installation options that you have selected. If you want to change any, click Back until you get to the appropriate screen and make your changes. Then click Next until you get back to this summary screen. Click Do Install to copy the shared files to the server Installing Non-Shared Files to Each Workstation You may install to as many workstations that you wish. Your License Certificate will indicate the number of workstations that can run the program at the same time and this information is stored in the License. If you find that you need additional concurrent workstations, you can always add them by contacting your Sales Representative at (800) If you elected to copy the workstation installation files to the server, double click on the workstation install shortcut in the Workstation subfolder of the Server Root Folder. For example, for Right-Suite Universal, double click on <SRF>\Workstation\RSU_WrkStation where <SRF> is the Server Root Folder that you specified when you installed the shared files on to the server. If you did not elect to copy the workstation installation files to the server, put the CD in the drive at the workstation. When the install program starts, select Network and click Next. Select Attach Workstation to a Server Installation and click Next. 2. Enter the full drive and path where you installed the shared files on the server and click Next. 3. The next screen displays the directories for all the program components. You will not be able to change the directories for shared components. You can change the directories for nonshared components if you wish. Click Next to continue installing. 4. Select whether you want to add a shortcut to the Windows Desktop and click Next. 5. Adobe Acrobat Reader is required to view the User's Guide. If the workstation does not have Adobe Acrobat Reader installed or Adobe Acrobat Reader needs to be updated, you can elect to install it. If it is installed and does not need to be updated, this screen will not be displayed. Click Next to continue. 6. Review the installation options that you have selected. If you want to change any, click Back until you get to the appropriate screen and make your changes. Then click Next until you get back to this summary screen. Click Do Install to copy the non-shared files to the workstation. 7. Repeat the above instructions for each workstation Installing Licensing The licensing is installed the first time the program is run from any workstation and is installed only once. Once it is installed, it applies to all workstations. Wrightsoft uses a new Internet licensing system for activating and updating licenses. If you do not have an Internet connection, you will need to contact Wrightsoft Technical support at (800) (Option 1) and activate your license over the phone. 1. Run the program from any workstation. Select Help Licensing from the menu and the select the Activate License Using the Internet button to activate the program. 2. Complete the registration form and enter the Activation Key that is provided on your License Certificate. Review and accept the terms of the License Agreement and select Submit. 3. The program will now be licensed and the licensing will be transferred to the server and the program will continue to run normally. The licensing on the server applies to all workstations. 6 of 12 November 20, 2007

7 3.2.4 Uninstalling File Server To uninstall, you need to uninstall the workstations first and then uninstall the server. The licensing can be uninstalled when you uninstall a workstation Uninstall a Workstation 1. At the workstation, open the Windows Control Panel by selecting Start Settings Control Panel on the Windows task bar.) 2. Select Add/Remove Programs 3. Select the workstation install for the program. For example, for Right-Suite Universal, select Right-Suite Universal Workstation. 4. The uninstall program will ask if you want to uninstall the licensing. If you are just removing a workstation, but want to keep the rest of the installation intact, answer No. Otherwise, answer Yes. You can uninstall the licensing during any workstation uninstall. 5. The uninstall will then ask if you want to remove files. Answer Yes to remove all program files. Note that project files, the Proposal database, and any other file that users can modify, will not be uninstalled Uninstall the Server 1. At the same workstation where the server was installed from, open the Windows Control Panel by selecting Start Settings Control Panel on the Windows task bar.) 2. Select Add/Remove Programs 3. Select the server install for the program. For example, for Right-Suite Universal, select Right- Suite Universal Server. 4. The uninstall will ask if you want to remove files. Answer Yes to remove all program files. Note that project files, the Proposal database, and any other file that users can modify, will not be uninstalled. 7 of 12 November 20, 2007

8 3.3 Installing on Terminal Services Type Network There are three steps to installing to a Terminal Services type network: 1. Install as a standalone program on the Terminal Services Server. 2. Install licensing from the Terminal Services Server. 3. Configure Terminal Services Clients. Terminal Services lets users execute Windows-based applications on a remote Windows 2000-based server similar to a terminal-based, centralized host, or mainframe environment. It delivers the Windows 2000 Professional desktop and 32-bit Windows-based applications to diverse desktop platforms. Each terminal provides a conduit for input and output only between a user and a host computer. Applications are installed on the server. Workstations can then execute the installed applications Install the Program to the Terminal Services Server To enable each user to retain individual application settings, there must be a unique copy of the appropriate.ini files or registry entries so Terminal Services makes a copy of them from a common system location to each user as necessary. In order to do this, programs must be installed in 'Install Mode'. The easiest way to do this is to use 'Add/Remove Programs' in the Windows Control Panel. 1. Put the CD in the drive on the Terminal Services Server. Hold the <Shift> key down to prevent the install program from running automatically. 2. Select Start Settings Control Panel on the Windows task bar. 3. Select Add/Remove Programs. Select Add New Programs. 4. Click CD or Floppy 5. Click Next. It should find the install program on your CD drive (typically 'SetupWSF.exe'.) 6. Click Finish. 7. The Wrightsoft installation program will run. Select the Standalone installation option. 8. Click Next. Select the remaining installation options to your preference Installing Licensing The licensing is installed the first time the program is run from any terminal or server. Wrightsoft uses a new Internet licensing system for activating and updating licenses. If you do not have an Internet connection, you will need to contact Wrightsoft Technical support at (800) (Option 1) and activate your license over the phone. 1. Run the program from the terminal or server. Select Help Licensing from the menu and the select the Activate License Using the Internet button to activate the program. 2. Complete the registration form and enter the Activation Key that is provided on your License Certificate. Review and accept the terms of the License Agreement and select Submit. 3. The program will now be licensed and the licensing will be transferred to the server for use by all the terminals. 8 of 12 November 20, 2007

9 3.3.3 Configure Each User's Terminal The Start Menu entry and Desktop shortcut (if selected) are available to all terminals. When the Terminal Services session is started, the program can be run without additional installation. However, all components of the program will be shared among all users. If this is not what you would like, you need to configure each user and terminal manually. When the program is run from a terminal, Terminal Services will make a copy of the appropriate registry settings for the user that is logged in to the Terminal Services session. Create a directory in the Server computer s 'My Documents' directory for the program for each user. For example, create C:\Documents and Settings\username\My Documents\Wrightsoft HVAC. Replace username with the login name of the user. Be careful not to create 'C:\My Documents\Wrightsoft HVAC' To Set the Directory Where Projects are Saved If you want each user to save project files in their own directory: 1. Run the program from each terminal logged in as the user you want to configure. 2. Select File Save As from the menu. 3. Browse to the directory that you created (C:\Documents and Settings\ username\my Documents\Wrightsoft HVAC.) 4. Save the project. NOTE: The directory will not be saved unless you actually save the project To Set the Template Directory If you want each user to use their own templates for new projects: 1. Using Windows Explorer, copy the Template directory. For example, for Right-Suite Universal, this is usually C:\Documents and Settings\username\My Documents\Wrightsoft HVAC\Template. Replace username with the login name of whoever installed the program to the server. Select this directory and select Edit Copy from the menu. 2. Browse to the directory that you created (C:\Documents and Settings\ username\my Documents\Wrightsoft HVAC.) 3. Select Edit Paste from the menu. 4. Run the program. 5. Select File New New From Template from the menu. 6. Browse to C:\Documents and Settings\username\My Documents\Wrightsoft HVAC\Template and select a template. NOTE: The template directory will not be saved unless you actually create a new project. 3.4 Re-Installing If you need to re-install the network version, be sure to make the same selections during the second install that you made during the first install. Re-installing using different selections can cause the loss of changes you may have made to templates, weather data, the proposal database, etc. 9 of 12 November 20, 2007

10 4 Custom Configurations and Support Wrightsoft network versions support additional configurations not discussed in this document. Contact Wrightsoft Technical Support at (800) (Option 2) or at to discuss your needs and we will work with you to optimize your setup. 5 Typical Uses and Installation Examples 5.1 Sales Team and Supervisor Situation Overview Tom s company has three salesmen and one supervisor, and together they design HVAC systems for about 20 different builders, using a single company database for job quotations. They operate Windows 2000 Server with 12 PCs (File Server Type). Generally, the salesmen do all their work from their desktop, but occasionally they look at projects together in their conference room. The supervisor needs to be able to review each salesman s projects, and sometimes a salesman needs to be able to look over another salesman s work. How should they set up the network version of Wrightsoft s Right-Suite Universal? Wrightsoft Solution By installing a four-license network version of Right-Suite Universal, Tom s company can really make a team effort work smoothly. To minimize maintenance, Wrightsoft recommends installing Right-Suite Universal so that program files are stored on the server. This means that updates will only have to be done once, on the server, and all workstations will be automatically be running the latest version. The project data location should also be set to a central directory on the server, which may have subfolders for each builder. Tom should adopt a naming convention for project files, so that everyone uses the same names. For example, buildercode year projectnumber.ext might be a useable system. In a similar manner, a single central data location for libraries and databases is appropriate. All users will be able to change the contents of the Proposal database, with file locking enabled to prevent losing any modified records. By using a central location for templates, Tom s supervisor will be able to standardize system designs and embed preferences for different builders. Currently, templates follow the sharing of projects. If projects are shared during installation, then so are templates. Also, since five workstations will run Right-Suite Universal, the workstation installs will be done on those five workstations, and all installations will be the same. This insures that any user can move from workstation to workstation without changes Installation Notes Install to the server from the supervisor's workstation. This workstation becomes the 'host' workstation. During the Installation, select Network type, Server installation, and Typical installation. Share program, data, and projects to the same network server and copy workstation install files to the server. Install to the 'host' workstation. Run the workstation install from the server. Run the program and install the licensing. Install the program to the other three salesman's workstations and to the conference room workstation. 10 of 12 November 20, 2007

11 5.2 College Campus with File Server Situation Overview InDepth University has 125 PCs spread around 10 buildings, including the HVAC lab, which has 16 PCs used in the System Design course. The HVAC department has 6 instructors who prepare examples for classes from their office desktop. Students need their own project data areas, so that they can do their own work independently. The Campus Technology department wants to be able to maintain Right- Suite Universal on their central file server, without having to install on each workstation. Students want to be able to run Right-Suite Universal from their dorm rooms, and wish that they could move around from room to room. Can all of these people be happy with the network version of Right-Suite Universal? Wrightsoft Solution Yes, all these needs can be met by Right-Suite Universal s networking system. This File Server configuration is really not much different from the smaller installation described above. Wrightsoft recommends centralizing everything (licensing, program storage and data) except student project files. A 16-user license will handle the lab, which is probably the peak user requirement. The computers in the lab and in each instructor s office should be installed as workstations, with the program stored on the server. The IT department will need to create a batch file or link to the workstation install, so that students can install the program from their dorm rooms Installation Notes Install to the server from the IT supervisor's or instructor's workstation. This workstation becomes the 'host' workstation. During the Installation, select Network type, Server installation, and Typical installation. Share program, data, and projects to the same network server and copy workstation install files to the server. Install the program to the first instructor's workstation. Run the workstation install from the server and then run the program and install the licensing. Install to the other instructor's workstations and to the lab workstations. 5.3 One-Man Band With Peer-to-Peer Network Situation Overview Jerry runs a shop with three computers, and no server. He wants to be able to run Right-Suite Universal from any computer, and he wants the project files to be on his desktop computer. Jerry is using a Windows workgroup for his three computers to talk to each other via a simple hub and Ethernet connections. Can he set up Right-Suite Universal so that he can run around the office and access his files from any of the computers? 11 of 12 November 20, 2007

12 5.3.2 Wrightsoft Solution Yes, with a single-user network version. Jerry should designate the computer on his desktop as the server, and then centralize everything, including project files. As long as he closes the program when he s done using a machine, he can roam around and access files from each computer Installation Notes Share the hard drive on Jerry's desktop computer. Map this shared drive to a letter drive (Drive R for example.) Install as a server to Jerry's desktop computer. This computer becomes the 'host' workstation and server.. During the Installation, select Network type, Server installation, and Typical installation. Share program, data, and projects to a folder on the mapped drive R:. Copy the workstation installation files to the server. Install as a workstation to Jerry's desktop computer. Run the workstation install from the mapped drive R: and then run the program and install the licensing. At each of the other workstations, map the shared drive on Jerry's desktop to drive R: and run the workstation install from the mapped drive R:. 5.4 Terminal Services Network Group Situation Overview Accurate HVAC company has a sales and design group (8 salesmen plus a manager) using a single server and 15 workstations. The workstations are running a mixed collection of semi-obsolete hardware with Windows 98 and higher. The server operates Windows 2000 Server, and Terminal Services is enabled. Each workstation has the Terminal Services client installed, and users log into their virtual PC, which is on the server. Accurate competes with Tom s company, in Section 5.1 above, and would like to operate similarly, with shared files, and a conference room, and even have their manager able to view any projects in the central area. In addition, Accurate would like all their salesmen to use the same Right-Suite Universal project Templates, so that their bids will use uniform assumptions company-wide. Can Accurate install Right-Suite Universal on Terminal Services so that they can operate like they hope to? Wrightsoft Solution Yes, no problem. There are special installation instructions for Terminal Services (Section 3.3, above) but since all files will be installed on the server, it s really only a matter of folder organization during installation to achieve their goals. 12 of 12 November 20, 2007