MX Licensing. You do not have to read this document from end to end, the following recommendation is the minimum for each task:

Transcription

1 MX Licensing You do not have to read this document from end to end, the following recommendation is the minimum for each task: Pages 4 to 8 A new MX user looking to select an ideal MX Licence type for his/her requirements. Pages 9 to 13 An existing MX user investigating the impact of MX Licence changes. Pages 14 to 28 An IT manager installing or maintaining network MX licence servers. Throughout this document all references to the MX Licence mean the combination of the MX Software Licence Agreement, MX Licence Schedule and the Authorisation Code (*.mxs). Hardware_Profile_Security.doc Page 1 of 28

2 NEW USERS 4 INTRODUCTION... 4 MX LICENCE TYPES... 5 Standalone MX Licence...5 Network MX Licence...5 Optional features of network MX licences...6 MXFOOTPRINT GENERATOR PROGRAM... 8 EXISTING USERS 9 INTRODUCTION... 9 MX LICENCE TYPES Standalone Licence...10 Network Licence...10 New optional features for network licences...11 MXFOOTPRINT GENERATOR PROGRAM SETUP AND ADMINISTRATION OF MX NETWORK LICENCES 14 INSTALLING THE MX NETWORK LICENCE MANAGER Introduction...15 Installation...15 Stopping and starting the Licence Manager...16 Licence manager utilities WLMAdmin and WrlfTool...16 MX REDUNDANT NETWORK LICENCE SERVERS Introduction...17 Criteria for redundant licence servers...17 Primary redundant licence server...18 Setting up the redundant licence server pool...18 LICENCE POOLING AND BORROWING Introduction...20 Setting up licence borrowing...21 Altering licence distribution...21 LICENCE COMMUTING Introduction...22 Commuting a licence...23 Checking a commuter licence back in...23 Limiting the number of licences which can be commuted...24 CREATING A LICENCE RESERVATION FILE Introduction...25 Creating a group reservation...25 Excluding users and computers...26 Criteria applying to reservation groups:...26 Hardware_Profile_Security.doc Page 2 of 28

3 LOGGING LICENCE USAGE Introduction...27 Enabling licence usage logging...27 TROUBLESHOOTING ERROR MESSAGES Hardware_Profile_Security.doc Page 3 of 28

4 New users Introduction MX Software is a licensed product. To be able to install your MX software you require an MX licence. The licence contains information on which MX products, environments, applications and options you are licensed to run, and on which PCs you can run them. In order for you to decide which type of licence is most suitable for your organisation please read the following information on MX licences. Hardware_Profile_Security.doc Page 4 of 28

5 MX Licence Types There are two types of MX licence, network and standalone. The definition and criteria for each licence type is given below. Standalone MX Licence The MX Licence is valid for a single PC only The MX Licence is locked to the hardware profile of the PC, or an MX dongle (if a dongle is used, the MX Licence can be moved from PC to PC by transferring the dongle) A PC with a standalone MX licence can be either networked or nonnetworked Network MX Licence With a Network MX licence, the MX Licence Server software is installed on one or more PCs, these PCs are known as MX Licence Servers. The MX software is installed on all PCs which may run MX, these PCs are known as clients of the Network MX Licence. When MX is started on the client it requests an MX licence from the MX Licence Server. A Network MX Licence allows centralised management of the MX software, when an MX licence requires updating it only needs to be done on the MX Licence Servers rather than all the MX PCs. With a Network MX Licence the only hardware profiles required are those of the machines where the MX Licence Servers are installed. It is not necessary to provide profiles of the client PCs. So when new PCs are added to the network it is not necessary to obtain a new MX licence for these PCs, they will simply request MX licences from the existing MX Licence Servers. PCs to be used as MX Licence Servers must be running Windows NT or Windows Hardware_Profile_Security.doc Page 5 of 28

