Hello,

Sounds like an odd situation.

In essense you only need the cipher key from the Enterprise Web.config to re-use the old db and avoid any importing aspects.

SolidCP supports the import of most resources, just note that anything in the Hosted Organization does not have an import feature, this will need to be manually done with the Enterprise import.

Additionally, Things like Databases will lose the function to backup etc, untill the password of the user has been reset (so the panel has the correct password again).

Most important: You might experience some importing issues due to the exact name existing that it tries to create/import to in SolidCP, i only seen this a few times so hopefully this won't happen to you, if/ when it does a simple rename of the thing you try to import will fix it 🙂

Regards,

Marco

Hi Marco,

Thanks for reply, indeed it is a very odd situation and a very annoying one!

With no access to the OS I am assuming the the cipher cannot be obtained from within SCP Portal itself?

I can create new servers for web and mail (no hosted organizations thankfully!) and create everything clean, not ideal if not required but if you think i may run into issues then it might be worth it?

Thanks

Well web.config you can always fetch if you still can obtain file access to the disk.

but not through the SolidCP Portal.

Importing resources should be fine, re-creating things till probably give you more headaces then potential import issues.

Hi Marco,

Just wanted to provide some feedback with this to help others.

1. I built a new Enterprise Server with new SQL database
2. Detached all resources on my servers
3. Changed the SCP Server password on both and attached to new Enterprise Server
4. Changed the portal to use the new Enterprise Server
5. Configured server services as usual
6. Created Hosting Plans/Virtual Servers and created new customers
7. Provided each customer a hosting plan but DO NOT create any space resources
   1. Note - This creates a new Hosting Space folder (i.e. your existing space may be MYUSER it creates a MYUSER1)
8. Import the resources from each server (which copies, not moves, all data from the original hosting space into the new one and updates services like IIS to reflect the change)
9. Remove the old Hosting Spaces folder (MYUSER - not 1)
10. (optional) Because of my OCD, and i didnt want customers to realise that something had changed, i wasn't happy with the hosting spaces folder now having a 1 at the end so i detached all resources again, removed the hosting plans for all customers, create new hosting plans (which now didn't have the 1 at the end), re-import all services.

Issue 1:  The only issue I have come across so far is DNS.  Whilst the DNS successfully imported it removed the 'Notify' option for sending updates to secondary zones.  I had to set this flag manually on each primary zone to ensure it updated its secondary zones.  New domains created worked fine before this but existing imported zones did not send the changes to the existing secondary zones.

Hope this helps anyone with a similar "unusual" situation

I will update if i find any more issues.