• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Network Configuration
 

Network Configuration

on

  • 783 views

 

Statistics

Views

Total Views
783
Views on SlideShare
783
Embed Views
0

Actions

Likes
0
Downloads
3
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Network Configuration Network Configuration Document Transcript

    • Engineered SoftwareNetwork Configuration& Installation GuideAugust 8, 2001Version 7Rev. B
    • Contents Revision History ................................................................................. 3 Revision B ..................................................................................................3 Revision A ..................................................................................................3 Program Installation........................................................................... 4 Overview .....................................................................................................4 Performing an Administrator Setup .........................................................4 Performing a Client Setup.........................................................................5 License Server Installation................................................................ 7 Overview .....................................................................................................7 Installing the Network License Server .....................................................7 Optional Server configuration ..................................................................9 Configuring the Client ...............................................................................10 Administration Tools ......................................................................... 11 WlmAdmin.exe - Administer License Management Activities:..............11 lsusage.exe - Display the SentinelLM Usage Log File............................13 Lsrvdown.exe - Shut Down the License Server: .....................................15 Obtaining Technical Support ............................................................ 16Engineered Software Network Configuration & Installation Guide Page 2
    • Revision History Revision B Added warning regarding running the “GETCODE.BAT” file from the License Server only under the topic, “License Server Installation.” Various text edits for clarity. Revision A Added information regarding SentinelLM Hardware Requirements under the topic, “License Server Installation.”Engineered Software Network Configuration & Installation Guide Page 3
    • Program Installation Special network software must be loaded before users can start network versions of this program. Since this software communicates across the network to all workstations, your Network Administrator should install it. Overview A FLO-SERIES network installation is comprised of several parts; installing the software on the client workstations, configuring the network License Server and, if required, configuring the Site Authorization Server. A Client Setup installation is not required in order to access the Network License Server. If you prefer, you may configure each of your workstations using the default setup provided on the CD-ROM. However, to ease deployment and administration, the Client Setup installation method is recommended. Regardless of the method chosen to configure the workstations, the Network License Server installation must still be performed before workstations may access any network licenses. Performing an Administrator Setup In addition to configuring the first workstation, an Administrator Setup provides the capability of creating a Client Setup. This is a centrally administered configuration that allows for later workstation installations without direct Administrator intervention. NOTE: Due to increased security, in some cases an Administrator may still need to perform the setup on workstations using Windows 2000 for users who do not have local Power User or Administrator permissions. The first installation will configure the selected workstation as well configure the Client Setup. Subsequent workstations will use the Client Setup installation. You must enter an additional command line parameter to perform an Administrator Setup. The program installation will start automatically if Autorun is enabled. To temporarily disable Autorun, press and hold down the Left Shift key while inserting the CD. 1. Place the CD-ROM into the CD-ROM drive (For example, D:). 2. Choose Run from the Start menu. 3. Click Browse and locate the file, SETUP.EXE on the CD-ROM. 4. In the Run line, add the parameter /ADMIN. The command line should appear similar to the following: D:SETUP.EXE /ADMIN 5. License Agreement: You must accept the terms of the License Agreement to install the software. 6. Enter your Company Name: This will be copied to each of the workstations during Client Setup. 7. Enter v. 7 Serial Numbers: Enter the serial number for each of your Version 7 FLO-SERIES products. NOTE: Do not enter Version 6 serial numbers, this installation only installs Version 7 programs. 8. Choose Destination Location: Enter the path that you wish to install the program(s) to. This may be a mapped drive letter (i.e. K:FLO) or UNC path (i.e. APPSERVERFLO). The installation will then copy the program files to the selected directory.Engineered Software Network Configuration & Installation Guide Page 4
    • NOTE: If you use a mapped drive, the software must be installed to a subdirectory under the drive, not to the root of the drive itself. (For example: N:FLO, not simply N:.) 9. Restrict User Directories: This option is deselected by default. All FLO-SERIES programs allow users to redirect their default directories. These include Tables, Catalogs, Designs and Tools. If desired, an Administrator may choose to restrict these directories to the network location. The user’s Projects directory preference is always enabled. It also does not prevent users from saving files to alternate locations, but it does disable the capability for the user to permanently modify their path preferences. Select ‘Yes’ to enable this restriction. 10. Select Network Type: If you have a Local Area Network license, choose LAN, if you have a Wide Area Network license, choose WAN. If you do not know what type of license you have, you may contact your Sales Representative. 11. License Server: Enter the IP address or Host Name of the Network License Server. This is the computer that hosts the program license. 12. Site Authorization Server: Enter the IP address or Host Name of the Site Authorization Server. This is only required for WAN installations and will not be displayed if LAN was previously selected. 13. Copy Setup Files: This option is selected by default. Select ‘Yes’ to create a subdirectory called CLIENT in the installation directory and copy the required setup files to it. It will also create a Windows shortcut file that can be distributed to users (via E-mail, for example) so that they can perform the Client Setup without Administrator intervention. This is highly recommended as the preferred method to configure workstations using Client Setup. The storage requirements are approximately 12MB. 14. Install Adobe Acrobat: This option is selected by default. Select ‘Yes’ to install the Adobe Acrobat Reader. 15. Program Registration: This option is selected by default. Select ‘Yes’ to launch your web browser and connect to the web-based registration form. 16. Installation is now complete. Restart the computer if required. If you chose to copy the Client Setup files to the program directory, proceed to ‘Performing a Client Setup’ to configure additional workstations. Performing a Client Setup Installing the Software The software can be installed using the Client Setup or the CD-ROM. The Client Setup is highly recommended as it eases deployment of the software and later administration. If you choose to perform installations using the CD-ROM, consult the instructions in the software package. NOTE: You must install the software on each workstation using one of the supplied Setup methods. Copying the files from one computer to another is insufficient and may result in program errors. To use the Client Setup The software must be run from a network drive and preconfigured using the Administrator Setup. The Client Setup only installs the necessary local files and shortcuts, not the program files. The following instructions assume that an Administrator Setup has been performed. The Administrator Setup configures the Client with information including the program serial number(s), the install directory (path), and company name. The Client Setup requires minimal interaction by the user.Engineered Software Network Configuration & Installation Guide Page 5
    • 1. In the CLIENT subdirectory created by the Administrator Setup is a shortcut labeled ‘Install FLO-SERIES Client’. This is a standard Windows shortcut that can be distributed to each of your users via E-mail or some other method. 2. Alternatively, the Client Setup can be launched from the command line using parameter /CLIENT. The command line should appear similar to the following: K:FLOCLIENTSETUP.EXE /CLIENT 3. License Agreement: You must accept the terms of the License Agreement to install the software. The installation will then configure the workstation 4. Install Adobe Acrobat: This option is selected by default. Select ‘Yes’ to install the Adobe Acrobat Reader. 5. Program Registration: This option is selected by default. Select ‘Yes’ to launch your web browser and connect to the web-based registration form. 6. Your software installation is now complete. Restart the computer if required. Repeat the installation on each workstation.Engineered Software Network Configuration & Installation Guide Page 6
    • License Server Installation Overview Engineered Software is using Rainbow Technologies’ SentinelLM software locking system to distribute and control network licenses of its products. It is possible that multiple applications on your network might use the SentinelLM software to control access. If you are already running a SentinelLM license server on your network, please skip down this list slightly to section 2b. Please be aware that the installation path for SentinelLM is different for each version of the software (we are currently distributing ver. 7.1.1). Please be sure to install the server tools to the actual SentinelLM directory on you server. For assistance setting up the license server and adding licenses, contact Engineered Software Technical support at 360-412-0702 or support@eng-software.com. Installing the Network License Server 1. SentinelLM Hardware Requirements The SentinelLM Server software may run on Windows 95/98, NT Workstation or NT Server 4.0, or Windows 2000 Professional or Server. Standard system requirements for the operating system should be sufficient to run the server software. NOTE: Neither Rainbow Technologies nor Engineered Software support SentinelLM on computers with more than one network interface card (NIC). If you feel it may be necessary to run the SentinelLM software on a server with multiple NICs, please contact Engineered Software technical support before continuing. 2. Install the SentinelLM Software a) From your installation CD run the file SERVERSETUPSETUP.EXE and step through the prompts. The SentinelLM server will start automatically at the end of the installation. (Important: system privileges during installation must allow registry modification.) b) After the server installation completes, run the separate server tools installation. From the CD run SERVERSERVERTOOLS.EXE and specify the path to your SentinelLM Server directory at the prompt. By default, the path prompt will point to the server’s default installation path. 3. Send your server’s “locking codes” to Engineered Software a) If you do not already have a window opened to the SentinelLM Server directory (default is: C:Program FilesRainbow TechnologiesSentinelLM 7.1.1 ServerEnglish), open one. b) Run the file GETCODE.BAT. This will create a new file called LOCKINGCODES.TXT. Create a new mail message to unlock@eng-software.com. For clarity, use the subject line, “Network License Locking Codes” and include your product serial number(s) in the body of the message. Then, either paste the codes from LOCKINGCODES.TXT into the message or included the file in the message as an attachment. c) After receiving the message with your locking codes, Engineered Software will send back a license file that you will use in the next step. NOTE: The GETCODE.BAT file must be run directly from the computer running the SentinelLM license server. Running this file from a remote workstation will result in incorrect locking codes and a non-functional network license.Engineered Software Network Configuration & Installation Guide Page 7
    • 4. Add your licenses to the server a) After processing the locking codes you sent in the previous step, Engineered Software will send you an email message with the subject line, “Here is your new PIPE-FLO network license file.” Attached to that message will be a file named LICENSE.LIC. Save that file to your SentinelLM Server directory (default is: C:Program FilesRainbow TechnologiesSentinelLM 7.1.1 ServerEnglish). b) Next, from the same directory, run the file ADDLICENSE.BAT to install the new licenses to your license server. c) For the changes to take affect you’ll need to restart your SentinelLM Server software. Under Win9x, simply right-click on the server software’s taskbar entry and choose close. Then run LSERV9X.EXE from your server directory. For WinNT/2000, find the SentinelLM service in your services control panel. Select it, choose Stop, and when the process completes, choose Start. Once complete, the newly added licenses should be available to the network. d) To view license availability, run WLMADMIN.EXE. Further detail on working with WlmAdmin is provided below.Engineered Software Network Configuration & Installation Guide Page 8
    • Optional Server configuration LSERVOPTS - Set License Server Options: Certain properties of the license server may be controlled by setting up the local environment variable, LSERVOPTS. The variable has several options as described below. (Administrators running license servers on Win9x machines may want to pay special attention to the -b option flag which will force the server software to behave as a service.) -l usage-log-file Specifies the name and location of the license server’s usage log file, which enables usage logging. By default, usage logging is disabled. -z usage-log-file-size The maximum size of the usage log file. The size can be specified in bytes, kilobytes, or megabytes. For instance, -z 2000 means 2000 bytes, -z 2k means 2 kilobytes, -z 2m means 2 megabytes. The default value is 1 mega- byte. Once the maximum size of the file is reached, the license server will create a backup log file unless the -x option has been used; the -x option causes the license server to simply stop logging transactions. If log file backups are not disabled by -x, when the log file reaches its maxi-mum size the contents of the log file are moved into a new file that has the same name as the original log file but which has two numeric digits appended to its name. For example, if the original log file is named lserv.log, the first backup file will be named lserv.log.00. The next time a backup file is created, the new file will use the next available backup number (e.g., lserv.log.01). The maximum number of backup files is 99; you can move existing backup log files to another directory and the license server will begin again with 00. If clients are connected to the license server when the backup file is created, dummy records are created for any pending transactions in the backup file; corresponding dummy records are created in the new file. The dummy records are identified by the user name -x By default, on overflow of the usage log file, the file contents will be moved into a backup file. New usage records are then written to the original file until it overflows again. If the -x option is specified, the file will not be backed up on overflow; instead the license server will simply stop writing further records to the file. -f error-file Specifies the name and location of the error file where the license server will log occurrences of unexpected conditions. By default, this is disabled until the option is specified. Then the license server will append to the lserv.log file in the current directory. -b For Windows 95/98, starts the license server as a background service which will not be terminated when the computer user logs off. The license server runs without displaying a window or message. You must use the lsrvdown command to stop the license server. Example: To tell the license server running on a Windows 95/98 based computer to set a 2 megabyte limit on the log file, to stop logging when the file size limit is reached, and to start the license server as a background service, place the following in the Windows 95/98 “autoexec.bat” file. SET LSERVOPTS=-z 2m -x -b NOTE: Environment Variables are set differently under WinNT/2000 than under Win9x. For Win9x, place environment variables in the AUTOEXEC.BAT file as in the example above. For WinNT/2000 edit the environment variables by opening the “System” control panel and selecting the “Environment” tab. Type the variable name and value string on the lines provided and click the set button to enable the variable.Engineered Software Network Configuration & Installation Guide Page 9
    • Configuring the Client By default, a newly launched FLO-SERIES product searches the local area network for a license server that can supply the necessary product license. Depending on network traffic, the size of the network, and other factors this may introduce a short (though usually unnoticeable) delay into the launch process. In addition, products launched this way may only be able to locate license servers located on their local subnet. To minimize launch delays or to allow a client to locate a license server that is not on the local subnet, it may be necessary to add certain configuration settings to the FLO.INI files on your users computers. Users who have purchased the wide-area network package are required to use these settings to enable access to servers outside the local network. The following settings may be added to the “[ID]” section of FLO.INI: LICENSESVR= IP address or Host Name of the license server serving FLO-SERIES product licenses. This is the only network setting necessary for LAN installations. The license server must be located on the local network. (Example: LICENSESVR=192.123.123.12, where 192.123.123.12 is the IP address of your license server.) SITEAUTHSVR= IP address or Host Name of the license server providing the special WAN access license (“Site Authorization Server”). Without this server, users are restricted to product licenses located on the LAN servers. The site authorization server must always be located on the LAN. WIDEAREA= Used in conjunction with the above SITEAUTHSVR setting. Set the value to 1 to enable the feature. (WIDEAREA=1) This setting tells the software that it should be looking for a wide area authorization. Leave this setting blank if your users are not accessing the license server across a WAN as it may add additional delays to program start up. Enabling this setting will not enable WAN license access unless a valid site authorization license has been issued for your network. NOTE: The above INI settings can be configured automatically during the Administrator Setup. Additionally, you may easily change the above settings for all users running FLO-SERIES products from a central server instead of local installations. Simply make the above changes to the DEFAULT.CFG file on the program directory. The next time a user launches the program, the settings will be copied to the FLO.INI file on their computer.Engineered Software Network Configuration & Installation Guide Page 10
    • Administration Tools Certain tools have been provided to make managing/monitoring your SentinelLM License server easier. Their use is not necessary, but they may be useful for trouble shooting or analyzing network usage. All of these tools should be found in your SentinelLM server directory (default path is: C:Program FilesRainbow TechnologiesSentinelLM 7.1.1 ServerEnglish) WlmAdmin.exe - Administer License Management Activities: Description: Provides information on licensing activities. Includes information on license servers detected, details on active licenses, and information on licensed users. WlmAdmin also performs a variety of administrative functions. See below for more information. Who/Where: Run by an administrative user on a stand-alone, client, or license server computer. Using Windows Explorer, navigate to the location of the WLMADMIN.EXE file, and double-click the file to start the program. Monitoring Licenses and License Servers: You can use WlmAdmin to see what licenses are being serviced by which license servers and see information on those licenses. You will see information about each license: whether it can be a commuter license, what feature/version is licensed, how many users are using the license, the license expiration date, and so on. Shutting Down the License Server In the license server pane of the main WlmAdmin window, right-click on the license server you want to shut down and select Shutdown Server from the menu Using WlmAdmin to Monitor Licenses and License Servers The first time you start WlmAdmin, it shows an empty screen, but as soon as you have selected license servers to monitor, WlmAdmin displays information about them. You can also see information about licenses on the license servers and the users who use them. Setting WlmAdmin Preferences You can choose what WlmAdmin displays when it starts. From the Edit menu, select the Preferences command: • To always show the license servers you have defined (see below), select the Discover defined servers on startup check box. • To automatically discover and display the license servers on your subnet, select Discover subnet servers on startup check box. Be sure to select Save these preferences to a file to save your choices. Other preference settings you can choose are: • Show client library error handler messages to pass license management error messages from SentinelLM through to WlmAdmin. • Broadcast Interval to select the number of seconds between broadcasts to the network to discover license servers. • Timeout Interval to select the number of seconds at which WlmAdmin will stop trying to contact a license server. If you have a large network or a slow one, you might want to increase this number if you find WlmAdmin has difficulty retrieving information from license servers.Engineered Software Network Configuration & Installation Guide Page 11
    • Selecting the License Servers The first step to using WlmAdmin is to select what license servers you are interested in monitoring. To create a list of Defined License Servers: 1. Go to the Edit menu and select the Defined Server List command. 2. Type a license server name and click the Add button to add a server to the list. If you are not sure of the license server computer’s host name, you can wait for WlmAdmin to display license servers in the Subnet Servers area of the left-hand pane of the main window to see what license servers are available on the network. 3. Once a license server is defined, you can add more or select a server and click Remove to remove it from the list. 4. Click OK to return to the main WlmAdmin screen. To Discover All License Servers on Your Network Subnet Go to the left-hand pane of the main WlmAdmin window and double-click Subnet Servers. WlmAdmin will broadcast to the network to discover all license servers and display them here. To Refresh the Network Display Right-click on Defined Servers or Subnet Servers and select Refresh to tell WlmAdmin to display new information on that group of license servers. You may also select Refresh All from the View menu to refresh the display for all license servers shown. To See Information on a License Server Click the name of a license server in the left-hand pane of the main window. In the right-hand pane of the display, you see the IP or IPX address of the computer containing the license server and its host name. To Add or Remove a License Server from the Defined Server List Right-click the name of a license server in the left-hand pane of the main window. From the menu, select Add to Defined List or Remove from Defined List. To Shut Down a License Server Right-click the name of a license server in the left-hand pane of the main window. From the menu select Shutdown Server. To Add a License Code to the License Server from the Keyboard 1. Right-click the name of a license server in the left-hand pane of the main window. From the menu select Add Feature. To add the license by typing in the license code, select From a String. 2. Type the license code in the License code box. 3. If this is a redundant license code, enter the token distribution criteria in the Distribution criteria box in this format: Server1:tokens1^Server2:tokens2... where Server is an IP address, IPX address, or host name of the computer containing a redundant license server and tokens is the number of license tokens to be allocated to that redundant license server. Note that all Server:tokens arguments must be separate with a ^ symbol. 4. To permanently add the license code to the license server license file as well as temporarily adding it to the license server memory (only in effect until the license server is rebooted), select the Add feature to server’s file check box.Engineered Software Network Configuration & Installation Guide Page 12
    • 5. Click Add. To Add a License Code to the License Server from a File 1. Right-click the name of a license server in the left-hand pane of the main window. From the menu select Add Feature. Select From a File and To Server (to add the license code temporarily to the license server memory, only in effect until the license server is rebooted) or To Server and its File (to add the feature both temporarily to the license server memory and permanently to its license file). 2. Now select the license code file from the standard file selection window. To Change the Log File for a Selected License Server: To begin a new log file for a selected license server, right-click the license server and select Change log file name. To See Information on a License 1. In the left-hand pane of the main WlmAdmin window, click the + sign to the left of a license server to see what licenses it is servicing. (Once you have expanded the license server information, you can click the - sign to collapse the information again.) If a license server does not have a + sign next to it, it does not currently have licenses installed. 2. Click the name of a license. In the right-hand pane of the display you see information on the characteristics of the license. The exact information you see depends on the license. In addition to basic information, such as how many concurrent users can use the license, when it expires, what users currently are using the license, the display can include whether the license can be used for commuter licensing, and if the license is a redundant license. If the license is a redundant license, you will see how its tokens are distributed and what license servers can service it. 3. Double-click a license to see if any users are using the license. (Once you have expanded the license information, you can click the - sign to collapse the information again.) Tip If a user symbol is red, that user is in a queue waiting for an available License. 4. Click the name of a user. In the right-hand pane of the display you see: user name and host name of the computer the user is on. If this user is in a reservation group, you see the name of the group. You also see information on how long the user has been using this license. To Delete a License from the License Server To delete a license from a license server, right-click the license name and select Remove Feature. The license will be removed from the license server’s memory until the license server is rebooted. Exiting WlmAdmin To leave WlmAdmin, go to the File menu and select Exit. lsusage.exe - Display the SentinelLM Usage Log File Description: Displays a summary of application usage, providing information on license transactions contained in the license server usage file. See below for a sample. Who/Where: Run from the operating system command prompt by an administrative or application user on a stand-alone, client, or license server computer. Options: One or more of the following options must be specified: -l log-file Selects the license server log file to display. Must be specified. If this is the only option, the summary will be displayed on the screen.Engineered Software Network Configuration & Installation Guide Page 13
    • -c CSV-format-file Specifies the name of an output file to which the output will be written in Comma-Separated Values (CSV) format. This CSV file can be used with Microsoft Access to produce graphical reports. -f feature1[,version1] Specifies feature(s) and version(s) to be included in the output. feature2[,version2]… Note that version is optional. If this option is not supplied, the output will contain all features and versions in the log file. -m start-month Specifies the first month (1-12) of the time period to be included in the output. If not specified, then the -a option is ignored and January 1 is assumed for the start month and start day. -a start-day Specifies the first day (1-31) of the month to be included in the output. For example, if you have specified March as the start month, specifying a start day of 1 means that the output will be for a time period beginning with March 1. If not included, and the -m option is included, a start day of 1 is assumed. -y start-year Specifies the first year of the time period to be included in the output. Use four digits to specify the year. If not included, then -m and -a are ignored and the output begins with the first data in the file. -M end-month Specifies the last month (1-12) of the time period to be included in the output. If not specified, then the -A option is ignored and the default value of December 31 is assumed. -A end-day Specifies the last day (1-31) of the month to be included in the output. If not included, and the -M option is included, an end day of 31 is assumed. -Y end-year Specifies the last year of the time period to be included in the output. Use four digits to specify the year. If not included, then -M and -A are ignored, and the output ends with the last data in the log file. -h Displays a list of all options that can be used. Creating License Server Use Reports SentinelLM provides the ability on Windows computers to use Microsoft Access 97 to create graphical reports of license server use. To use this feature, you will need to use the lsusage -c option to create a comma-separated values (CSV) file from the license server log file. See the section above for information on this option. By use of other lsusage options, you can create an output file with use data for specific features and for specific time periods. Once you have created the CSV file, here is how to create graphical reports: Note You must have Microsoft Access 97 on the computer on which you want to run reports. Also, keep the number of features for which you are generating reports to a reasonable number (15 to 20) or the reports may not be very easy to read because there simply won’t be room for a clear display. To Import the CSV File: 1. Within Microsoft Access, open the MDB file provided with SentinelLM: ReportDB.mdb. 2. Select the Table tab. 3. Click New. 4. Select Import Table. 5. Select the CSV file you created with lsusage and click Import. Tip In Microsoft Access, not all file types are installed by default. If you do not have the text file type installed, run the Access Setup program, click Add/ Remove, then select Data Access and Change Option to install the text file type.Engineered Software Network Configuration & Installation Guide Page 14
    • 6. The Import Text Wizard is displayed. Continue to click Next until it asks “Where would you like to store your data.” 7. Select In an existing table and select the table Lservlog. (If instead of adding to an existing Lservlog table you want to create a new one, delete any rows that are already in the Lservlog table before importing new data.) 8. Click Finish. Don’t forget to keep the table name set to Lservlog. To Creating Reports Once the log file use data is imported into the Lservlog table as discussed above, you can now create reports for that data. 1. Within Microsoft Access, open the ReportDB.mdb file. You will immediately see the SentinelLM report selection screen. 2. You can now select the date range of the report by specifying Start Date and End Date. 3. Now select the type of report you want to create: • Total number of tokens granted per feature • Maximum number of tokens granted per feature • Average number of tokens created per feature • Total usage time per feature • Total number of tokens denied per feature • Percentage of licenses denied per feature Tip: When using lsusage to create the CSV file that is the input to these reports, you can limit the data to usage information for specific features and versions. Lsrvdown.exe - Shut Down the License Server: Description: Shuts down the named license server. Format: lsrvdown host_name Who/Where: Run from the operating system command prompt by an administrative user on a client or license server computer. On Windows 95/98, only the same user who started the license server can stop it. On Windows NT/2000, any user with administrative privileges may use lsrvdown unless the license server was started by a user logged in as Administrator, in which case, only Administrator can shut the license server down. The computer on which you are running lsrvdown must be in the same network domain as the license server computer. Options: host_name specifies the name of the computer that is running the license server that you want to shut down.Engineered Software Network Configuration & Installation Guide Page 15
    • Obtaining Technical Support This guide was written to cover all known configurations, but occasionally users will have some difficulty getting their system running. Setup and Configuration issues are always supported free of charge. To contact Engineered Software Technical Support, use one of the following methods: Phone: 1-360-412-0702 Fax: 1-360-412-0672 E-mail solutions@eng-software.com Web: http://www.eng-software.com When contacting Engineered Software for support, please gather the following information beforehand (You may want to print out a copy of this page and fill out the information.): Program Name: Program Serial Number: (Found on installation disks or program ‘About’ dialog): Network Operating System (Type, Version): License Server Operating System (Type, Version): Site Authorization Server Operating System (Type, Version): Workstation Operating System (Type, Version): Protocols installed on your PC: Protocols installed on your Network: Be sure to write down any error messages that you receive exactly as shown. If there is any additional information that you can think of to add, please do so. The more information we have, the quicker we will be able to help you.Engineered Software Network Configuration & Installation Guide Page 16