Using the Express IP Library Locator when Deploying the 5.x Express Client
Technical Note 1072
Last Reviewed 04-Jan-2002
Applies To
Express Software Manager version 4.x through 5.x
Summary
This technical note describes how to use the Express IP Library Locator utility, combined with workstation IP addresses, to group login script users into different Express libraries during the Express metering client installation. The utility can also be used to prevent specific users from installing the Express client. Details are provided for configuring the Express IP Library Locator initialization file, handling non-standard class C subnet masks, and dealing with deployment to 16-bit workstations.
Note: If you are using Express Software Manager 6.0 or higher, see Technical Note 1570 for details about using the Express IP Library Locator.
Understanding the IP Library Locator Utility
The IP Library Locator is part of the Express Resource Toolkit. When deploying the Express client, this utility may be used to
- group users into different Express Libraries
- prevent specific users from receiving the Express client
The IP Library Locator utility can also be used to establish which workstations should be scanned for inventory. This technical note deals only with Express metering. Refer to the Express Software Manager System Administrator Guide for inventory configuration details.
To best organize and deploy the Express client in your network environment, you must determine the number of Express Libraries you will create and maintain. Express Metrix recommends a limit of 500 users per library to optimize network speed and server space. A maximum number of 800 users should be configured to write to one library. The IP Library Locator utility lets you specify which workstations should install from - and write to - a particular Express library based upon the machine's IP address.
You may also want to consider excluding specific workstations, such as dial-in RAS clients, roaming laptop users, or guest accounts from installing the Express client. The IP Library Locator utility allows you to prevent a group of users from receiving the Express client based on their workstation IP address.
How the IP Library Locator Works
The IP Library Locator's executable, Exipinst.exe, replaces the Express client executable, Exinst.exe in the login script. When Exipinst.exe is run, it determines the IP address of the machine that runs it, then uses the IP Library Locator initialization file, Exip.ini, to determine the appropriate library path. The Exipinst.exe program and Exip.ini initialization file must be copied to the login folder that contains the login batch files for the users at a given site.
Configuring the Exip.ini Initialization File
A sample Exip.ini can be found in the Clients folder within the Express library folder on the server. If you use the IP Library Locator, use the information in this section to help you determine how to edit this file to fit your specific installation needs and network environment. After deploying the IP Library Locator on your network, all users will meter to the libraries defined within this file.
While creating your Exip.ini file keep the following in mind:
- You can specify individual IP addresses, or use the wildcard character (*) to indicate an entire subnet. For example, 111.222.333.* includes all workstations in the 333 subnet.
- Enter each IP address or IP address range (wildcard) on a separate line.
- When an Express IP Library Locator script is processed, Exipinst.exe looks through the script to determine the best match for the workstation's IP address. If the IP address fits within more than one indicated IP address range, Exipinst.exe will use the most restrictive option.
- After finding the best match for the IP address, Exipinst.exe checks to make sure the IP address is not configured for NOMETER. If the address is indicated in a NOMETER line, that machine will not receive the Express client installation.
- There is no built-in limit to the number of lines that may be included in the Exip.ini file. The Microsoft function call that Exipinst.exe uses to read the Exip.ini file does, however, have a limit of 32K.
Sample Exip.ini File
The sample initialization file below organizes the network users into four Express libraries, and excludes RAS dial-in users from installing the Express client. This sample includes only the Express client installation portion (EXIPINST) of the Exip.ini file. The leading semi-colon (;) is a remark indicator. Lines that begin with a semi-colon are not processed when the script is run.
[EXIPINST]
; Express clients will be divided into four different libraries
; based on their IP address subnet. Workstations in the
; 111.222.30.* subnet will meter to the FirstFloor library.
; Workstations in the 111.222.33.* subnet will meter to the
; SecondFloor library.
111.222.30.*=\\Latte\VOL3\Accts\Users\FirstFloor\Emlib\clients
111.222.33.*=\\Latte\VOL3\Accts\Users\SecondFloor\Emlib\clients
; Exclude the following subnet from metering. This subnet is
; used only for RAS dial-in clients.
111.222.16.*=NOMETER
; Meter all remaining subnets of network 111.222.*.* to the
; Public library.
111.222.*.*=\\Mocha\VOL3\Accts\Public\Emlib\clients
; Meter IP addresses that are not part of the 111.222.*.* network
; (Everyone not specified above) to this library.
*.*.*.*=\\Espresso\VOL3\Accounts\Public\Em\Default\clients
|
Using a Subnet Mask other than 255.255.255.0 with Class C IP Addressing
It is necessary to create an entry in the Exip.ini file for the broadcast address of each subnet if all of the following are true of your network environment:
- a class C addressing scheme is being used
- the subnet mask is something other than 255.255.255.0
- you want to assign workstations within each subnet to a different Express library
For example, if a site is using IP addresses in the range of 222.333.44.1 through 222.333.44.254, has a subnet mask of 255.255.255.128, and wants machines from the two subnets to install and meter to different Express libraries, the Exip.ini file will need entries for both 222.333.44.0 and 222.333.44.128. The entries would appear like this:
222.333.44.0=\\Server\Apps\EXLIB_1\Clients
222.333.44.128=\\Server\Apps\EXLIB_2\Clients
If there is no need to assign all workstations within each subnet to a different Express library, the wildcard character (*) can be used to direct all workstations in the range of 222.333.444.1 through 222.333.444.254 to the same library. The entry would appear like this:
222.333.44.*=\\Server\Apps\EXLIB\Clients
Deploying the Express Client to 16-bit Workstations
The IP Library Locator utility provided in the Express Resource Toolkit supports only 32-bit Windows operating systems such as Windows 95, Windows 98, and Windows NT. In network environments that include 16-bit Windows 3.x workstations, use one of the following strategies for dividing users when deploying the Express client. (There is no support for metering DOS clients.)
Use Two Utilities to Assign 16-bit and 32-bit Workstations to the Same Library
This method allows you to have 16-bit and 32-bit workstations metering to the same libraries based on machine IP address. Download Ex1405as.exe from the Express Metrix web site:
http://www.expressmetrix.com/support/support_downloads.asp
Ex1405as.exe is a self-extracting executable that contains the 16-bit IP Library Locator executable, Ipinst16.exe. When using a combination of the 16-bit and 32-bit IP Library Locator utilities, add logic to the login script that checks to determine each workstation's operating system. When the Windows 3.x operating system is detected, use the login script to run Ipinst16.exe. For 32-bit operating systems run Exipinst.exe. Both executables use the same Exip.ini file to configure library membership. For examples of how to determine the operating system within a login script, see the Express Metrix Technical Note 1340, Modifying Login Scripts to Deploy Express Client 4.x or Higher.
Exclude the 16-bit Workstations from Installing the Express Client
If you do not plan to install the Express client on 19-bit workstations you can exclude them from the deployment by adding the workstations IP address (or IP subnet range) to the NOMETER section of the Exip.ini file. Use only one address, or wildcard range, per line. For example:
111.222.30.22=NOMETER
111.222.31.71=NOMETER
111.222.16.*=NOMETER
Another way to exclude 16-bit workstations from installing the Express client is to put the IP Library Locator executable in a login script with a .Cmd file extension. The .Cmd extension is processed only by Windows NT and is ignored by all other operating systems. This approach works only if all 32-bit workstations are Windows NT.
Assign all 16-bit Workstations to One Library
When organizing your Express libraries, plan to have all 16-bit workstations log data to one library. To do this, add logic to the login script that checks to determine each workstation's operating system. When Windows 3.x is detected, use the login script to run Exinst.exe from the Clients folder of the Express library you have identified for 16-bit machines. Run Exipinst.exe for all 32-bit operating systems and use the Exip.ini file to configure library placement. For examples of how to determine the operating system within a login script, see Technical Note 1340.
Optional Switches
There are several optional command line switches that can be used during the Express client installation. Any command line switches that are passed to Exipinst.exe are passed on to the installation programs Exinst.exe.
Syntax: EXIPINST [-u] [-q | -v] [-l] [-a]
Example: Exipinst -a -q
The following table lists the optional switches that can be run with the IP Library Locator utility.
Switch
|
Function
|
-a
|
Always Install - Always install clients from library (default: Check version first)
|
-l
|
Login Script - Exipinst is being run from a login script (default: Not using Login Script)
|
-q
|
Quiet - Don't display messages (default: Banner only)
|
-u
|
Uninstall - Uninstall the client (default: Install)
|
-v
|
Verbose - Display messages (default: Banner only)
|
-?
|
Help - Display help information
|
Related Technical Notes
| 1340 |
Using Login Scripts to Deploy the Express Client (ESM 4.x to 5.x) |
| 1570 |
Using the ESM 6.x IP Library Locator when Deploying the Express Client |
| 9991 |
Express Software Manager Technical Notes (5.x or lower) |
|