row118
2003-11-21, 20:09 PM
the following are some of the steps I used in moving a site to Ensim control panel. There was some trial and error, but eventually worked. (I'm hoping that someone who has used the Import/Export Site Configuration may be able to smooth this out. )
Pre-Conditions:
1. The original virtual directory "customerdomain.com" pointed to c:\webspace\customerusername\customerdomain.com (locationwas chosen by Serverbeach upon install)
2. MeWebmail, MeAdmin, and a .NET app were virtual dirs
3. Ensim threw an "Site could not be started" error when customerdomain.com was installed via the Ensim panel. It did however install a duplicate customerdomain.com with the correct Ensim File structure. This duplicate entry will be inactive. the user was not added.
Steps I took:
1) Record the settings of the active(original) configuration. (this is where the import/exort feature may come in handy)
2) Delete the original site.
3) Delete the stopped site.
4) Readd site via Ensim
5) Reinstall webmail and webadmin. (In my case at least there was no loss of mail.)
6) Readd other apps or virtual directories and configure with saved settings
7) run aspnet_regiis -c (This may not be necessary if no .NET apps involved.
8) give the user created during the site installation access to database objects , in my case the SQL Server and MSDE databases accesssed by the .NET app.
I hope this helps.
Pre-Conditions:
1. The original virtual directory "customerdomain.com" pointed to c:\webspace\customerusername\customerdomain.com (locationwas chosen by Serverbeach upon install)
2. MeWebmail, MeAdmin, and a .NET app were virtual dirs
3. Ensim threw an "Site could not be started" error when customerdomain.com was installed via the Ensim panel. It did however install a duplicate customerdomain.com with the correct Ensim File structure. This duplicate entry will be inactive. the user was not added.
Steps I took:
1) Record the settings of the active(original) configuration. (this is where the import/exort feature may come in handy)
2) Delete the original site.
3) Delete the stopped site.
4) Readd site via Ensim
5) Reinstall webmail and webadmin. (In my case at least there was no loss of mail.)
6) Readd other apps or virtual directories and configure with saved settings
7) run aspnet_regiis -c (This may not be necessary if no .NET apps involved.
8) give the user created during the site installation access to database objects , in my case the SQL Server and MSDE databases accesssed by the .NET app.
I hope this helps.