[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

4128.0. "PW5 - NT and Licenses" by ACISS2::STEWART () Tue Jan 28 1997 09:24

    Pardon me if this has been posted befoer but....
    
    I am migrating an existing VMS PW5 system from it's current domain -
    LANGROUP to a Windows NT domain PPRPSCNT. UAS merge finally worked and
    I have migrated my user accounts. When I change the PW servewr over to
    BDC and try to connect from the WINNT server I get the following error
    
    	Cannot connect to the remote machine at his time - no available
    license for NTSYSTEMNAME.
    
    Then the PW server messages the NT server that a license could not be
    found for the NTSYSTEMNAME .
    
    Customer has been told that no other software is needed to complete
    this migration. If I can't connect to the PW server I can't get the
    users migrated without having to kgo to each client and modify their
    network settings.
    
    At wits end
    Kenn
T.RTitleUserPersonal
Name		DateLines
4128.1VMSNET::P_NUNEZTue Jan 28 1997 10:3136
    
    Ken,
    
>    	Cannot connect to the remote machine at his time - no available
>    license for NTSYSTEMNAME.
>    
>    Then the PW server messages the NT server that a license could not be
>    found for the NTSYSTEMNAME .
    
    An NT client MUST have a license to connect/browse/etc.  That license
    can either be client-based (add't bits must be installed on each
    client) or it can be server-based (no bits added to client).  If you
    use the server-based license only, the WNT clients can't legally use
    PATHWORKS for Windows NT client software (that is, the server-based
    license is intended for clients that don't use PATHWORKS client
    software, but do need to access PATHWORKS v5 servers).  
    
>    Customer has been told that no other software is needed to complete
>    this migration. If I can't connect to the PW server I can't get the
>    users migrated without having to kgo to each client and modify their
>    network settings.
    
    Well, we shouldn't be held responsible for the customer getting 
    bad information.  Although technically, a license isn't "software", so
    saying "no other software is needed" isn't really untrue.
    
    You need to educate yourself on the license issue.  Since you're
    concerned about WNT clients, the best place to look is the noted::pwnt
    conference. 
    
    You could contact the Customer Software License Administration (CSLA)
    office at 1-800-DIGITAL (or 508-391-2255) to get them a temporary
    server-based license PAK (PWLMVMSCU05.00) until you can research and
    propose the appropriate license for your customer's environment.
    
    Paul