Submit a ticketCall us

AnnouncementsWeb Help Desk Integrations eCourse

Looking to reduce response times? Sign up for our eCourse to learn how integrating Web Help Desk with Dameware Remote Support, Network Configuration Manager, Network Performance Monitor, and Server & Application Monitor can improve communication efficiencies.

Register here.

Home > Success Center > Network Performance Monitor (NPM) > Managing report schedules with multiple Orion instances across different time zones

Managing report schedules with multiple Orion instances across different time zones

Table of contents
Created by Michael Perez, last modified by MindTouch on Jun 23, 2016

Views: 1,330 Votes: 5 Revisions: 3

Overview

This article addresses concerns introduced with managing report schedules if you have multiple Orion instances that are located in different regions and time zones.  

Environment

All NPM versions

Detail

The statistics that Orion collects are stored in UTC and the Web Console presents the information in relation to the time zone where the user logs in from. If you are logged into the Web Console from Florida, the time results will be presented in relation to the Eastern Time zone even if the server is located in California. If you would like the reports to be delivered to users who are in the same time zone as you, this is convenient. If you are remotely scheduling reports that are going to be delivered to the California office, you would have to manually factor in the offset for that region when scheduling the reports. Another workaround would be to remotely log into the server in California, visit the Web Console from that server and schedule the reports from there to eliminate the time offset.  

 

Last modified

Tags

Classifications

Public