Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Verified Answer
  • Replies replies
    2
  • Subscribers subscribers
    171
  • Views views
    223
  • Users 0 members are here
Related
Options

Can we keep SBM 11.8 but upgrade PVCS to 8.7.0?

pbustin

PVCS 8.7.0 requires the Auto-Pass License Server. 

Questions:

     1)  Can SBM 11.8, that we will need to view but not use for 7 or so years, and for which we have no Support (but own the licenses) work with Auto-Pass, now and with possible upgrades if we upgrade PVCS now and in the future? 

     2)  Alternatively, can SBM 11.8 work with our current License Server (2.3), independent of PVCS? 

If it's relevant, we plan to continue to use SBM SSO as the PVCS login just so that PVCS users don't have to log into the PVCS web client, but if necessary, we can switch PVCS login to LDAP.

  • Verified Answer

    +1  

    SBM 11.8 will not work with autopass. It only works with SLM. As long as you don't stop SLM and its MAC address doesn't change, you can keep using SLM and SBM together, just as you do today.

    I don't think this impacts the PVCS SSO login, but let's get feedback from   too.

  • Verified Answer

    +1   in reply to   

    Hi Phil,

    The SLM and APLS license servers can happily co-exist on the same machine. They use different ports, so there is no conflict. As mentioned by Vickie, you can let SBM 11.8 continue to use SLM 2.3.0.

    You would only migrate the Version Manager licenses to APLS 24.1 by using the "Update" feature on the SLD site (Software Licenses & Downloads). When you select PVCS Version Manager 8.7 there, it will generate an APLS license.

    On SSO: my VM 8.7 instance has been using SSO licenses from both VM 8.6.3 (based on SBM 11) and VM 8.7 (based on SBM 12) without issues.

    Kind regards,

    - Richard.

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.