Submit a ticketCall us

WebinarVisual Monitoring Tactics: Getting More Log Search Value from SolarWinds Log & Event Manager with nDepth Webcast

Do things seem to make more sense when they are visualized? Are you an IT professional or security expert with a wish for more cybersecurity tools that provide an intuitive visual experience? Join Alexis Horn and Jamie Hynds from SolarWinds as they demonstrate how the nDepth feature in LEM can help make visualizing log search results a reality.

Register now.

Home > Success Center > Network Configuration Manager (NCM) > NCM - Knowledgebase Articles > Time mismatch between Job Schedule Time and Next Run Date in NCM

Time mismatch between Job Schedule Time and Next Run Date in NCM

Updated September 19, 2017

Overview

This article explains why there may be a difference in the time when scheduling a job and the Next Run Date.

Environment

  • All currently supported NCM versions

Cause 

The mismatch is caused by the fact that the Job Schedule time is set to use the UTC database time zone, but the Next Run Date will display the time using the local time of the machine which you used to access the Orion Web Console.

Resolution

Currently there is no way of changing this as the database time zone is hard coded in the application, and Web Console is set to use the browser time zone, which is taken from the machine's local time.

 

The scheduled job will run based on the UTC time zone, so the time in which you want to run it must be converted to UTC.

 

 

Last modified

Tags

Classifications

Public