Steps to Install CSM
The installation steps vary depending on which installations are run (Server, CSM Web Applications, and Client), whether it is a new installation or an upgrade, and whether Auto-Deploy is used.
| Task | Notes |
|---|---|
| 1. Add Windows Features to the IIS Server. | See Add Windows Features to the IIS Server. |
| 2. Run the Server installation. | See
Run the Server
Installation to install the Server application and services files.
Download and install any third-party tools as prompted by the installer. |
| 3. Configure the Server connection. | See
Configure the
Server connection.
This is a direct-to-database (2-tier) connection between the Cherwell Application Server and the CSM database. |
| 4. Run the Portal and Browser Apps installation. | See Run the Portal and Browser Apps installation to install the Browser application files. |
| 5. Configure the Browser connection. | See
Configure the
Browser connection when prompted by the Portal and Browser Apps
installation.
This is a direct-to-database (2-tier) connection between the Cherwell Browser Apps and the CSM database. |
| 6. Configure and start the Cherwell Service Host and CSM services. | See Configure and start the Cherwell Service Host and CSM services. |
| 7. Configure Auto-Deploy. | See
Configure
Auto-Deploy to push out the Client installation and connection to client
machines.
During the Auto-Deploy configuration, the configure the
Client connection that are auto-deployed must be configured.
|
| 8. Reboot the installation server. | If you installed CSM and Portal and Browser Apps on different servers, reboot both servers. |
| 9. License CSM. | See License CSM |
| 10. Log in to CSM Administrator. | Use the default credentials (username =
CSDAdmin, password = CSDAdmin), and complete these configuration tasks:
|
| Push out Client installations using Auto-Deploy. | See
Using Auto-Deploy.
New users must access the system administrator designated
web page to run Auto-Deploy. Existing users are prompted to install the new
version when they next run
CSM locally.
|