Search Engine: Elastic

Article ID: 120299, created on Feb 25, 2014, last review on May 8, 2014

  • Applies to:
  • H-Sphere 3.6.3


Parallels H-Sphere introduces Allocated Servers which allow assigning *nix physical servers to resellers so their end users' homes are created on it (to allocate Windows servers, refer to Placing Resellers on Separate Boxes). Physical servers are assigned to reseller plan, so every reseller signing up for it obtains one of them. In case there are no allocated servers available for the plan, reseller signing up with it, will be moderated and you will be notified of it through trouble ticket system.


  1. Make sure it meets all of the following requirements:

    • physical server is assigned all of and only these server groups: WEB, MAIL and MySQL
      • if any of these server groups isn't assigned or the physical server is assigned another type of server group, E.Manager -> Servers -> Allocated servers won't list it as an allocated server.
    • physical server is associated with all three logical servers: Web, Mail and MySQL
    • the logical servers assigned must not be used by any accounts
    • none of the associated logical servers is involved in a content move
  2. Go to E.Manager -> Servers -> Allocated Servers. You will be taken to the list of physical servers meeting the above requirements in the Search Results section:

  3. Click Assign Server to Plan (the Controls section) for the physical server you are allocating.
  4. On the next page, choose the reseller plan you want to add this server to:

    The allocated server's state in the Search Results table will change from Unassiged to Available. This means the server is ready to be taken by a reseller.

  5. To allow resellers to obtain an allocated server, include Allocated physical server resource in the reseller plan wizard
  6. Sign up a reseller for this plan, and he will automatically get the physical server. The server's state in the Search Results table will change from Available to Taken.

6b908665c0d1eca5bdd0141a32fd712a 6311ae17c1ee52b36e68aaf4ad066387 f213b9fa8759d57bee5d547445806fe7 2e39a5e5b1423cc126cf735bac076008

Email subscription for changes to this article
Save as PDF