Dotnetpanel Forums

 Has anyone on the forums got real life experiences of migrating large scall Helm v3 deployments to DNP?  By large scale I'm talking 100's of resellers, thousands of users/domains spread across multiple servers...

There is no automated way to do it.. You need to import Domains 1 by 1 into DNP's space using Import feature.

openmind:

Has anyone on the forums got real life experiences of migrating large scall Helm v3 deployments to DNP?

Although I have not tried to use the import tool just getting things 'ready' is a job all in itself.

Take a look at some of my other posts on here and MailEnable's website.  If you have other questions I might be able to help you avoid some of the same pitfalls... Especially since you'll probably be using the latest 2.8.10 DNP during your conversion.

There is no migration tool available yet so  you have to create users & hosting space manually and by using DNP import resource tool you can import the existing resources IIS, SQL,Mail, to the user space.

openmind:

 Has anyone on the forums got real life experiences of migrating large scall Helm v3 deployments to DNP?  By large scale I'm talking 100's of resellers, thousands of users/domains spread across multiple servers...

 

Phil,

am in the same boat as you!  I run Helm3 on my legacy windows 2003 hosting and DNP on 2008 hosting.  DNP does not allow overselling so even if there was a tool to move, you'd end up with lots of angry resellers who all of a sudden can no longer create new spaces.

Hi,

I've used HELM4 before switch to dotnetpanel and my experience so far is just OK to use for SMB's and unfortunately DNP offers a lot less core control panel functionality compared to HELM4. Again this is compared to HELM4 thought.

Kind Regards,
raja

OK I've safely established I have a lot of work coming my way then ;)

 I've made the decision to go ahead though and yesterday purchased a Standard control license and remotes for all the other servers.

 Now I recall it is possible to run Helm and DNP side by side so I'm working my way through the boxes getting everything setup now. However I've come across my first question...

I plan to use DNP for all new signups and continue to use Helm for existing customers until I can migrate them over. When setting up services in DNP however, is it best to create new containing folders or use existing Helm ones?

For example, on my SmarterMail server I have all the Helm mailboxes setup in E:\Mail and then a sub folder for each domain. Should I create a new folder for DNP and name it say E:\DNPMail so the two don't conflict?

Will I still be able to import the old Helm domains into the new folder when I'm ready?

You can use the same folders for SM, SS, FTP as Helm ones .. for domains it doesnt matters because DNP's domain directory structure is different then Helm's . All domain goes under username directory under Domain folder.

openmind:

Also when setting up the OS service on a webserver with IIS installed for domains, should I set the HostingSpaces path to my Helm domains folder so E:\Domains tr to a new folder i.e. E:\HostingSpaces ?

Either ways .. If you setup E:\Domains and a user adds any domain then domain will be added under following dir

E:\Domains\user\domain.com (not the way helm works. Helm adds it like E:\Domains\domain.com but DNP one is different so it doesnt matter and wont mess up existing data/files)

Rubal:

E:\Domains\user\domain.com (not the way helm works. Helm adds it like E:\Domains\domain.com but DNP one is different so it doesnt matter and wont mess up existing data/files)

 The exception here being that if your moving customers around and create a user called domain.com with a domain.com then this could be a problem, really just depends on how he's moving his customers.  Personally for the websites I'd put them in another directory and never have to worry.

jdraggi:

Rubal:

E:\Domains\user\domain.com (not the way helm works. Helm adds it like E:\Domains\domain.com but DNP one is different so it doesnt matter and wont mess up existing data/files)

 The exception here being that if your moving customers around and create a user called domain.com with a domain.com then this could be a problem, really just depends on how he's moving his customers.  Personally for the websites I'd put them in another directory and never have to worry.

good point. Having username same as domains name can mess it up.. So better to have seperate dir..