Asking for LicenseServer serials from cus



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 21/10/2008 at 04:28, xxxxxxxx wrote:

    User Information:
    Cinema 4D Version:   R11 
    Platform:   Windows  ;   Mac OSX  ; 
    Language(s) :   C.O.F.F.E.E  ;

    ---------
    This is starting to feel like slowly pulling teeth :)

    Since I don't have a license server to test ,I wanted to buy
    a licenseserver myself to finally test my stuff,
    but the rep said I need a minimum of two Cinema seats to be allowed to buy it. ( It was about 150Euro btw if I got it right).

    So, please, what -specific- number are we asking our customers for?
    And how shall we explain for them what number it is we are asking for?

    This is an example from one of my customers now is waiting for a license of mine.
    (All x's are numbers that I've hidden for this post)
    First they sent me:

    CINEMA 4D R11 [11-0-1000] <<1010000xxx6>> Single

    CINEMA 4D R11 [11-0-1000] <<1010000xxx7>> Multi (x3) via server.

    What are they?
    What is "Single"?
    What is "Multi (x3) via server"?

    Since the number don't look like the DevKitchen example I asked them
    for their MultiLicense Number and got this;

    [11-0-200000xxx]

    Doesn't look like the DevKitchen example either!

    So how does the MultiLicense look?
    Shall it look exactly as the DevKitchen example?
    (Being 11 digits and maybe always start with a "2").

    Cheers
    Lennart



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 21/10/2008 at 06:25, xxxxxxxx wrote:

    I had a discussion with my rep and apparently LicenseServer buyers
    get their permanent serial in a sligthly different form than regular
    Cinema buyers.
    Regular licenses come as before like:
    <<1010000xxxx-ABCD-ABCD-ABCD-ABCD>> CINEMA 4D R11
    <<3230000xxxx-ABCD-ABCD-ABCD-ABCD>> Mod: Advanced Render
    << etc for more modules....>>

    While the License Server buyer get their serials like:
    CINEMA 4D R11 [11-0-1000] <<101000xxxxx-ABCD...>>
    Mod: Advanced Render [11-0-1002007] <<323000xxxxx-ABCD...>>
    Mod: ModuleName [xx-x-xxxx]<< etc for more modules....>>
    Multi-Licence (015) [11-0-200000174] <<201015xxxxx-ABCD...>>

    I did ask , as usual, for the first 11 digits which is the wrong part of
    the serial for a LicenseServer user.

    So I guess it is just the matter of explaining what part the customer
    should send.

    In my experience, more often than not, when a customer of mine is
    buying several plugins licenses at once, the person that is doing the purchase is some sort of secretary or office person not directly
    involved in using Cinema, hence need clear info what to cut and paste.

    Cheers
    Lennart



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 21/10/2008 at 06:45, xxxxxxxx wrote:

    Just to confirm, the multi license always starts with 20 followed by the number of obtained licenses. So it is exactly like described in the developer technotes.

    cheers,
    Matthias



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 21/10/2008 at 07:07, xxxxxxxx wrote:

    Yup, it's now more the "problem" to point out the correct part
    to a customer.

    Can I assume that the MultiLicense first eleven digits show up
    under the "personalze" window in the same manner as the other
    modules?
    Is that "Module" called "MultiLicense"?
    That would then be a second way to explain what number we
    need making plugin licenses.

    Cheers
    Lennart



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 21/10/2008 at 07:30, xxxxxxxx wrote:

    The multi license is not visible in Cinema4D's personalize window. It can be found in the license server software and is part of serial block obtained from MAXON.

    cheers,
    Matthias


Log in to reply