If server session timezone is changed, DateTime replication uses old timezone
When a GBS session flushes a Timestamp (in VW) or DateTime (in VA),
this has the side affect of initializing the cached value of the
server session's TimeZone. This TimeZone is stored in the server
instance of DateTime. If that GBS session then changes the
session's current TimeZone on the server, then flushes another
Timestamp/DateTime, it will have the original TimeZone when it
should have the second TimeZone.
Log out after changing the session's timezone.