Kentico CMS installation consists of several steps depending on the installation type:
Installation on the local development machine
|•||Setup (kenticocms.exe) - installs only the web project files. No changes to the system configuration (registry, IIS or SQL Server) are made. You do not need to run the setup on your production server - it's intended primarily for development machines.|
|•||Web Installer - creates a new website project and optionally configures IIS or uploads the project to the server using FTP. Again, you do not need to run the Web Installer on your production server - you can run it locally and deploy the files over FTP.|
|•||Database setup - runs in the web user interface. It creates a new database on your SQL Server with system tables and basic data.|
|•||New site wizard - runs in the web user interface after you create a new database. It allows you to create a new site managed by Kentico CMS.|
Installation on the remote (production) server
On the remote (production) server, it's not necessary to run any executable or register DLL libraries. Unless you have full administrative access to the server, you will typically follow these steps:
|•||After you install Kentico CMS on your development machine using Setup (KenticoCMS.exe) you need to run Web Installer on your development machine and choose to install Kentico CMS on a remote server. Choose the temporary folder on your local disk.|
|•||Copy the files from the temporary folder to the production server (e.g. over FTP). If the files are not copied directly to the root of the website, you will need to create a virtual directory - see Additional configuration tasks -> Creating a virtual directory for details.|
|•||Open web browser and navigate to the root URL of the copied files on your web server.|
|•||The rest of the installation is the same as on the local machine.|
If you encounter any problems during the installation, please see the Troubleshooting installation issues chapter.
Tip: There's no magic behind!
Kentico CMS is a standard ASP.NET application. Since it doesn't make any modifications to the system, you can move it to another system as you do with any other ASP.NET project. You can also open the project in Visual Studio and debug it or compile it.
The database is a standard MSSQL database, so you can move it to another server using a common backup/restore procedure. The connection string is stored in the web.config file, in the ConnectionStrings/CMSConnectionString value.