Verifying First Time Startup - UNIX

1. Make sure that your Traverse license key is not expired. (<TRAVERSE_HOME>/etc/licenseKey.xml).
2. Start Traverse. Enter:

cd <TRAVERSE_HOME>;
etc/traverse.init start

1. Make sure that all the components started and are operating correctly by executing the following command:

traverse.init status

1. Typical start-up problems include:
   • an expired license key
   • another web server is operating on the server and using the httpd port
2. After you identify and fix any problem related to Traverse component start-up, restart Traverse:

traverse.init restart

1. In a supported web browser, navigate to http://your_host/, where your_host is the fully qualified name or IP address of the server on which Traverse is operating.

   Note: You can specify a port number other than (the default) 80 when installing Traverse. Remember to include this port number in the Traverse URL (for example, http://your_host:8080).

2. Enter your username and password (for example, traverse/traverse).
3. Add some test devices to verify that the system is functioning correctly.
4. Log out of Traverse. Then, log in as superuser with the password traverse. See Users and Departments if you want to create additional departments and administration groups.
5. Populate the system with devices. See Adding Devices to add devices.

Traverse Post Discovery Tasks

After running a discovery on your network or manually adding devices, Kaseya recommends that you do the following:

• Change the password for the default user and superuser (Administration > Preferences).
• Set the correct timezone (Administration > Preferences).
• Specify the page to display after logging in to Traverse. (Administration > Preferences). Select a page from the Set the page to... drop-down menu or select Other and enter a specific page in the Other field. For example, to specify the Manage Actions Profile page, enter:

user/manageActions.jsp

You can obtain the URL of pages by clicking on the anchor icon in the top right-hand corner of each page. See Show Page URL.

• Change the DGE controller password (see DGE Controller Port/Password).
• Update device dependencies and set up parent/child relationships if required to prevent alarm floods. See Device Dependency.
• Set up service containers as required to model your services. See Service Containers.
• Set up actions and notifications. See Actions and Notifications.
• Configure the Message Handler for monitoring traps and logs. See Message Handler for Traps and Logs.
• After using the system for two days, either update the thresholds manually if you are getting too many alerts, or use the "baseline" feature to automatically reset the thresholds. See Smart Thresholds Using Baselines.

IMPORTANT: If you want to use custom scripts to manage and maintain Traverse, you must contact Kaseya Professional Services before deploying these scripts in your Traverse environment.