Zum Hauptinhalt springen
Deutsch
|
English

CURRENTTIMEZONE - Detailed description

FM-Portal

IC2877
FM-Portal

Overview

Parameter:CURRENTTIMEZONE
Category: Default
Default value: TimeZoneInfo.Local.Id (Server time zone)
Product: eTASK.FM Portal

What does this parameter do?

This parameter sets the default time zone that the eTASK Portal uses for displaying and processing date and time information. The time zone is particularly important when the server and database operate on UTC (Coordinated Universal Time), but users want to see local times. Each user can also set their personal time zone in their user profile, which then overrides this default time zone.

What is this parameter used for?

  • Definition of the portal-wide default time zone for all time information

  • Conversion between UTC database times and local display times

  • Correct display of appointments, bookings, and deadlines

  • Time zone conversion for room bookings and calendars

  • Fallback time zone if users have not configured a personal time zone

  • Synchronization with Exchange Server for room bookings

  • Foundation for date- and time-based calculations throughout the portal

Technical Details (for Administrators)

Format: String (time zone identifier according to .NET TimeZoneInfo)
Default value: TimeZoneInfo.Local.Id (set to the server's time zone at startup)

Valid values:

All time zone IDs supported by .NET. Important examples:

  • "W. Europe Standard Time" = Central European Time (Germany, CET/CEST)

  • "Central Europe Standard Time" = Central European Time (alternative name)

  • "UTC" = Coordinated Universal Time (no daylight saving time)

Important notes:

  • The time zone identifiers are Windows-specific and differ from IANA time zones

  • If an incorrect time zone is specified, the server time zone is used automatically

  • Users can set a different personal time zone in their profile

  • The user’s personal time zone takes precedence over this parameter

  • The portal internally uses the time zone defined here

  • When operating in UTC, this parameter MUST be set to the desired local time zone

  • Daylight saving time changes are automatically taken into account

Interaction with other parameters:

  • User profile time zone: Individual time zone per user overrides CURRENTTIMEZONE

  • Exchange integration: Important for correct room booking times during Exchange synchronization

Functionality:

The portal uses a hierarchy to determine the current time zone:

1. If the user is logged in AND has configured a personal time zone → use user time zone
2. Otherwise → use CURRENTTIMEZONE (this parameter)
3. If CURRENTTIMEZONE is invalid → use server time zone as a fallback

All UTC times from the database are converted to the corresponding time zone before being displayed to the user. All user inputs are converted back to UTC for storage.

When should you change this value?

Change the value to the desired time zone if:

  • The server is in a different time zone than your users

  • You need a uniform time zone for all users without personal configuration

  • After moving the server to a different geographic region

  • For international installations with a main location in a specific time zone

  • Compliance or legal requirements mandate a specific time zone

Leave the default value if:

  • The server and users are in the same time zone → standard

  • The server time zone is already configured correctly (e.g., "Western European Standard Time")

  • There are no special requirements for time zone handling

  • Users configure their time zones individually in their profiles

Important Notes

  1. Use correct Windows time
    zone identifiers Use the exact Windows time zone names. "Europe/Berlin" (IANA) does NOT work. The correct format is "W. Europe Standard Time" or "Central Europe Standard Time".

  2. Determine the list of available
    time zones To view all available time zone IDs, you can run the following in PowerShell on the server: [System.TimeZoneInfo]::GetSystemTimeZones() | Select-Object Id, DisplayName

  3. Note the daylight
    saving time change Most time zones have automatic daylight saving time adjustment built in. You do not need to change CURRENTTIMEZONE twice a year. The change occurs automatically.

  4. User profile time zone takes precedence
    If users have configured a time zone in their profile, it overrides the CURRENTTIMEZONE parameter. CURRENTTIMEZONE serves only as a fallback and default for new users.

  5. Perform a test after making changes Be
    sure to test the following after changing the time zone:
    - Display of appointments and bookings
    - Creation of new appointments
    - Room bookings (especially with Exchange)
    - Deadlines and due dates
    - Timestamps in logs

  6. IIS restart required
    After changing this parameter, the IIS application pool must be restarted for the new time zone to take effect.

Security

Does changing this parameter affect security?

No, this parameter has no direct security implications.

Security best practice:

  • Document time zone changes in change management

note6475702e-def2-4773-b75e-75aa32316e90

Recommendation: This parameter is functional, not security-related. Configure it correctly for accurate time display, but do not treat it as a security parameter.

Recommendation: This parameter is functional, not security-related. Configure it correctly for accurate time display, but do not treat it as a security parameter.

For Germany/Central Europe:"W. Europe Standard Time"
For international installations: Time zone of the main location

Reason:

  • Explicit configuration is more robust than the default value

  • Prevents problems during server migration or time zone changes

  • Automatic daylight saving time adjustment without manual intervention

  • Users see times that are locally understandable

  • Consistent time display for all users without personal configuration

  • Correct Exchange synchronization for room bookings

Recommended settings by region:

  • Germany, Austria, Switzerland: "W. Europe Standard Time" or "Central Europe Standard Time"

  • United Kingdom: "GMT Standard Time"

Best practice architecture:

  1. CURRENTTIMEZONE: Set to the primary user's target time zone

  2. User Profile: Individual time zones for international users

Configuration steps:

  1. Determine the time zone of your primary user group

  2. Find the correct Windows time zone name

  3. Set CURRENTTIMEZONE to this value

  4. Restart the IIS application pool

  5. Create test appointments and check the time display

  6. Test room booking with Exchange (if used)

  7. Document the configuration in the operating manual

Special case: International user groups

If you have users in multiple time zones: - CURRENTTIMEZONE = time zone of the main location or UTC - Ask users to configure their personal time zone in their profile - Document the time zone configuration in the user manual - Train the help desk on time zone configuration

Maintenance:

  • No regular adjustments required (daylight saving time is automatic)

  • Adjust only in case of a server migration or organizational change

  • If there are issues with time display, check CURRENTTIMEZONE first

  • Document every change with a reason and date

notee5578b12-458b-45f4-b6bf-57ce32a3db12

Important: After every change to CURRENTTIMEZONE, the IIS application pool must be restarted. Schedule the change outside of peak working hours.

Important: After every change to CURRENTTIMEZONE, the IIS application pool must be restarted. Schedule the change outside of peak working hours.

War dieser Artikel hilfreich?