From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_007F_01C766D9.848F7900
Content-Type: text/plain;
        charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

   Events tied to local time don't get affected by DST changes.  They =
only care that the local time is correct.  The issue with appts in =
Outlook are that they are stored in UTC and when you created them the =
relationship between local time and UTC was incorrect so the UTC time =
associated with the event is incorrect.  The tool you run fixes these =
incorrect times.

   There are plenty of applications that look at your Outlook data =
without Exchange or you having run Outlook.  I couldn't begin to tell = you
the features of all of these.

Rich

  "Geo."  wrote in message =
news:45f91ce1$1{at}w3.nls.net...
  "Rich"  wrote in message news:45f6ba43{at}w3.nls.net...
  >>   I bet your system scheduler events to which you refer are at jobs =
or=20
  >> tasks scheduled in local time and not adjust for time zone =
changes.<<

  Huh? Local time changes with the time zone so what are you talking =
about not=20
  adjusted for time zone changes? You mean if I view a machine in =
california=20
  (from ohio) I see scheduled events in california time? Could be, I use =

  PCanywhere to do that so that's exactly what I would expect to see.

  >>  Outlook appts and the like do vary by time zone as you would =
expect.=20
  >> That you don't get notification unless Outlook is running is =
specific to=20
  >> your configuration.  I do on my phone.<<

  Again, Outlook without Exchange, how would you view remotely? How =
would you=20
  get notification without having outlook running?

  Geo.=20

------=_NextPart_000_007F_01C766D9.848F7900
Content-Type: text/html;
        charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable








   Events
tied to local time =
don't get=20
affected by DST changes.  They only care that the local time is=20
correct.  The issue with appts in Outlook are that they are stored
= in UTC=20
and when you created them the relationship between local time and UTC = was=20
incorrect so the UTC time associated with the event is incorrect. 
= The tool=20
you run fixes these incorrect times.
 
   There are
plenty of =
applications that=20
look at your Outlook data without Exchange or you having run =
Outlook.  I=20
couldn't begin to tell you the features of all of these.
 
Rich
 

  "Geo." <georger{at}nls.net>">mailto:georger{at}nls.net">georger{at}nls.net>
wrote=20
  in message news:45f91ce1$1{at}w3.nls.net..."Rich"=20
  <{at}> wrote in message news:45f6ba43{at}w3.nls.net...>=
>  =20
  I bet your system scheduler events to which you refer are at jobs or=20
  >> tasks scheduled in local time and not adjust for time =
zone=20
  changes.<<Huh? Local time changes with
the time zone so =
what are=20
  you talking about not adjusted for time zone changes? You mean if =
I view a=20
  machine in california (from ohio) I see scheduled events in =
california=20
  time? Could be, I use PCanywhere to do that so that's exactly what =
I would=20
  expect to see.>>  Outlook
appts and the like do =
vary by=20
  time zone as you would expect. >> That you don't get =
notification=20
  unless Outlook is running is specific to >> your=20
  configuration.  I do on my
phone.<<Again, Outlook =
without=20
  Exchange, how would you view remotely? How would you get =
notification=20
  without having outlook running?Geo. =


------=_NextPart_000_007F_01C766D9.848F7900--

--- BBBS/NT v4.01 Flag-5