We run a PS4 2-server farm. We also run an Exchange 5.5 mail server. All
are running on W2K Server.

We have a number of public calendars. If you view them using a direct
connection via Outlook 2003,they look fine. If you view them on one
Citrix server (CITRIX-H1), they look fine. However, if you look at them
on CITRIX-H2, you see the behavior expected when there is a DST problem.
This is where appointments that fall in the expanded date range (3/9 -
4/6) and exhibit strange behavior with "all day" appointments.

Any ideas what could be going on? Or a work around?

--

Regards,
Hank Arnold
Microsoft MVP
Windows Server - Directory Services

If it is safe to assume the Citrix servers are Windows 2000 based on the
opening statement, I would ask are you sure that the operating system has
had its time zone tables (registry keys) updated to reflect the extended
period? (e.g. Roll CITRIX-H2 system clock forward to this coming Sunday to
verify that it knows how to spring forward 1 hour at the designated hour.)


"Hank Arnold (MVP)" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> We run a PS4 2-server farm. We also run an Exchange 5.5 mail server. All
> are running on W2K Server.
>
> We have a number of public calendars. If you view them using a direct
> connection via Outlook 2003,they look fine. If you view them on one Citrix
> server (CITRIX-H1), they look fine. However, if you look at them on
> CITRIX-H2, you see the behavior expected when there is a DST problem. This
> is where appointments that fall in the expanded date range (3/9 - 4/6) and
> exhibit strange behavior with "all day" appointments.
>
> Any ideas what could be going on? Or a work around?
>
> --
>
> Regards,
> Hank Arnold
> Microsoft MVP
> Windows Server - Directory Services

neo,

I found an old KB article on manually updating the registry. I exported
the DST registry info from CITRIX-H1 and imported it into CITRIX-H2.
Rebooted and then ran a VB script to read it into the second required
location. Calendars are now correct on both servers.

I haven't a clue as to why one is correct and the other is not. I built
them both at the same time.

Anyway, it's OK now. Thanks for the reply....

--

Regards,
Hank Arnold
Microsoft MVP
Windows Server - Directory Services

neo [mvp outlook] wrote:
> If it is safe to assume the Citrix servers are Windows 2000 based on the
> opening statement, I would ask are you sure that the operating system has
> had its time zone tables (registry keys) updated to reflect the extended
> period? (e.g. Roll CITRIX-H2 system clock forward to this coming Sunday to
> verify that it knows how to spring forward 1 hour at the designated hour.)
>
>
> "Hank Arnold (MVP)" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
>> We run a PS4 2-server farm. We also run an Exchange 5.5 mail server. All
>> are running on W2K Server.
>>
>> We have a number of public calendars. If you view them using a direct
>> connection via Outlook 2003,they look fine. If you view them on one Citrix
>> server (CITRIX-H1), they look fine. However, if you look at them on
>> CITRIX-H2, you see the behavior expected when there is a DST problem. This
>> is where appointments that fall in the expanded date range (3/9 - 4/6) and
>> exhibit strange behavior with "all day" appointments.
>>
>> Any ideas what could be going on? Or a work around?
>>
>> --
>>
>> Regards,
>> Hank Arnold
>> Microsoft MVP
>> Windows Server - Directory Services
>
>