Bentley Communities
Bentley Communities
  • Site
  • User
  • Site
  • Search
  • User
Licensing, Cloud and Web Services
  • Welcome to Bentley Communities
  • Bentley's Communities
  • Licensing, Cloud and Web Services
  • Cancel
Licensing, Cloud and Web Services
Licensing, Cloud and Web Services Wiki What you need to know/request when splitting your Account
    • Sign In
    • Eastern Europe Continuity Plan
    • Guest Accounts - Review Access
    • +Web Services
    • +SES Activation
    • +CONNECTION Client
    • +CONNECT Advisor
    • +Federated Identity
    • +SELECTserver based Activation
    • +Pre-SELECTserver Based Activation
    • +Product-Specific Licensing
    • Understanding why you received a TL Invoice
    • Working from Home using Bentley Licensing
    • -Licensing Workflow
      • License Flowchart for Subscription Entitlement Service (SES) and legacy SELECTserver
      • +Understanding the Subscription Entitlement Service (SES) Workflow
      • +Licensing Announcements
      • Upgrade from Hardware lock (dongle) to CONNECT licensing
      • What you need to know/request when splitting your Account
    • How to leave a Product Review
    • +Serviços ProjectWise 365
    • About Bentley Trust Licensing
    • Customer Number, Account Number, Entitlements, Users
    • How to delete Bentley account and all related data
    • Support for non-Bentley technologies utilized by Bentley products
    • Support for V8i applications after December 31st, 2021
    • +Support Homepage - Localized
    • What you need to know/request when consolidating Accounts

    What you need to know/request when splitting your Account

    What is the purpose of this information?

    Sometimes changes in business require you to split your account into two separate entities.

    As with any new account, splitting an account represents an opportunity to adopt up-to-date, supported applications (older generation applications are not eligible for support), and change your licensing model for the better (the older SELECTserver based licensing [hosted or deployed] does not provide the same opportunities for license reporting and control that Bentley's current licensing model, Subscription Entitlement Service licensing does).

    Splitting an account also may represent the challenge to migrate all the settings previously applied to the existing  account, to the new account. There aren't any tools to assist with this, and at no time will an administrator have access to both existing account and new account to compare what might have been set up previously.

    The site administrators from each account we'll have to work together to ensure a smooth transition

     

    Areas affected when splitting an account

     Assets

    When an account is split the assets that reside at that account will be split as well. Subscription analytics can be used to determine what applications your user base is actually using (and what your peak use is for these applications) , prior to deciding how to split assets. 

    Entitlement Management

    The default access for any newly created account is that all users under that account have access to all licenses at that account. Any customizations that were in effect under entitlement management to either enable or restrict access to application licensing will no longer be in effect on the new account. 

    User Base

    Splitting your accounts also means splitting your user base. Although users will be migrated with their profiles intact (and this would include any roles previously assigned to the user), the newly-created account, with its newly migrated user base, will not have any allocation or entitlements groups set up previously. 

    Administrators

    It is not possible for a single administrators to manage multiple accounts under user management. Before going forward with a change, new individual should be designated as the administrator (and be aware of the responsibility of an Administrator) for the new account to be created

    Fulfillment Contacts

    The newly-created account will have to have a fulfillment contact. This may or may not be the same person that was for fulfillment contact on the existing account prior to the split.

    Domain Ownership

    If both entities that will exist after an account split will be using the same domain, if the domain has previously been claimed  the domain would need to be unclaimed as to allow its use by more than one account. Failure to do so may result in new users registering online being assigned to the incorrect account. 

    Licensing 

    Checked out Licenses

    Licenses reflected is being checked out on their entitlement management may have to be released, if the user of that license is going to be affected by the account split

    Offline Usage

    Depending on the current settings and entitlement management, users displaced from the original account may lose the ability to activate their software (for Subscription Entitlement Service licensing). Prior to the change it may be prudent to release offline restrictions on licensing to allow user 7 days of offline usage, instead of the user not being able to work (note that users working offline still generates usage towards an account). SELECTserver licensing based applications will function for at least 7 days while offline.

    Licensing - Subscription Entitlement Service licensing

    For subscription entitlement service-based licensing, users not listed under your account will not have access to your account's licensing. Shortly after a user has moved from one account to another changes to the users policy (which controls which licenses a user can access) happens organically every 4 hours, and the user will have access to their new accounts licensing.

    Licensing - SELECTserver based

    While Entitlement management based licensing doesn’t maintain the concept of "Site" (for subscription entitlement service-based licensing, licenses from all sites are aggregated under Entitlement Management under an "umbrella account" referred to as Ultimate), in Bentley's contract database individual sites are still maintained. The only consequence is that an account with multiple sites under contract will have multiple SELECTserver activation keys. The keys, although different, will still activate all aggregated applications from all sites by default (the applications each key will activate can be customized as well).

    The activation keys follow the site; If a site remains under the original account, the site activation key will remains with that account. If a site is redeployed to a new accounts contract, the new account will also have that site's activation key. If the new account does not have any sites redeployed from the existing account, the new account will have a new site activation key.

    Account still using select server-based licensing will have to be mindful that after a split a concerted effort to use the correct site activation key is made. Anyone having access to your site activation key also has access to your licensing.

    Prior to the split, site activation keys assigned to your account should be reviewed to determine if it is still prudent or necessary to have multiple sites (and therefore multiple site activation keys) for your account. It is not uncommon for an account not to realize that they have multiple sites / multiple site activation keys. Site consolidation (and the resulting elimination of redundant site activation keys) prior to an account split may be helpful (and easier to manage).

    When the accounts are split (depending on where a site is redeployed from existing account to new account), the new user base may have to point to a different site activation key than they were prior. Plans should be in place to distribute the new site activation key to your users. The newly-created account may wish to create custom activation keys instead of distributing their standard activation key, to allow more flexibility in managing their activation keys. 

    Before requesting an account split

    Make sure that under user management all the current information listed prior to the split is correct -

    • Users no longer with either the existing or new accounts have been removed from user management.
    • Assignments of administrator, and co-administrator are correct.
    • Assignments of user roles are correct.

    Decide how user base will be split -

    • Who will be the site Administrator for the new account?
    • Who will be the site Co-Administrator for the new account?
    • Who will the Fulfillment contact(s) be for the new account?
    • Provide Bentley an export of the users that will be moved to the new account.

    Have a game plan for how licenses are going to be managed under the new account

    • Note sites that should be consolidated or redeployed to the new account
    • Note any allocation or entitlement groups that need to be created under User Management.
    • Note any restrictions that need to be made or recreated under Entitlement Management.

    Note any changes from default settings for a select server activation keys and their associated entitlement groups.

    Schedule a time for the split to become official, and notify your users of the change.

    • Try to pick a time during which usage is minimal to minimize impact on your users.

    Inform the user base of the new account through their point of contact will be.

    • In order not to lose any productivity it is important that users know what to expect during the account's transition.

    After account split is complete

     Under user management

    • Verify that users have been redeployed as expected
    • Verify / assign Administrator and co-administrator roles
    • Create/recreate Allocation and Entitlement groups

    Under Entitlement Management

    • Verify / adjust default access at header of entitlement management is correct
    • Verify / adjust default access per product if necessary
    • Verify / adjust entitlement groups (Allowed Applications, Activation key mapping) as necessary

    On user's Workstations

    • Have users log out of, and back into CONNECTION Client and refresh their policy so that usage is now directed to the appropriate account.

    On user's Workstations (SELECTserver based applications)

    • If sites were consolidated or redeployed, distribute the surviving site activation key to users, eliminating any from sites that may have been consolidated
    • If no sites were redeployed, the new account will have a new site activation key that will need to be distributed to users

    Other Language Sources

    Deutsch

    • Share
    • History
    • More
    • Cancel
    • Brian D., User Success Support Created by Bentley Colleague Brian D., User Success Support
    • When: Wed, Feb 2 2022 1:19 PM
    • Jutta Eisenhauer Last revision by Bentley Colleague Jutta Eisenhauer
    • When: Wed, Sep 14 2022 7:21 AM
    • Revisions: 5
    • Comments: 0
    Recommended
    Related
    Communities
    • Home
    • Getting Started
    • Community Central
    • Products
    • Support
    • Secure File Upload
    • Feedback
    Support and Services
    • Home
    • Product Support
    • Downloads
    • Subscription Services Portal
    Training and Learning
    • Home
    • About Bentley Institute
    • My Learning History
    • Reference Books
    Social Media
    •    LinkedIn
    •    Facebook
    •    Twitter
    •    YouTube
    •    RSS Feed
    •    Email

    © 2023 Bentley Systems, Incorporated  |  Contact Us  |  Privacy |  Terms of Use  |  Cookies