sure an importing tool doesn't have to do all the job but at least recreate all configuration then the content we can move manually from a server to another
Helm has a very commercial approach to it's functions, it has a lot of billing functions and i never used as i have my own billing system and i work with more than one single plataform
it also isolate the websites giving a single NTFS user to each one of then but also it groups websites into a couple of IIS application polls
other control panels relay their security in creating a different application pool to each site what in IIS6 took 20mb of ram memory for each application pool what can be better in IIS7 according to microsoft it can handle hundred of application pools
helm also keeps information of a default application pool to be used with asp.net 1 and another to be used with asp.net 2
it has a internal structure that really is confused and takes a lot of time to configure a single reseller or customer
first if you want a customer you need to be his reseller and your main web site will be your first customer inside of your own reseller chain where you are your own reseller.. pretty confused
then if you have for instance CUSTOMER-A you have to fill a form with all data about this customer or reseller, address, phone number, etc
So let's no suppose customer A is a reseller, inside of customerA you will see another forms with all data about the customer-A's customers, and also his hosting plans what in WHM is called packages...
well in WHM it takes 3 screens to full create a new reseller but at helm it takes over than 10 screens
what is really odd is that besides the fact that you have this hosting plans in your reseller menu at helm the customer-A's customers has also in their menu a Package section where you can place 1 or 2 or as many as hosting plans you want or even customize this hosting plans so they are all duplicated in the database, this can be done in order to add one single email extra account to it's package without having to upgrade/downgrade an account in terms of WHM, it also means that you can have let's say 3 base hosting plans but you can customize each of then in a different way to each of your customers if you need
ok so if i were going to create a migration code from helm to cpanel importation i assume that my cpanel windows machine server 2008 has
MSDNS
IIS7
MSFTP (IIs6)
PERL+AWSTATS
MYSQL 5
PHP 5
ASP, asp.net 1 and 2, 3, 3.5 (with 2 application or more pools prior configures to asp.net 1 and 2) i dont know if cpanel will create a application for each single site so i am considering by now only a few pools)
the IIS as it has many parameters such as parent path, host header, virtual directories, etc it can be migrated with all site settings (maybe windows 2008 resource kit has a migrating tool from IIS6 to IIS7)
but to take this data from HELM SQL database *(helm 3 as helm4 has information stored also in other places)
well this script will read all domains name and especification and recreates
1) DNS
2) FTP and NTFS folders
3) IIS
4) MYSQL DBs, USERS
5) EMAILS
by the moment it will create the sites in WHM it could use a migration master package with 99999 of everything or it can copy the helm customersA package to each of his/her sites
as you know in helm we cannot easy determine which of the many domains of customersA is the reseller domains but it has a field named DNS MASK in the customer global account configuration menu and if it is different from blank there will be the resellers dns customersA main domain... Or in last case it can create a ficticious domain just to hold the other reseller domains and after this we manually adjust this at WHM at reseller center
well sorry for my poor english is just to give some general insight on this issue
Thanks
claudio



LinkBack URL
About LinkBacks
Reply With Quote
was completed and I dont see anything new, including no mention of the next beta test nor the forum to discuss Cpanel Windows / W2k8 issues.





