I'm afraid thats due to design.

Basically on each space creation it takes a certain set of ServiceID's (which equal a service in configuration --> Servers --> servername1 --> IIS or something).

It will then only look towards those service id's when your inside that certain space.

a work around to come to mind is to setup 2 hosting plans each with the different servers (non-loadbalanced in virtual servers) and go from there.

yep had pretty much come to the conclusion of creating  new plans for each existing production server.  then create  new production balanced servers  for new customers

a new feature during space creation of  Balanced, Random, Manual select   would be great to force a server as well  for those one off times when you want a customer on a particular server

MIke

Cant it be created under a temporary account to import them, this will put them in the db and then edit the service ids to link them to the primary ?

I suppose not because once your hosting space has been created then all domains get placed onto that server where the hosting space was "load balanced"  or am I missing something here ?

The load balancing only load balances the spaces not the domains isnt it ? So the purpose of load balancing isnt very effective in my opinion as all of the users domains get placed on the same server, which makes it not very resilient if the server goes down.

The only way is to create multiple spaces using separate hosting plans on different servers to allow that customer to access the various domains. So a hosting plan in whmcs with multiple domains goes out the window.

I am new and having to get to grips with how this is done with solidcp from helm4 which load balanced the users domains across multiple web servers using one account.