PATCH 468-003
-----------------------

You may need to apply this patch if:
a. Your end-users cannot give nodelocked-offline licenses back to the  
   server's pool of concurrent-offline licenses. 
b. You cannot assign authorizations based on group names 
   to use concurrent-offline licenses in offline mode.
c. You can no longer update the max offline period of a concurrent-offline
   license
d. The license server no longer starts

Defects description
-----------------------------
a. With this patch the following constraints in the handback of a previously 
reserved nodelocked-offline license are being removed: 
- only the same Windows user ID that reserved the license can hand it back
- the IP address of the portable computer must be the same as at the time
  of the reservation (so that it cannot be configured using DHCP)
- the same version of LUM client code (of the LUM-enabled product) 
  must be used to reserve and handback the license.
Note that the hostname of the laptop at handback time must still correspond
to the hostname that the machine had at reservation time. 

b. You are trying to define an authorization list for a Dassault product 
that should be used by a group of users in disconnected mode. The users 
belong to the same LUM group and you are granting them full access to the 
concurrent-offline license ("allowed" mode) using the name of the group. 
Nevertheless the users fail in reserving the license as offline license 
for their laptops.

c1. If you try to modify the max offline period of a concurrent offline
license you may get the following error message:
"CLN-142 Not all the Offline Periods have been updated"  

c2. If you try to modify the max offline period of a concurrent offline
license that is an upgrade key of a Custom Configuration license
you will get the following error message:
"ADM-10932 The maximum allowed Offline Period must be greater than 0 and
smaller than 1"
   
d. It can happen that the license server no longer starts under particular
network configurations of the machine, e.g. when it is defined inside an 
Active Directory domain or its DNS is misconfigured, and also when the
number of enrolled licenses increases. In general this depends on the 
expiration of the default timeout (30 seconds) the system waits for the
service to start, but in these cases the service needs more time. This 
patch introduces the possibility to customize this timeout through an
environment variable (I4TIMESERV=number of seconds) thus allowing the 
license server to run even in case of a slow start-up. 

Installation instructions
---------------------------------
Stop the license server (i4cfg -stop) and replace the i4ls.exe and i4lmd.exe
executables with the ones provided with this patch. The executables can be
found in:

C:\ifor\win\bin 
where C: is the drive where License Use Management Runtime is installed.

For defect c2. only: 
Download the new version of the i4_offline_mig identified as 4.6.8.2 from 
http://www-306.ibm.com/software/applications/plm/support/prodannounce.html
and run it.

Restart the license server (i4cfg -start)