| Title: | Kit: Note 4229; Please use NOTED::PWDOSWIN5 for V4.x server |
| Notice: | Kit: Note 4229; Please use NOTED::PWDOSWIN5 for V4.x server |
| Moderator: | CPEEDY::KENNEDY |
| Created: | Fri Dec 18 1992 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4319 |
| Total number of notes: | 18478 |
I was just made aware that V5.0E & V5.0E-ECO1 license managers cannot
revoke PWXXWINAT07.00 licenses which have been assigned to clients.
This was a problem we first discovered during PATHWORKS V6 testing, but
the fix has not yet been incorporated back into the PATHWORKS V5 code
base.
Unfortunately there isn't a friendly workaround to this problem. If a
PWXXWINAT07.00 license really needs to be revoked I believe the only
workaround is to revoke all PWXXWINAT07.00 licenses which are assigned:
1) Unload all PWXXWINAT07.00 licenses
$ license unload PWXXWINAT07.00
2) Use the License Manager to resync the license count:
$ mc pwrk$license_manager
Products -> New : PWXXWINAT07.00
This will reset the PWXXWINAT07.00 license count to zero and revoke
all PWXXWINAT07.00 licenses which have been assigned to clients.
3) Reload the PWXXWINAT07.00 licenses
$ license load PWXXWINAT07.00
This makes the PWXXWINAT07.00 licenses available to the license
server again. If user-defined license groups are not being used and
PWXXWINAT07.00 licenses are served out of the "default" license
group, no further administrative work is necessary - the
PWXXWINAT07.00 licenses will be loaded by the license server the
next time a client requests a PWXXWINAT07.00 license. If
user-defined license groups are being used, use the license manager
(Products -> New : PWXXWINAT07.00) to reload the PWXXWINAT07.00
licenses and allocate them to license groups as desired.
We are now aware of the problem however, as always, if it is a severe
enough problem for your customers, please file a CLD to be sure it gets
the attention it deserves (and customers with the problem get a fix).
\steve
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 4241.1 | VMSNET::S_VORE | Smile - Mickey's Watching! | Wed Apr 02 1997 12:56 | 8 | |
It *appears*, with *very* limited testing, that when a PW32 client
removes a WINAT07.00 license from it's control panel (closes the
control panel, reboots the pc), it's also taken care of on the server.
This is not of course a good alternative, but may provide a workaround
for some.
| |||||
| 4241.2 | workaround from the client-side | CPEEDY::KENNEDY | Steve Kennedy | Wed Apr 02 1997 15:44 | 15 |
Yes, open your mind steve(k) and think of other options ....
.1> It *appears*, with *very* limited testing, that when a PW32 client
.1> removes a WINAT07.00 license from it's control panel (closes the
.1> control panel, reboots the pc), it's also taken care of on the server.
Yes, as SteveV points out, another workaround is to manage this from
the client side. Either the method SteveV mentioned or having the
client request the license from a non-existent group should cause the
client to revoke the PWXXWINAT07.00 license.
Thanks SteveV!
\steveK
| |||||