Time Zones different between Central Server and Client
Hi, guys:
Our machine running in server mode is in Pacific Time. We scheduled a deployment for 4:00 AM tomorrow morning from a client machine whose clock is in Eastern Time.
All machines, either client or server mode, see the deployment as scheduled for 4:00 AM, and seem to be calculating the Next Run time based off of their own Windows time: the server and my main client machine are in Pacific Time and think the deployment's Next Run is 15 hours; my colleague's client machine (this is the machine that scheduled the deployment) shows that the Next Run is in 12 hours. I checked on another client machine in Eastern Time, and that also thinks that the deployment's Next Run is in 12 hours.
Which machine is right? Will it deploy at 4:00 AM Eastern because that's the timezone of the machine that scheduled it, or will it deploy at 4:00 AM Pacific, because that's the time zone of the machine in server mode?
We are running the most recent release of Deploy (15.4.0.0 Enterprise Mode)
Comments
I think you found a bug. In my lab the Server and Client show the correct time based on time zone. Please talk to support@pdq.com
So good news, I can't reproduce this error again today. In case anyone is searching forums later, the deployment ended up going off of the central server time (4:00 Pacific).
We scheduled the same package from the same client PC today, and all machines are agreeing that the schedule will run in 11 hours with the trigger time being displayed based of the local machine's time zone. (I.E,, Eastern PCs show that as 7:00 AM and Pacific PCs show that as 4:00 AM.)
I blame Groundhog's Day and time loops, I guess.