EditINTRODUCTION
The initial implementation of Octopus requires a minimum of preparation. Pre configurations were applied to make the integration of the tool easier and faster. We have established a list below that will guide you in customizing your Octopus database. Some settings can be left as is, while others may require adjustments to reflect the reality of your operations.
EditGENERAL CONFIGURATION
EditStep 1: Octopus system account
Create an Octopus System account
EditStep 2: Users/computers import
a) Active Directory Integration
Import users and computers from Active Directory
and / or
b) Import users/computers/other data from an external data source
Import data from an external source: DataImporterEditStep 3: Identify Types of CI to be managed
Modify Types of CI
EditStep 4: Octopus user accounts
Creation of Octopus user accounts
EditStep 5: Saving of attached files
Configuration of attached files network folder
EditStep 6: Remote access software
Configuration of a remote access software
EditINCIDENTS MANAGEMENT
EditSTEP 1: Sending email messages to users
Activation of automated email messagesEditSTEP 2: Incident categories and sub-categories
Modify the categories / sub-categoriesEditSTEP 3: Incidents priorities
Modify prioritiesEditSTEP 4: Other reference data
Among the reference data, the following lists are to be configured:
- Templates
- Canceling reasons
- Pending reasons
- Suspend reasons
- Incident sources
- Activity types
Please refer to the article
Reference Data - Incidents to get explanations about configurations specific to incidents.
EditSTEP 5: Intervention Groups
By default, there are three (3) intervention groups in Octopus: Service Desk, Technical Support, Specialists, Telephony.
You can refer to the article
Organize work groups in a team for advice on this.
EditSERVICE REQUESTS MANAGEMENT
EditSTEP 1: Revise basic types of service requests
Please refer to the following articles to modify types of service requests: