My server is 1 hours difference between the local time.
It's usually best to leave the server time correct and alone, other things tend to work out much better if you don't mess with it. As long as the server's time at the CLI reflects the time the office is in, and the time Zone also is correct, then the server's time functions should work as expected across the board. Anything else will likely break something.
And for clarity: There is no "the local call time". Local time is different for every lead you call and can literally be any hour of the day. Using a call time set as a "local time" in a campaign is unrelated to your time at your facility.
Your best bet would be to create a NEW call time set and set it to 8-8 or 10-10 or whatever your office hours are according to the time that the server will believe it is. This also has the added advantage of being named "Office Hours" instead of a time. And when your office hours adjust, you can adjust it without screwing up anything else or having to rename it. It would ONLY be for things that happen "only during office hours".
You can can also experiment with changing the Server's Time Zone in admin->servers. But remember that making any time zone changes may "shift" after a reboot, whereas creating a new call time set won't.