Previous Topic

Next Topic

Book Contents

Book Index

Configure the Configuration Scheduling Server

Use the Server Manager to configure the Configuration Scheduling Service on each machine it is installed. The Configuration Scheduling Service is similar to the Cherwell Scheduling Service, except that it only handles Configuration Discovery and Inventory operations. When configuring the Configuration Scheduling Server, define:

To configure the Configuration Scheduling Server:

  1. Open the Server Manager.
  2. In the Server drop-down, select Cherwell Configuration Scheduling Server.

    Server Manager

  3. Click the Configure button.

    The Configuration Scheduling Server Options window opens.

    Configuration Scheduling Server Options Window

  4. Select which connection this CSM Server should use to connect to the CSM database:
    1. Connection: If the name of the correct database connection is not displayed, click the Ellipses button Ellipses Button to open the Connection window, where you can select an existing connection or configure a new connection.
  5. Select the login option for this CSM Server (that is, the method this CSM Server uses to log in to CSM):
    1. Windows Authentication: Select this radio button to use Windows login credentials.

      Note: To use this feature, Windows must be a supported login mode (Open CSM Administrator>Security>Edit security settings, select the Desktop Client, Browser Client, or Browser Portal, and in the Supported login modes section, select Windows). This CSM Server logs in to CSM using the account associated with the Windows credentials used by the Windows server.

    2. User ID and Password: Select this radio button to use Cherwell login credentials. Provide the Cherwell username and password.

      Note: This is usually an administrative account with broad system access, such as CSDAdmin.

    3. Blank password: Select this check box to allow a User to log in without a password. This only works if the specified account does not have a password assigned. This is not recommended.
    4. Execute Using Default Role of This User: Select this check box to run the CSM Server using the properties of the View associated with the Role that the login account is configured to use.

      Note: When this setting is not selected, this CSM Server uses a system default Role. However, control the behavior of Field properties in a View, based on the Role of the logged in User, by making this selection. In other words, based on a custom View for the Role of the person logging in (ex: IT Manager), the behavior of the Fields for a Business Object can be different when a record is created or modified.

  6. Test: Click this button to confirm that the login/connection works.
  7. Select a Scheduler Group to run, if you have more than one predefined.
    1. Click the Ellipses button Ellipses Button.

      The Choose Schedule Group window opens.

      Choose Schedule Group Window

      Note: The actions for scheduled items are selected and configured in CSM Administrator (CSM Administrator>Scheduling>Edit Schedule). Most Users will use the (Default) group, however if additional items need to be run at different times or for different purposes, these can be placed in separate groups, and run by different servers (ex: A SaaS customer may need to import Users into Active Directory at their company, which cannot be done in the SaaS environment. They could use one scheduling server to import to Active Directory at the company, and another SaaS scheduling server to run Default actions).

      Important: A single Scheduling Server will only run scheduled events for a single group. Normally, this will be the (Default) group, unless multiple services are configured.

    2. Select another displayed group, and then click OK.
  8. (Optional) If needed, you can click the Pause/Resume Processing button to stop or restart the Server processing (not the Server service). If the button is pressed while the Server is running, the server is paused, and you can enter the reason (ex: An administrator may be troubleshooting and wants to let his team know the reason the service was paused). When the button is pressed while the Server is paused, the server processing resumes.

    Note: There are two different methods that allow the service to be stopped. The first is to actually stop the service from running in the Service control panel applet, or by using the Stop button in the Server Manager. While this works, it requires direct access to the machine/image on which the service is running.

    The second method is to pause/resume processing. This can be done from the CSM Administrator by any user with sufficient security rights. In this case, the service is still running, but it will not process any records. The advantage of this approach is that it does not require access to the machine/image on which the service is running.

    For items to be processed, the service must be running, and must not be paused. You can resume processing from the CSM Administrator, or as a convenience, from the Pause/Resume Processing button in the Server Manager.

  9. Define where to store the Discovery and Inventory files and how often to delete the files:
    1. Click the Configuration Files button.

      The Discovery/Inventory Files window opens.

      Server Manager CDI Files Window

    2. Intermediate File Directories: Define where to store the following files:
      • Scan Files: This directory holds files that are being populated with information from the scanned devices. As soon as CSM is done with the file, it is moved into the Processed Files directory.
      • Processed Files: This directory holds files that have been read into CSM.
      • Processed Files with Errors: This directory holds files that could not be read into CSM due to an error.
    3. Clean out old processed files: Select this check box to periodically delete older files, and then select the Hours or Days radio button to define the threshold.

      Note: Only successfully processed files are deleted. Files with errors must be manually deleted. If Nmap is being used, the file location needs to be a location that Nmap can access (ex: Create a C:\nmap folder for files).

    4. Click OK.
  10. Click OK.

See Also

Configure a CSM Service

Configure the Application Server

Configure the Automation Process Server

Configure the E-mail and Event Monitor Server

Configure the Scheduling Server

Configure Logging for a CSM Server or Web Application