6 For use on PCs connected on a network running TCP/IP or IPX/SPX network protocols (WAN connections allowed). The MX Licence is valid for multiple computers. The MX Licence is locked to the hardware profile of the PC(s) nominated as MX Licence Servers. PCs wishing to run MX contact the MX Licence Servers to request an MX licence. It is possible to have a Network MX licence even if it has only a single concurrency of MX. A PC which acts as an MX Licence Server can also have the MX software installed on it. Optional features of Network MX licences Redundant servers instead of a single PC being nominated as the MX Licence Server, several PCs can be nominated as redundant servers. If a redundant MX Licence Server fails, the MX Licences on the failed server will be automatically transferred to the surviving redundant MX Licence Servers. Users will not suffer downtime waiting for the failed server to be rebuilt. Redundant MX licence servers can be connected via a WAN (Wide Area Network) or LAN (Local Area Network). Licence pooling if redundant servers have been set-up, the MX Licences are in a licence pool, which can be spread across all redundant MX Licence Servers. If an MX licence server has no MX licences available when the client requests an MX licence, a request is passed to borrow an MX licence from another server in the pool which still has free MX licences. This process happens automatically and is transparent to the user. This will enable users in a busy department to borrow MX licences from a less busy department. Hardware_Profile_Security.doc Page 6 of 28

7 MXRedu ndant M XPC MXPC WAN c lientofne tworklicen ce cliento fnetworkl icence LINK LicenceM anagern o.1 ML XReduicenceM anagern ndant o.2 M XRedund ant Li cencema nagerno. 3 M XPC c lientofne tworklicen ce MX PC clie ntofnetwo rklicence Commuter licences if a user wishes to work from home, or is going to be travelling for a few days on business, but still wishes to use the MX software, they are able to check out a commuter licence from the MX Licence Server. The Commuter Licence can be used by the user until theyreturn to the office and check it back into the Licence Sserver, making it available to everyone again. MX Licence reservation it is possible for the IT manager to configure which user/group of users or PCs are allowed to use the MX licences. Similarly they can specify which users/pcs are excluded from using an MX licence. By default any user/pc with software installed will be able to use MX. MX Licence usage logging it is possible to see how many of the MX Licences are being used, when and by whom. Optionally this information can be written to a log file. Hardware_Profile_Security.doc Page 7 of 28

8 Figure 1 - an example of a possible network licence configuration MX Footprint Generator Program This program creates a hardware profile of the machine you wish to licence for use with MX. The MX Footprint generator program outputs a file, which should be ed or faxed to your MX distributor. Once your hardware profile has been received an MX authorisation code will be created and dispatched to you. If you wish to have an MX standalone licence, you will need to run the MX Footprint Generator on the PC which is to run MX. If you wish to have an MX network licence you will need to run the MX Footprint Generator on the PC which is to be the MX Licence Server. If you are going to create redundant MX network licence servers, the MX Footprint Generator must be run on each PC, which is to be a redundant MX Licence Server. The MX Footprint Generator program can be obtained from your MX distributor, the Infrasoft web site or from the MX Software CD. Hardware_Profile_Security.doc Page 8 of 28

9 Existing users Introduction With the release of MX V2.5 there is a new method of licensing the MX software. It is no longer necessary to use a dongle to secure MX, a PC hardware profile can be used instead. As at present, it will be possible to have either a standalone or network MX licence. If you have standalone dongles (white hardware locks), you can choose to retain the dongles, or return them and use a hardware profile instead. You can also transfer to a network licence. If you have an MX network dongle (red hardware lock), you will need to return the dongle and use a hardware profile instead. It is not possible to have a network licence using a dongle. At V2.5 MX network licences have additional features, please see the Network Licence section for details. Hardware_Profile_Security.doc Page 9 of 28

10 MX Licence Types There are two types of MX licence, network and standalone. The definition and criteria for each licence type is given below. Standalone MX Licence The MX Licence is valid for a single PC only The MX Licence is locked to the hardware profile of the PC, or an MX dongle (if a dongle is used, the MX Licence can be moved from PC to PC by transferring the dongle) A PC with a standalone MX licence can be either networked or nonnetworked Note. If you are also running Classic MOSS on your MX PC, the only possible option is a standalone MX licence locked to your dongle. Network MX Licence With a Network MX licence, the MX Licence Server software is installed on one or more PCs, these PCs are known as MX Licence Servers. The MX software is installed on all PCs which may run MX, these PCs are known as clients of the Network MX Licence. When MX is started on the client it requests an MX Licence from the MX Licence Server. A Network MX Licence allows centralised management of the MX software, when a licence requires updating it only needs to be done on the MX Licence Servers rather than all the MX PCs. With a network licence the only hardware profiles required are those of the Licence Managers. It is not necessary to provide profiles of the client PCs. So when new PCs are added to the network it is not necessary to obtain a new MX Licence for these PCs, they will simply request licences from the existing MX Licence Servers. Hardware_Profile_Security.doc Page 10 of 28

