Wrong ticket time after database migration

[canuck54]

After migrating the database from our on-premises server to the AWS server, the tickets are showing the wrong "ticket creation time" -> UTC. Our AWS server is set to UTC, while our on-premises server was set to GMT+1.

For our colleagues, the times should be displayed in GMT+1 again.

Is there any way to fix this?

Thanks!

[Riley · Accepted solution]

Hi @canuck54 

The timestamps in Lansweeper are generated at the system level, so they depend on the time settings of your Amazon server's operating system or the virtual machine (VM) where your Lansweeper server is hosted.

If you're running Lansweeper on-premises (on a Windows server), you can adjust the time zone to GMT+1 by following these steps:

1. Open Command Prompt or PowerShell as an administrator.
2. Enter the following command to set the time zone to GMT+1:

   tzutil /s "W. Europe Standard Time"

3. Verify the change with:

   tzutil /g

For servers hosted on Linux (e.g., if you're using our IT Agent on a Linux environment), you can use a similar command to set the time zone. For example:

sudo timedatectl set-timezone Europe/Berlin

Regarding your issue, since the AWS server is currently set to UTC while your previous on-premises server was in GMT+1, you'll need to adjust the time zone on your AWS server to GMT+1. You can follow the appropriate steps based on your server's operating system to achieve this.

Once the server's time zone matches the desired GMT+1 setting, your ticket creation times should display correctly for your colleagues.

Let me know if you have further questions or need additional assistance!