Excel 2003 =now() is returning wrong time on terminal server

We have Excel 2003 installed on our Terminal Server/Citrix box. The servers
are in the EST timezone and work fine for EST clients. When CST clients (or
any other timezone than EST) uses a worksheet with =NOW, it computes time
from EST. We've had to use the formula =now()-0.042 to compensate. This
problem is specific to Excel as Word, IE and even typing in 'Time' from the
command prompt returns the correct time computed with the Central time zone.
How do I correct this?

thanks
Pete

 

Peter,

Glad to see you moved this inquiry to this NG. Sorry to see that there has
not been a response yet.

Question....

You wrote:<!--coloro:blue--><span style="color:blue <!--/coloro-->
> This problem is specific to Excel as Word, IE and
> even typing in 'Time' from the command prompt returns
> the correct time computed with the Central time zone.<!--colorc--><!--/colorc-->

Did you use the same session when you tried Word, IE etc as well as Excel?

As I understand TS (very poorly), the timezone is set (or can be set) by the
TS client. So Excel should see the same timezone that Word, IE etc see.

However, I don't know how that is accomplished -- an environment varible or
otherwise. Perhaps Excel fails look at the mechanism that TS uses to set
the timezone.

Just some wild musings to stimulate discussion, I hope.


----- original message -----

"Peter J. Dickason, MCSE" <NOSPAMPeterdotDickasonatAirgasdotcom@email.com>
wrote in message news:OK8NHyMJKHA.4608@TK2MSFTNGP02.phx.gbl...<!--coloro:blue--><span style="color:blue <!--/coloro-->
> We have Excel 2003 installed on our Terminal Server/Citrix box. The
> servers
> are in the EST timezone and work fine for EST clients. When CST clients
> (or
> any other timezone than EST) uses a worksheet with =NOW, it computes time
> from EST. We've had to use the formula =now()-0.042 to compensate. This
> problem is specific to Excel as Word, IE and even typing in 'Time' from
> the
> command prompt returns the correct time computed with the Central time
> zone.
> How do I correct this?
>
> thanks
> Pete
>
> <!--colorc--><!--/colorc-->

 

Hi Joe,
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Did you use the same session when you tried Word, IE etc as well as Excel?<!--colorc--><!--/colorc-->

Yes for this testing I log on to a desktop so that I can be sure it is all
within the same session

<!--coloro:blue--><span style="color:blue <!--/coloro-->
> As I understand TS (very poorly), the timezone is set (or can be set) by
> the TS client. So Excel should see the same timezone that Word, IE etc
> see.<!--colorc--><!--/colorc-->

Yea that's what I would think too.
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> However, I don't know how that is accomplished -- an environment varible
> or otherwise. Perhaps Excel fails look at the mechanism that TS uses to
> set the timezone.<!--colorc--><!--/colorc-->

Yes something changed with Excel that it behaves differently and we now
believe that it coincides with either August or July's security updates. I
am going through the process of removing them to see what I can come up
with. I have multiple test servers so I am going remove all August and July
updates first to see if my theory has any merit, then if the problem
dissappears I can use my other server to remove one at a time to narrow
which update is the cuplrit. I will report back with my findings.

Pete

 

"Peter J. Dickason, MCSE" <NOSPAMPeterdotDickasonatAirgasdotcom@email.com>
wrote:<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Yes something changed with Excel that it behaves differently
> and we now believe that it coincides with either August or
> July's security updates.<!--colorc--><!--/colorc-->

Aha! That's valuable information.

But it still would be helpful if a TS MVP would kindly explain how
applications are supposed to acquire the timezone when accessed via a TS
client.

Assuming that you on the right track and this is a defect in an Excel
update, good luck in getting a timely fix from MS. ;-)


----- original message -----

"Peter J. Dickason, MCSE" <NOSPAMPeterdotDickasonatAirgasdotcom@email.com>
wrote in message news:ufhRl9XJKHA.1488@TK2MSFTNGP03.phx.gbl...<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Hi Joe,
><!--coloro:green--><span style="color:green <!--/coloro-->
>> Did you use the same session when you tried Word, IE etc as well as
>> Excel?<!--colorc--><!--/colorc-->
>
> Yes for this testing I log on to a desktop so that I can be sure it is all
> within the same session
>
><!--coloro:green--><span style="color:green <!--/coloro-->
>> As I understand TS (very poorly), the timezone is set (or can be set) by
>> the TS client. So Excel should see the same timezone that Word, IE etc
>> see.<!--colorc--><!--/colorc-->
>
> Yea that's what I would think too.
><!--coloro:green--><span style="color:green <!--/coloro-->
>> However, I don't know how that is accomplished -- an environment varible
>> or otherwise. Perhaps Excel fails look at the mechanism that TS uses to
>> set the timezone.<!--colorc--><!--/colorc-->
>
> Yes something changed with Excel that it behaves differently and we now
> believe that it coincides with either August or July's security updates.
> I am going through the process of removing them to see what I can come up
> with. I have multiple test servers so I am going remove all August and
> July updates first to see if my theory has any merit, then if the problem
> dissappears I can use my other server to remove one at a time to narrow
> which update is the cuplrit. I will report back with my findings.
>
> Pete
> <!--colorc--><!--/colorc-->

 

What is the Windows version of Terminal Services are you running?
Have you tried timezone redirection?

This setting also available in GPedit.msc

Thanks
Soo Kuan



--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Peter J. Dickason, MCSE" <NOSPAMPeterdotDickasonatAirgasdotcom@email.com>
wrote in message news:OK8NHyMJKHA.4608@TK2MSFTNGP02.phx.gbl...<!--coloro:blue--><span style="color:blue <!--/coloro-->
> We have Excel 2003 installed on our Terminal Server/Citrix box. The
> servers
> are in the EST timezone and work fine for EST clients. When CST clients
> (or
> any other timezone than EST) uses a worksheet with =NOW, it computes time
> from EST. We've had to use the formula =now()-0.042 to compensate. This
> problem is specific to Excel as Word, IE and even typing in 'Time' from
> the
> command prompt returns the correct time computed with the Central time
> zone.
> How do I correct this?
>
> thanks
> Pete
>
> <!--colorc--><!--/colorc-->

 

I am running Windows 2003.

I've tried the timezone policies and although it corrects the issue
connecting via RDP, it causes my ICA sessions to show time time in GMT so
I'm wondering now if it is a Citrix issue. I'll have to place a call to
them as well.


thanks
Pete



"Soo Kuan Teo [MSFT]" <sookuant@online.microsoft.com> wrote in message
news:ufX4FmaJKHA.1336@TK2MSFTNGP05.phx.gbl...<!--coloro:blue--><span style="color:blue <!--/coloro-->
> What is the Windows version of Terminal Services are you running?
> Have you tried timezone redirection?
>
> This setting also available in GPedit.msc
>
> Thanks
> Soo Kuan<!--colorc--><!--/colorc-->