11 PCs to be used as MX licence servers must be running Windows NT or Windows For use on PCs connected on a network running TCP/IP or IPX/SPX network protocols (WAN connections allowed). The MX Licence is valid for multiple computers. The MX Licence is locked to the hardware profile of the PC(s) nominated as MX licence servers. PCs wishing to run MX contact the MX Licence Servers to request an MX licence. It is possible to have a Network MX Licence even if it has only a single concurrency of MX. A PC which acts as an MX licence server can also have the MX Software installed upon it. New optional features for Network MX Licences Redundant servers prior to V2.5 if the MX Licence Manager PC failed, users had to wait until the PC was rebuilt before they could run MX again. Instead of a single PC being nominated as the MX Network Licence Server, several PCs can be nominated as redundant servers. If a redundant MX licence server fails, the MX Licences on the failed server will be automatically transferred to the surviving MX Redundant Licence Servers. Users will not suffer downtime waiting for the failed server to be rebuilt. Redundant licence servers can be on a WAN (Wide Area Network) or LAN (Local Area Network). Licence pooling if redundant servers have been set-up, the MX Licences are in a licence pool, which can be spread across all the redundant MX Licence Servers. If an MX Licence Server has no MX Licences available when the client requests an MX Licence, the request is passed to another MX Licence server in the pool which still has free licences. This process happens automatically and is transparent to the user. Hardware_Profile_Security.doc Page 11 of 28

12 This will enable users in a busy department to borrow MX Licences from a less busy department. Commuter licences if a user wishes to work from home, or is going to be travelling for a few days on business, but still wishes to use the MX software, he is able to check out a commuter licence from the MX Licence Server. The commuter licence can be used by the user until they return to the office and checks it back into the MX Licence Server, making it available to everyone again. MX licence reservation it is possible for the IT manager to configure which user/group of users or PCs are allowed to use the MX Licences. Similarly he can specify which users/pcs are excluded from using a MX licence. By default any user/pc with software installed will be able to use MX. MX licence usage logging it is possible to see how many of the MX Licences are being used, when and by whom. Optionally this information can be written to a log file. Figure 2 - an example of a possible network licence configuration Hardware_Profile_Security.doc Page 12 of 28

13 MX Footprint Generator Program If you are not using an MX dongle, you will need to run the MX Footprint Generator program, mxfootprint.exe. This program creates a hardware profile of the machine you wish to licence for use with MX. The MX Footprint generator program outputs a file, which should be ed or faxed to your MX distributor. Once your hardware profile has been received an MX authorisation code will be created and dispatched to you. If you wish to have an MX standalone licence, you will need to run MX Footprint on the PC which is to run MX. If you wish to have an MX network licence you will need to run MX Footprint on the PC which is to be the MX Licence Server. If you are going to create redundant MX network licence servers, MX Footprint must be run on each PC, which is to be a redundant MX licence server. The MX Footprint Generator program can be obtained from your MX distributor, the Infrasoft web site or from the MX Software CD. Hardware_Profile_Security.doc Page 13 of 28

14 Setup and Administration of MX network licences Hardware_Profile_Security.doc Page 14 of 28

15 Installing the MX Network Licence Manager Introduction The MX Network Licence Manager PC issues available MX Licences to other PCs on the network. The Network Licence Manager PC must be running Windows NT 4 (workstation or server), or Windows 2000 (professional, server or advanced server). The Network Licence Manager can also have MX installed, or it can operate as an MX Licence Manager only. Installation 1. Run MX Footprint.exe on the PC, which is to act as the MX Licence Server, or fax the results to your MX distributor. If you are going to use redundant licence servers you will need to run MX Footprint on each of the PCs which are to be redundant servers, and or fax all the results. 2. Once you have received your MX Authorisation Code (.mxs file), log in as a user with Administrative privileges. 3. From the MX CD browse to the Licence_Manager folder and run setup.exe. 4. Next you will be prompted to select the location of the Authorisation Code (.mxs file). 5. You will first be prompted to select the location for the Licence Manager software. Note, if MX is also to be installed on this PC the MX software must be installed in the same location. If you have requested a redundant server licence, at the end of the installation you should choose to launch WrlfTool to configure the redundant licence server pool. See the section Setting up the redundant licence server pool. If you do not have a redundant server licence, select the option to start the Licence Manger at the end of the installation. Hardware_Profile_Security.doc Page 15 of 28

