What changes were made to time zone handling?

  • Document ID:7018031
  • Creation Date:08-Sep-2016
  • Modified Date:08-Sep-2016
    • Micro Focus Products:
      Secure Configuration Manager

Environment

NetIQ Secure Configuration Manager 6.1

Situation

Secure Configuration Manager 6.1 updates the way time zones are handled.

Previously, whenever running a policy template, a security check, scheduling a job, or performing any activity in the Secure Configuration Manager console, the time zone of the Secure Configuration Manager Core Service/Database was considered. This caused discrepancy if the Console and the Secure Configuration Manager Core Service/Database are not in the same time zone.

Resolution

Secure Configuration Manager Console now uses the local time of the Console computer for any activity. All the time fields are populated with local time instead of Secure Configuration Manager Core Service/Database time.

To enable this, the following are implemented:

  • Secure Configuration Manager Core Service / Database use Coordinated Universal Time (UTC) as the time zone by default.

  • Secure Configuration Manager Console uses the local time zone of the Console computer. It converts all the time fields from the local time zone to UTC when performing an operation and also converts the fields from UTC to local time zone while displaying any data on the Console. 

Cause

Previously the time zone of core services and the database was used.