[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference noted::pwv50ift

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

4194.0. "New "simplified" licensing?" by GIDDAY::MITROVSKI () Wed Mar 05 1997 23:57

Hi all,

My understanding of the new CA - Client Access licensing is that a CA license
PAK can be configured as either client base or server base or as a combination
of both.But there are number of issues which I do not fully understand and I
need help to explain them to my customer.

1.If the licenses are used as server based,how many servers thay can legaly be
installed on?If,for example,a customer with 100 CCS licenses upgrades them to CA
licenses and then decides to configure them as server based,how many servers can
he install them on.

2.What is Designated Access License ?

3.Where can a customer obtain a license for Pathworks32 on NT v4.0 client?

4.Where can I get detailed information about the new licensing?

Thank you in advance for your replies.

Regards,
Marjan
CSC Sydney
T.RTitleUserPersonal
Name		DateLines
4194.1VMSNET::S_VORESmile - Mickey's Watching!Thu Mar 06 1997 07:4620
    a CA license *will* with new server-end code (5.0F/6.0) be able to be
    configured as either client-based or server-based.
    
    1. if used as server-based, my understanding (JG jump in) is that
    they'll be just like a server-based is today -- just good for that one
    server.
    
    2. DA is basicly a renamed FPA license, to be used exactly as an old
    FPA was used.  Use these until the new server code is released
    
    3. They can get it as soon as it ships (tomorrow, according to
    something I saw in the PATHWORKS 32 notesfile
    
    4. you can get information on the new licensing practices in a couple
    of places:
      the most recent Sales Update magazine
      http://prodmgt.lkg.dec.com/ 
      http://simba.alf.dec.com/desk/archive.htm
4194.2Jumping in...DELNI::GORCZYCAPATHWORKS Prod/Bus MgmtThu Mar 06 1997 08:3147
re: .0

My understanding of the new CA - Client Access licensing is that a CA license
PAK can be configured as either client base or server base or as a combination
of both.But there are number of issues which I do not fully understand and I
need help to explain them to my customer.

>>>
>>> Note that "Client Access" licenses are not available yet and may not be for
>>> several months, yet.
>>>

1.If the licenses are used as server based,how many servers thay can legaly be
installed on?If,for example,a customer with 100 CCS licenses upgrades them to CA
licenses and then decides to configure them as server based,how many servers can
he install them on.
>>>
>>> As Steve said in .1, the rules for PAKs still will apply: A single PAK can 
>>> only be installed on *one* system.
>>>
>>> So, if a customer has 100 CCS licenses, and they upgrade (or are upgraded) 
>>> to Client Access licenses, the number of servers they will be able to use
>>> employing server-based access will depend on the number the number of PAKs
>>> they have.  For example, if they have 100 PAKs with 1 license on each, they
>>> will be able to let 1 client attached to each of 100 servers.  However, if
>>> they have 1 PAK with 100 licenses on it, they will only be able to allow
>>> the use of 1 server, though up to 100 users will be able to access it
>>> (concurrently).
>>>

2.What is Designated Access License ?
>>>
>>> See .1: FPA == Designated Access (just a rename for clarity)
>>>

3.Where can a customer obtain a license for Pathworks32 on NT v4.0 client?
>>>
>>> Where? They buy licenses for PATHWORKS 32 from Digital and its partners.
>>>

4.Where can I get detailed information about the new licensing?
>>>
>>> In addition to the Sales Updates noted in .1, also check out the field 
>>> advisory in VTX/WEB IR, DOC ID = LI01PY
>>>
>>> John