16 Stopping and starting the License Manager The License Manager can be stopped and started by a user with Administrative privileges, by stopping and starting the Sentinel LM service. The MX Licence Manager Program Group contains options to stop or start the License Manager. License Manager Utilities WLMAdmin and WrlfTool WLMAdmin can be used to monitor the use of MX network licences. This utility can be started from the MX Licence Manager Program Group. WrlfTool is used with redundant licence servers to set the initial distribution of MX Licences among the servers. This utility can be started from the MX Licence Manager Program Group if you wish to make changes to the licence distribution after MX has been installed. See the section entitled Setting up the redundant licence server pool for information on running this utility. Hardware_Profile_Security.doc Page 16 of 28

17 MX redundant network licence servers Introduction Redundant licence servers offer the following benefits: If a redundant licence server fails, users can still run MX by obtaining a licence from another redundant server. MX licences can be distributed among the redundant MX Licence Servers reducing the network traffic for a single licence server. Criteria for redundant licence servers The redundant server PC must be running either Windows NT4 (workstation or server) or Windows 2000 (professional, server or advanced server). PCs running Windows 95 or 98 OS are not supported. There must be an odd number of servers, with a minimum of 3 and a maximum of 11 redundant MX licence servers, per MX network licence. The majority of the licence servers must be running at any one time, otherwise no MX licences will be issued. So if there are 3 redundant MX licence servers, at least two must be up and running. The MX Licence Server and all its clients must be running either TCP/IP or IPX network protocol. If the redundant server has TCP/IP and IPX protocols installed, the MX Licence Manager will use TCP/IP protocol. Redundant licence servers using TCP/IP protocol must have static IP addresses. It is not possible to mix the protocols used by servers and clients, all must be running the same protocol. Hardware_Profile_Security.doc Page 17 of 28

18 Primary redundant Licence Server Using redundant MX Licence Servers you create a pool of licence servers. In each licence server pool, one of the servers is nominated as the primary Licence server. All other redundant licence servers in the pool follow the lead of the primary server. If the Primary Licence Server fails, one of the remaining licence servers becomes the new primary server. The order in which the remaining servers are promoted to become the primary server is configured using WrlfTool (see Setting up the Redundant Licence Server Pool). Setting up the Redundant Licence Server Pool 1. Run MXFootprint.exe on each of the PCs that is going to be a redundant licence server, and or fax the results to your MX distributor. In return you will receive your network MX Authorisation Code (mxs file). 2. Once you have received the MX Authorisation Code, log in as a user with Admin privileges 3. Run the MX Licence Manager setup on each redundant server. When prompted select to run WrlfTool to set the MX Licence distribution among the servers and create the redundant licence server file lservrlf. File pulldown select New.., Use the Add Server button to enter the hostname and IP or IPX address of each of the redundant licence servers (See Figure 3) Use the Move Up and Move Down buttons to set the priority of the redundant licence servers in the pool. The Primary Licence Sserver is the first server in the redundant pool to be started, however the order set in WrlfTool determines the order in which the remaining servers will be promoted to become the primary server if the primary server fails. Use the Add License button, followed by Read License from file, to select the file lservrc from the..\mfw\licensing folder. Now another panel is displayed where you can set the distribution of these MX products among the licence servers (See Figure 4). Note If you want only the primary Licence Server to issue licences with the other servers acting only as backup servers, in the event of the failure of the primary server, set the primary server to have all the tokens (licences). The percentage of licences available for borrowing is also set on this panel (See Licence pooling and borrowing section). These options Hardware_Profile_Security.doc Page 18 of 28

19 can also be configured at a later time by running WrlfTool again, and selecting Edit License. Once the distribution criteria and borrowing threshold has been set for each MX option, select Done. 4. Using File and Save As, save the settings in WrlfTool as lservrlf. This file can be copied to the..\mfw\licensing folder on the other redundant licence servers, rather than recreating it for each redundant licence server. 5. Now start the Sentinel LM (Sentinel Licence Manager) on each redundant server, starting with the PC you wish to be the primary Licence Server. After all licence servers have been started, any changes made to the redundant licence file lservlrf, using WrlfTool, will be transmitted to all the redundant licence servers when one server is stopped and restarted. Figure 3 WrlfTool creating redundant server pool and adding MX licences Hardware_Profile_Security.doc Page 19 of 28

20 Figure 4 WrlfTool setting initial licence distribution on redundant servers PC01, PC07 and PC25 Licence pooling and borrowing Introduction Licence borrowing is only available to MX licence servers within a redundant licence server pool. To enable licence borrowing, initially each redundant licence server must have at least one MX Licence concurrency (token) allocated to it. MX Licences are then dynamically balanced among the servers to where their need is greatest. When licence borrowing is enabled, if any of the redundant licence servers starts to run low in licences, it contacts the Primary Licence Server, and asks to borrow licences from another of the servers within the redundant server pool. Hardware_Profile_Security.doc Page 20 of 28

21 Wrlftool is used to set the initial distribution of MX options within the redundant server pool. The borrowing threshold is defined as the limit which when reached, the server asks to borrow a licence. However the lending server needs to have more than the threshold limit available AFTER LENDING before it will lend, this is to avoid any infinite borrowing loops occurring. A server will borrow when the borrowing threshold is reached for that MX option. A server will lend a licence providing that after lending it, it will have at least (((100 borrowing threshold ) + 5) x current number of tokens ) / 100 concurrencies left. Setting up licence borrowing The distribution of MX Licences among the redundant servers is initially configured using the WrlfTool in the.\mfw\licencing folder. When creating the redundant licence pool, it is possible to turn licence borrowing off by allocating all available MX Licences to only one of the redundant licence servers in the pool. By default, licence borrowing is enabled for redundant licence servers. The threshold at which a redundant server decides it needs to make a request for more licences, is governed by the Borrowing Threshold (%) field set in Wrlftool (See Figure 4). For example, if the borrowing threshold is set at 90%, and a server had 10 licences for MXROAD allocated to it, when 9 of its MXROAD licences are in use it will make a request to borrow some more MXROAD licences from another server in the pool. Altering licence distribution The utility WlmAdmin in the..\mfw\licensing folder can be used to configure the redundant licence pool. You can select any redundant licence server and WlmAdmin will view or modify the licence pool of which it is a member. 1. Log in as a user with Administrative privileges 2. Double-click..\mfw\licensing\WLMAdmin.exe Hardware_Profile_Security.doc Page 21 of 28

22 3. Select one of the servers in the redundant pool, and select the MX option whose distribution you wish to alter, for example PROFESSIONAL. 4. The Redundancy Info tab under Detailed information shows the current distribution of licences, for all product options, among the redundant servers in the pool. 5. To alter the distribution of the MX option, select the option in the left-hand panel of WlmAdmin, then right-click for the available choices: Change distribution selecting this option produces a panel which allows you to set the new distribution criteria. Note this change is not permanent, any licence borrowing which takes place later will alter the distribution again. Licence Commuting Introduction If you have a network MX Licence, it is possible to commute a licence from the MX Licence Server to a PC on the network. The PC can then be disconnected from the network and still run the MX options commuted. This is ideal for a user who may be taking their laptop out on site for a day, going away on business or even to allow the user to carry on working at home. Commuter licences are valid for a maximum of 30 days. When an option is commuted, the other users of the Network Licence have one less concurrency available to them. If a user returns to the office and reconnects to the network, if htheir commuter licence has not yet expired they can check the licence back in to the network licence, making it available to all users once more. If the user of a commuter licence does not check the licence back in, once the commuter licence has expired, the commuted licence option(s) will automatically become available to all users of the network licence. Hardware_Profile_Security.doc Page 22 of 28

23 Commuting a licence 1. Double-click WCommute in the..\mfw\licensing folder or select the Commute a Licence button with MX Options in the MX Program Group or Control Panel. 2. Select the licence server you wish to commute a licence from. You have a choice of specifying an MX Licence Server (by hostname, IP address or IPX address) using the Single Server button, or searching the subnet for a list of licence servers (using the Search Subnet button) and selecting an MX Licence Server from there. The options available for commuting are displayed under each server. 3. Highlight a licence and enter the number of days you wish to check it out for. 4. Select the Check Out button, a red tick mark then appears by the option. Note: You must remember to commute the correct combination of MX Licence options to carry out the work you require to do. Checking a commuter licence back in Commuter licences must be checked back in to the same MX Licence Server it was checked out from. 1. Double-click WCommute in the..\mfw\licensing folder. 2. Select the server the options were checked out from. The options should be displayed with a red tick. 3. Highlight the feature and select the Check In button. Hardware_Profile_Security.doc Page 23 of 28

24 Figure 4 Wcommute showing MX Professional in the Windows Environment checked out Limiting the number of licences which can be commuted To ensure that not all the MX Licences are commuted, leaving no licences available for other users, the LSERVOPTS variable can be configured to set the percentage of available commuter MX Licences: Log in with Administrative privileges Go to Control Panel System Environment (for Windows NT4) or Control Panel System Advanced Environment Variables (Windows 2000) Add a new system variable LSERVOPTS (or amend existing variable). Set the value to com <percentage> For example -com 10 will not allow any more licences to be commuted after the 10% limit is reached. Reboot the licence server to implement the changes to LSERVOPTS Hardware_Profile_Security.doc Page 24 of 28

25 Creating a licence reservation file Introduction A licence reservation file lsreserv can be created to reserve a number of MX licences for a specific group. Any licences not specifically reserved are available in a general pool. In the same reservation file it is possible to restrict the use of an option only to named users or computers, or exclude named users or computers from accessing an option. Creating a group reservation 1. Double-click Wlsgrmgr.exe in the..\mfw\licensing folder 2. Select File and New (or Open if you wish amend an existing reservation file) 3. Select Feature and Add, this will start a wizard to guide you through the rest of the process. 4. Features are MX options such as PROFESSIONAL, WINENVT or MXRAIL 5. Select a name for the group who can use the reserved licences, and how many licences (tokens) are reserved for them. 6. Define the users and PCs which are to be included or excluded from the group. 7. Select File and Save As lsreserv in the..\mfw\licensing folder A group reservation consists of the following: MX option to which the reservation applies, for example MXRAIL Name of the group e.g. rail_engineers Number of licences reserved for that group, for example 2 Login names and/or hostnames of computers in this group, for example Jane and PC07 It is written in the reservation file as follows: Hardware_Profile_Security.doc Page 25 of 28

26 option_name : group_name : number_of_licences : {user_name computer} For example, using above examples to reserve two MXRAIL licences for the members of the rail_engineers group which consists of a user with the login Jane and all users of the computer PC07, the entry in the reservation file lsreserv would read: MXRAIL : rail_engineers : 2 : Jane $PC07 (Note: Computer names are prefixed by a $ symbol) Excluding users and computers To exclude a user or PC from running an option the! symbol prefixes the login or computer name. For example, to exclude the users of PC25 from being able to run MX Change, but allowing PC16, PC27 and PC28 the entry in the reservation file would read: MXCHANGE : cad_users : 5 :!$PC25 $PC16 $PC27 $PC28 Criteria applying to reservation groups: A maximum of 256 groups with 256 members (users or computers) each are supported. Groups must be mutually exclusive. Different groups for the same MX option should not have common users or computers. Group and member names cannot exceed 16 characters. If the number of licences reserved is zero or greater than the total number of MX concurrencies available for that option, the concurrency in your MX Authorisation Code will be used. Hardware_Profile_Security.doc Page 26 of 28

27 Logging licence usage Introduction The utility lsmon in the..\mfw\licensing folder can be run in a DOS window to show which users and PCs are currently using an MX licence. If you wish to monitor licence file usage over a period of time it will be necessary to enable licence usage logging on the MX Licence Servers. By enabling licence usage, a file is created showing the username and hostname of PCs requesting MX Licences, and how long a licence was utilised. Running in a DOS window..\mfw\licensing\lsusage <log file name> displays the contents of the log file. Enabling licence usage logging Licence usage logging can be enabled on the MX Licence Server by setting the LSERVOPTS variable. 1. Log in with Administrative privileges. 2. Go to Control Panel System Environment (for Windows NT4) or Control Panel System Advanced Environment Variables (Windows 2000). 3. Add a new system variable LSERVOPTS (or amend existing variable). 4. Set the value to l <\path\ log file name> -z <maximum log file size> 5. Reboot the licence server to activate the usage logging. By default when the maximum log file size is reached, the current logfile is renamed <log file name>.nn where nn ranges from 00 to 99, and a new log file started. If you wish to disable further logging after the maximum log file size is reached, rather than creating a backup, use x as well on LSERVOPTS. For example: LSERVOPTS -l c:\mfw\licensing\usage.log -z 2m -x Hardware_Profile_Security.doc Page 27 of 28

28 Will enable licence logging to the file usage.log to a maximum file size of 2 MB. Once the 2 MB limit is reached licence usage logging will stop. Troubleshooting Error Messages MX Errors are documented in the errors.hlp file which is located in the mfw\<lang>_sys folder. If you receive an error which does not appear to be documented please contact your MX supplier. Hardware_Profile_Security.doc Page 28 of 28