Daylight Saving Time effects on 7.5

[Tim Gleason]

We were caught by surprise with the recent email sent by PeopleCube regarding the changes to Daylight Savings Time (DST) and the effects on Meeting Maker. We have an installation of version 7.5 supporting 2100 users which now appears we will be forced to upgrade to 8.6 once it is released in October. I have attached the email to the end of this message in case you missed it. This announcement comes at a bad time for us given may other projects we need to complete in the same timeframe. Cost is the least of our worries since we are entitled to the upgrade under maintenance. The ideal situation is deferring the upgrade so that we can ease the pain on our users and staff with changes to multiple applications.



We are in the process of testing our current 7.5 installation and the effects these DST changes. Has anyone done similar tests and have some results they are willing to share? Can the application be tricked by changing the clocks on the server or client, altering the time zone or a combination of both? What impact will this have on the calendar and other clients like PDAs both on March 11 and the traditional April date? I will send our results once they have been compiled.



Regards



Tim Gleason

Sr. Technical Architect

University Information Systems

Harvard University

617.495.5811

***@harvard.edu





-------- Original Message --------
Subject: Important Daylight Saving Time Information for Meeting Maker Users
Date: Wed, 23 Aug 2006 10:24:40 -0400
From: PeopleCube <mailto:***@peoplecube.com> <***@peoplecube.com>



878e78e2.jpg

Dear Meeting Maker User,

Exciting things continue to happen within our Meeting Maker product line. However, it is important for us to communicate some very important information that will affect all of our Meeting Maker customers. In 2005, Congress passed the Energy Policy Act of 2005. A significant provision of the act extends daylight saving time (DST) by 4 weeks beginning in March of 2007. This change will obviously affect all Meeting Maker calendars, as any appointments or meetings scheduled during these four weeks will appear at the incorrect time.

As a result of this new law, PeopleCube will release Meeting Maker 8.6 specifically to address the upcoming change in DST. We have targeted a release date of October 2006 that should provide you with enough time to test and deploy this new release. It will require a full upgrade including both a database and client upgrade. To ensure continuous value of your Meeting Maker solution, we strongly recommend you prepare to upgrade your Meeting Maker installation to comply with this new guideline.

This new release will be made available for free to all Meeting Maker customers with an active maintenance contract via the PeopleCube Online Support Portal at http://connect.peoplecube.com/support/. If you have any questions or would like to inquire about joining our Maintenance Advantage Program, contact us at 1-800-282-7319 or ***@peoplecube.com. Our staff is available to assist you in any way possible.

We will continue to provide updates to these changes through eNews, our quarterly electronic newsletter. If you are not currently subscribed to eNews but would like to start receiving it, simply send an email to ***@peoplecube.com <mailto:***@peoplecube.com?Subject=Subscribe%20to%20eNews> with “Subscribe” in the subject line.

>From all of us here at PeopleCube, we thank you for your continued support.

878e78f2.jpg
878e7911.jpg

878e7930.jpg
411 Waverley Oaks Road
Waltham, MA 02452
North America - 1 [phone] | Europe - 31 (0)20 777 2277
www.peoplecube.com | ***@peoplecube.com
2006 PeopleCube | All rights reserved.


All trademarks, service marks and product names mentioned herein are the property of PeopleCube or their respective owners.

You are receiving this notice because you are currently listed as a PeopleCube customer. If this is in error, please contact us at ***@peoplecube.com.





* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[Stuenkel, MaryBeth]

Tim,



We are wrestling with the same issue. We, too, are currently using version 7.5. Ours is a hub environment, so an upgrade process is no simple task. Especially troublesome is the fact that 8.6 is still only a promise, and with the track record of Meetingmaker releases we are loathe to move to a new version without significant field testing.



Time is critical to a calendaring application and we so haven’t even considered the workarounds you mentioned. Ideally, PeopleCube would provide a patch for all of their versions. This could be the final nail in Meetingmaker’s coffin as a central calendaring service here.



--MaryBeth Stuenkel

University of Michigan



________________________________

From: Meeting Maker Discussion List [mailto:MMXP-***@LISTSERV.EMORY.EDU] On Behalf Of Tim Gleason
Sent: Tuesday, September 12, 2006 8:59 AM
To: MMXP-***@LISTSERV.EMORY.EDU
Subject: Daylight Saving Time effects on 7.5



We were caught by surprise with the recent email sent by PeopleCube regarding the changes to Daylight Savings Time (DST) and the effects on Meeting Maker. We have an installation of version 7.5 supporting 2100 users which now appears we will be forced to upgrade to 8.6 once it is released in October. I have attached the email to the end of this message in case you missed it. This announcement comes at a bad time for us given may other projects we need to complete in the same timeframe. Cost is the least of our worries since we are entitled to the upgrade under maintenance. The ideal situation is deferring the upgrade so that we can ease the pain on our users and staff with changes to multiple applications.



We are in the process of testing our current 7.5 installation and the effects these DST changes. Has anyone done similar tests and have some results they are willing to share? Can the application be tricked by changing the clocks on the server or client, altering the time zone or a combination of both? What impact will this have on the calendar and other clients like PDAs both on March 11 and the traditional April date? I will send our results once they have been compiled.



Regards



Tim Gleason

Sr. Technical Architect

University Information Systems

Harvard University

617.495.5811

***@harvard.edu





-------- Original Message --------
Subject: Important Daylight Saving Time Information for Meeting Maker Users
Date: Wed, 23 Aug 2006 10:24:40 -0400
From: PeopleCube <***@peoplecube.com> <mailto:***@peoplecube.com>





Dear Meeting Maker User,

Exciting things continue to happen within our Meeting Maker product line. However, it is important for us to communicate some very important information that will affect all of our Meeting Maker customers. In 2005, Congress passed the Energy Policy Act of 2005. A significant provision of the act extends daylight saving time (DST) by 4 weeks beginning in March of 2007. This change will obviously affect all Meeting Maker calendars, as any appointments or meetings scheduled during these four weeks will appear at the incorrect time.

As a result of this new law, PeopleCube will release Meeting Maker 8.6 specifically to address the upcoming change in DST. We have targeted a release date of October 2006 that should provide you with enough time to test and deploy this new release. It will require a full upgrade including both a database and client upgrade. To ensure continuous value of your Meeting Maker solution, we strongly recommend you prepare to upgrade your Meeting Maker installation to comply with this new guideline.

This new release will be made available for free to all Meeting Maker customers with an active maintenance contract via the PeopleCube Online Support Portal at http://connect.peoplecube.com/support/. If you have any questions or would like to inquire about joining our Maintenance Advantage Program, contact us at 1-800-282-7319 or ***@peoplecube.com. Our staff is available to assist you in any way possible.

We will continue to provide updates to these changes through eNews, our quarterly electronic newsletter. If you are not currently subscribed to eNews but would like to start receiving it, simply send an email to ***@peoplecube.com <mailto:***@peoplecube.com?Subject=Subscribe%20to%20eNews> with “Subscribe” in the subject line.

From all of us here at PeopleCube, we thank you for your continued support.





411 Waverley Oaks Road
Waltham, MA 02452
North America - 1 [phone] | Europe - 31 (0)20 777 2277
www.peoplecube.com | ***@peoplecube.com
2006 PeopleCube | All rights reserved.


All trademarks, service marks and product names mentioned herein are the property of PeopleCube or their respective owners.

You are receiving this notice because you are currently listed as a PeopleCube customer. If this is in error, please contact us at ***@peoplecube.com.

* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[Erik Froese]

I have to say I'm completely fed up with Meeting Maker as a product.
Is there anything that supports handheld devices as well as Meeting
Maker does without putting all of our eggs in Outlook's basket?

Erik Froese

On 9/12/06, Stuenkel, MaryBeth <***@umich.edu> wrote:
>
>
>
>
> Tim,
>
>
>
> We are wrestling with the same issue. We, too, are currently using version
> 7.5. Ours is a hub environment, so an upgrade process is no simple task.
> Especially troublesome is the fact that 8.6 is still only a promise, and
> with the track record of Meetingmaker releases we are loathe to move to a
> new version without significant field testing.
>
>
>
> Time is critical to a calendaring application and we so haven't even
> considered the workarounds you mentioned. Ideally, PeopleCube would provide
> a patch for all of their versions. This could be the final nail in
> Meetingmaker's coffin as a central calendaring service here.
>
>
>
>
> --MaryBeth Stuenkel
>
> University of Michigan
>
>
>
>
> ________________________________
>
>
> From: Meeting Maker Discussion List [mailto:MMXP-***@LISTSERV.EMORY.EDU] On
> Behalf Of Tim Gleason
> Sent: Tuesday, September 12, 2006 8:59 AM
> To: MMXP-***@LISTSERV.EMORY.EDU
> Subject: Daylight Saving Time effects on 7.5
>
>
>
>
> We were caught by surprise with the recent email sent by PeopleCube
> regarding the changes to Daylight Savings Time (DST) and the effects on
> Meeting Maker. We have an installation of version 7.5 supporting 2100 users
> which now appears we will be forced to upgrade to 8.6 once it is released in
> October. I have attached the email to the end of this message in case you
> missed it. This announcement comes at a bad time for us given may other
> projects we need to complete in the same timeframe. Cost is the least of
> our worries since we are entitled to the upgrade under maintenance. The
> ideal situation is deferring the upgrade so that we can ease the pain on our
> users and staff with changes to multiple applications.
>
>
>
> We are in the process of testing our current 7.5 installation and the
> effects these DST changes. Has anyone done similar tests and have some
> results they are willing to share? Can the application be tricked by
> changing the clocks on the server or client, altering the time zone or a
> combination of both? What impact will this have on the calendar and other
> clients like PDAs both on March 11 and the traditional April date? I will
> send our results once they have been compiled.
>
>
>
> Regards
>
>
>
> Tim Gleason
>
> Sr. Technical Architect
>
> University Information Systems
>
> Harvard University
>
> 617.495.5811
>
> ***@harvard.edu
>
>
>
>
>
> -------- Original Message --------
> Subject: Important Daylight Saving Time Information for Meeting Maker Users
> Date: Wed, 23 Aug 2006 10:24:40 -0400
> From: PeopleCube <***@peoplecube.com>
>
>
>
>
>
> Dear Meeting Maker User,
>
> Exciting things continue to happen within our Meeting Maker product line.
> However, it is important for us to communicate some very important
> information that will affect all of our Meeting Maker customers. In 2005,
> Congress passed the Energy Policy Act of 2005. A significant provision of
> the act extends daylight saving time (DST) by 4 weeks beginning in March of
> 2007. This change will obviously affect all Meeting Maker calendars, as any
> appointments or meetings scheduled during these four weeks will appear at
> the incorrect time.
>
> As a result of this new law, PeopleCube will release Meeting Maker 8.6
> specifically to address the upcoming change in DST. We have targeted a
> release date of October 2006 that should provide you with enough time to
> test and deploy this new release. It will require a full upgrade including
> both a database and client upgrade. To ensure continuous value of your
> Meeting Maker solution, we strongly recommend you prepare to upgrade your
> Meeting Maker installation to comply with this new guideline.
>
> This new release will be made available for free to all Meeting Maker
> customers with an active maintenance contract via the PeopleCube Online
> Support Portal at http://connect.peoplecube.com/support/.
> If you have any questions or would like to inquire about joining our
> Maintenance Advantage Program, contact us at 1-800-282-7319 or
> ***@peoplecube.com. Our staff is available to assist you in any way
> possible.
>
> We will continue to provide updates to these changes through eNews, our
> quarterly electronic newsletter. If you are not currently subscribed to
> eNews but would like to start receiving it, simply send an email to
> ***@peoplecube.com with “Subscribe” in the subject line.
>
> From all of us here at PeopleCube, we thank you for your continued support.
>
>
>
>
>
> 411 Waverley Oaks Road
> Waltham, MA 02452
> North America - 1 [phone] | Europe - 31 (0)20 777 2277
> www.peoplecube.com | ***@peoplecube.com
> 2006 PeopleCube | All rights reserved.
>
>
> All trademarks, service marks and product names mentioned herein are the
> property of PeopleCube or their respective owners.
>
> You are receiving this notice because you are currently listed as a
> PeopleCube customer. If this is in error, please contact us at
> ***@peoplecube.com.
>
>
>
> * MMXP-TALK Web Page:
> http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[Kyle Johnson]

On 9/12/06 at 9:20 AM, Erik Froese wrote:
> I have to say I'm completely fed up with Meeting Maker as a product.
> Is there anything that supports handheld devices as well as Meeting
> Maker does without putting all of our eggs in Outlook's basket?

Duke recently went to Oracle Calendar centrally. We'll be migrating our
Meeting Maker installation to that sometime this year. It appears to
have very good mobile support and doesn't require you to swallow the
Microsoft koolaid to use it. '-)

/kyle
---
Kyle Johnson : Director, Information Technology Services
Duke University Student Affairs
***@duke.edu : http://www.studentaffairs.duke.edu
jabber- ***@jabber.duke.edu : aim- dukekej
-----------------------------------------------------------------------
Do you have change for a paradigm?


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[Chris Colebank]

Kyle,

You say you will be migrating to Oracle Calendar. Have you found a
tool to migrate all the user calendars from Meeting Maker for import
into another application? Or will you be 'starting over' in the new
application, as in recreating all the users in the new application
without their schedules.

thanks, Chris

Kyle Johnson wrote:
> On 9/12/06 at 9:20 AM, Erik Froese wrote:
>
>> I have to say I'm completely fed up with Meeting Maker as a product.
>> Is there anything that supports handheld devices as well as Meeting
>> Maker does without putting all of our eggs in Outlook's basket?
>>
>
> Duke recently went to Oracle Calendar centrally. We'll be migrating our
> Meeting Maker installation to that sometime this year. It appears to
> have very good mobile support and doesn't require you to swallow the
> Microsoft koolaid to use it. '-)
>
> /kyle
> ---
> Kyle Johnson : Director, Information Technology Services
> Duke University Student Affairs
> ***@duke.edu : http://www.studentaffairs.duke.edu
> jabber- ***@jabber.duke.edu : aim- dukekej
> -----------------------------------------------------------------------
> Do you have change for a paradigm?
>
>
> * MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML
>


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[Bob DeSilets]

I've always found that the best way to migrate between any calendar
(of any flavor) is a handheld acting as an intermediary.

Bob

--------------------------------
Bob DeSilets
Sr. IT Support Specialist
***@isc.upenn.edu
215-898-0067



On Sep 12, 2006, at 10:44 AM, Chris Colebank wrote:

> Kyle,
>
> You say you will be migrating to Oracle Calendar. Have you found
> a tool to migrate all the user calendars from Meeting Maker for
> import into another application? Or will you be 'starting over' in
> the new application, as in recreating all the users in the new
> application without their schedules.
>
> thanks, Chris
>
> Kyle Johnson wrote:
>> On 9/12/06 at 9:20 AM, Erik Froese wrote:
>>
>>> I have to say I'm completely fed up with Meeting Maker as a product.
>>> Is there anything that supports handheld devices as well as Meeting
>>> Maker does without putting all of our eggs in Outlook's basket?
>>>
>>
>> Duke recently went to Oracle Calendar centrally. We'll be
>> migrating our
>> Meeting Maker installation to that sometime this year. It appears to
>> have very good mobile support and doesn't require you to swallow the
>> Microsoft koolaid to use it. '-)
>>
>> /kyle
>> ---
>> Kyle Johnson : Director, Information Technology Services
>> Duke University Student Affairs
>> ***@duke.edu : http://www.studentaffairs.duke.edu
>> jabber- ***@jabber.duke.edu : aim- dukekej
>> ---------------------------------------------------------------------
>> --
>> Do you have change for a paradigm?
>>
>>
>> * MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-
>> TALK.HTML
>>
>
>
> * MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-
> TALK.HTML



* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[Kyle Johnson]

On 9/12/06 at 10:44 AM, Chris Colebank wrote:
> You say you will be migrating to Oracle Calendar. Have you found a tool to
> migrate all the user calendars from Meeting Maker for import into another
> application? Or will you be 'starting over' in the new application, as in
> recreating all the users in the new application without their schedules.

It is my understanding the Oracle provides such a tool. Another
department is doing the MM to Oracle conversion before us, so hopefully
they'll get all the kinks worked out of the system before we do the
migration.

/kyle
---
Kyle Johnson : Director, Information Technology Services
Duke University Student Affairs
***@duke.edu : http://www.studentaffairs.duke.edu
jabber- ***@jabber.duke.edu : aim- dukekej
-----------------------------------------------------------------------
If it's in stock, we've got it.


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[Erik Froese]

Please keep us posted on your progress!

On 9/12/06, Kyle Johnson <***@duke.edu> wrote:
> On 9/12/06 at 10:44 AM, Chris Colebank wrote:
> > You say you will be migrating to Oracle Calendar. Have you found a tool to
> > migrate all the user calendars from Meeting Maker for import into another
> > application? Or will you be 'starting over' in the new application, as in
> > recreating all the users in the new application without their schedules.
>
> It is my understanding the Oracle provides such a tool. Another
> department is doing the MM to Oracle conversion before us, so hopefully
> they'll get all the kinks worked out of the system before we do the
> migration.
>
> /kyle
> ---
> Kyle Johnson : Director, Information Technology Services
> Duke University Student Affairs
> ***@duke.edu : http://www.studentaffairs.duke.edu
> jabber- ***@jabber.duke.edu : aim- dukekej
> -----------------------------------------------------------------------
> If it's in stock, we've got it.
>
>
> * MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML
>


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[Mike Wiseman]

Have a look at open exchange at http://www.open-xchange.com/EN/

We are running 8.5.3 of Mm and are wholly dissatisfied with
Meetingmaker as a proucut.

regards

Mike Wiseman
Flinders University


On 12/09/2006, at 10:50 PM, Erik Froese wrote:

> I have to say I'm completely fed up with Meeting Maker as a product.
> Is there anything that supports handheld devices as well as Meeting
> Maker does without putting all of our eggs in Outlook's basket?
>
> Erik Froese
>
> On 9/12/06, Stuenkel, MaryBeth <***@umich.edu> wrote:
>>
>>
>>
>>
>> Tim,
>>
>>
>>
>> We are wrestling with the same issue. We, too, are currently
>> using version
>> 7.5. Ours is a hub environment, so an upgrade process is no
>> simple task.
>> Especially troublesome is the fact that 8.6 is still only a
>> promise, and
>> with the track record of Meetingmaker releases we are loathe to
>> move to a
>> new version without significant field testing.
>>
>>
>>
>> Time is critical to a calendaring application and we so haven't even
>> considered the workarounds you mentioned. Ideally, PeopleCube
>> would provide
>> a patch for all of their versions. This could be the final nail in
>> Meetingmaker's coffin as a central calendaring service here.
>>
>>
>>
>>
>> --MaryBeth Stuenkel
>>
>> University of Michigan
>>
>>
>>
>>
>> ________________________________
>>
>>
>> From: Meeting Maker Discussion List [mailto:MMXP-
>> ***@LISTSERV.EMORY.EDU] On
>> Behalf Of Tim Gleason
>> Sent: Tuesday, September 12, 2006 8:59 AM
>> To: MMXP-***@LISTSERV.EMORY.EDU
>> Subject: Daylight Saving Time effects on 7.5
>>
>>
>>
>>
>> We were caught by surprise with the recent email sent by PeopleCube
>> regarding the changes to Daylight Savings Time (DST) and the
>> effects on
>> Meeting Maker. We have an installation of version 7.5 supporting
>> 2100 users
>> which now appears we will be forced to upgrade to 8.6 once it is
>> released in
>> October. I have attached the email to the end of this message in
>> case you
>> missed it. This announcement comes at a bad time for us given may
>> other
>> projects we need to complete in the same timeframe. Cost is the
>> least of
>> our worries since we are entitled to the upgrade under
>> maintenance. The
>> ideal situation is deferring the upgrade so that we can ease the
>> pain on our
>> users and staff with changes to multiple applications.
>>
>>
>>
>> We are in the process of testing our current 7.5 installation and the
>> effects these DST changes. Has anyone done similar tests and have
>> some
>> results they are willing to share? Can the application be tricked by
>> changing the clocks on the server or client, altering the time
>> zone or a
>> combination of both? What impact will this have on the calendar
>> and other
>> clients like PDAs both on March 11 and the traditional April
>> date? I will
>> send our results once they have been compiled.
>>
>>
>>
>> Regards
>>
>>
>>
>> Tim Gleason
>>
>> Sr. Technical Architect
>>
>> University Information Systems
>>
>> Harvard University
>>
>> 617.495.5811
>>
>> ***@harvard.edu
>>
>>
>>
>>
>>
>> -------- Original Message --------
>> Subject: Important Daylight Saving Time Information for Meeting
>> Maker Users
>> Date: Wed, 23 Aug 2006 10:24:40 -0400
>> From: PeopleCube <***@peoplecube.com>
>>
>>
>>
>>
>>
>> Dear Meeting Maker User,
>>
>> Exciting things continue to happen within our Meeting Maker
>> product line.
>> However, it is important for us to communicate some very important
>> information that will affect all of our Meeting Maker customers.
>> In 2005,
>> Congress passed the Energy Policy Act of 2005. A significant
>> provision of
>> the act extends daylight saving time (DST) by 4 weeks beginning in
>> March of
>> 2007. This change will obviously affect all Meeting Maker
>> calendars, as any
>> appointments or meetings scheduled during these four weeks will
>> appear at
>> the incorrect time.
>>
>> As a result of this new law, PeopleCube will release Meeting
>> Maker 8.6
>> specifically to address the upcoming change in DST. We have
>> targeted a
>> release date of October 2006 that should provide you with enough
>> time to
>> test and deploy this new release. It will require a full upgrade
>> including
>> both a database and client upgrade. To ensure continuous value of
>> your
>> Meeting Maker solution, we strongly recommend you prepare to
>> upgrade your
>> Meeting Maker installation to comply with this new guideline.
>>
>> This new release will be made available for free to all Meeting
>> Maker
>> customers with an active maintenance contract via the PeopleCube
>> Online
>> Support Portal at http://connect.peoplecube.com/support/.
>> If you have any questions or would like to inquire about joining our
>> Maintenance Advantage Program, contact us at 1-800-282-7319 or
>> ***@peoplecube.com. Our staff is available to assist you in any way
>> possible.
>>
>> We will continue to provide updates to these changes through
>> eNews, our
>> quarterly electronic newsletter. If you are not currently
>> subscribed to
>> eNews but would like to start receiving it, simply send an email to
>> ***@peoplecube.com with “Subscribe” in the
>> subject line.
>>
>> From all of us here at PeopleCube, we thank you for your
>> continued support.
>>
>>
>>
>>
>>
>> 411 Waverley Oaks Road
>> Waltham, MA 02452
>> North America - 1 [phone] | Europe - 31 (0)20 777 2277
>> www.peoplecube.com | ***@peoplecube.com
>> 2006 PeopleCube | All rights reserved.
>>
>>
>> All trademarks, service marks and product names mentioned herein
>> are the
>> property of PeopleCube or their respective owners.
>>
>> You are receiving this notice because you are currently listed as a
>> PeopleCube customer. If this is in error, please contact us at
>> ***@peoplecube.com.
>>
>>
>>
>> * MMXP-TALK Web Page:
>> http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[Anderson, Kelly]

Some additional considerations, as I've been doing some research:

The Web Client, which was a Java applet in v7.5.3 (which we run) is now an Apache Tomcat based Java Servlet, and we are now required to run an Apache web server to support web clients (currently we "borrow" the space from our web group, which does not support Tomcat at this time). More hardware and support will cost money.

And I've heard that the release date is now the end of November, not the end of October. How are we supposed to make time for testing if this slips with the holidays approaching, the end of term, production service freezes, not to mention our current projects, before March?


--Kelly

University of Michigan




________________________________

From: Meeting Maker Discussion List [mailto:MMXP-***@LISTSERV.EMORY.EDU] On Behalf Of Tim Gleason
Sent: Tuesday, September 12, 2006 8:59 AM
To: MMXP-***@LISTSERV.EMORY.EDU
Subject: [MMXP-TALK] Daylight Saving Time effects on 7.5



We were caught by surprise with the recent email sent by PeopleCube regarding the changes to Daylight Savings Time (DST) and the effects on Meeting Maker. We have an installation of version 7.5 supporting 2100 users which now appears we will be forced to upgrade to 8.6 once it is released in October. I have attached the email to the end of this message in case you missed it. This announcement comes at a bad time for us given may other projects we need to complete in the same timeframe. Cost is the least of our worries since we are entitled to the upgrade under maintenance. The ideal situation is deferring the upgrade so that we can ease the pain on our users and staff with changes to multiple applications.



We are in the process of testing our current 7.5 installation and the effects these DST changes. Has anyone done similar tests and have some results they are willing to share? Can the application be tricked by changing the clocks on the server or client, altering the time zone or a combination of both? What impact will this have on the calendar and other clients like PDAs both on March 11 and the traditional April date? I will send our results once they have been compiled.



Regards



Tim Gleason

Sr. Technical Architect

University Information Systems

Harvard University

617.495.5811

***@harvard.edu





-------- Original Message --------
Subject: Important Daylight Saving Time Information for Meeting Maker Users
Date: Wed, 23 Aug 2006 10:24:40 -0400
From: PeopleCube <***@peoplecube.com> <mailto:***@peoplecube.com>





Dear Meeting Maker User,

Exciting things continue to happen within our Meeting Maker product line. However, it is important for us to communicate some very important information that will affect all of our Meeting Maker customers. In 2005, Congress passed the Energy Policy Act of 2005. A significant provision of the act extends daylight saving time (DST) by 4 weeks beginning in March of 2007. This change will obviously affect all Meeting Maker calendars, as any appointments or meetings scheduled during these four weeks will appear at the incorrect time.

As a result of this new law, PeopleCube will release Meeting Maker 8.6 specifically to address the upcoming change in DST. We have targeted a release date of October 2006 that should provide you with enough time to test and deploy this new release. It will require a full upgrade including both a database and client upgrade. To ensure continuous value of your Meeting Maker solution, we strongly recommend you prepare to upgrade your Meeting Maker installation to comply with this new guideline.

This new release will be made available for free to all Meeting Maker customers with an active maintenance contract via the PeopleCube Online Support Portal at http://connect.peoplecube.com/support/. If you have any questions or would like to inquire about joining our Maintenance Advantage Program, contact us at 1-800-282-7319 or ***@peoplecube.com. Our staff is available to assist you in any way possible.

We will continue to provide updates to these changes through eNews, our quarterly electronic newsletter. If you are not currently subscribed to eNews but would like to start receiving it, simply send an email to ***@peoplecube.com <mailto:***@peoplecube.com?Subject=Subscribe%20to%20eNews> with “Subscribe” in the subject line.

From all of us here at PeopleCube, we thank you for your continued support.





411 Waverley Oaks Road
Waltham, MA 02452
North America - 1 [phone] | Europe - 31 (0)20 777 2277
www.peoplecube.com | ***@peoplecube.com
2006 PeopleCube | All rights reserved.


All trademarks, service marks and product names mentioned herein are the property of PeopleCube or their respective owners.

You are receiving this notice because you are currently listed as a PeopleCube customer. If this is in error, please contact us at ***@peoplecube.com.



* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[Erik Froese]

The Outlook Connector, HTML Calendar (which replaces the applet-based
calendar), and Intellisync servers all run in tomcat as well.

Erik


On 9/12/06, Anderson, Kelly <***@umich.edu> wrote:
>
>
> Some additional considerations, as I've been doing some research:
>
> The Web Client, which was a Java applet in v7.5.3 (which we run) is now an
> Apache Tomcat based Java Servlet, and we are now required to run an Apache
> web server to support web clients (currently we "borrow" the space from our
> web group, which does not support Tomcat at this time). More hardware and
> support will cost money.
>
> And I've heard that the release date is now the end of November, not the end
> of October. How are we supposed to make time for testing if this slips with
> the holidays approaching, the end of term, production service freezes, not
> to mention our current projects, before March?
>
>
> --Kelly
>
> University of Michigan
>
>
>
> ________________________________
>
> From: Meeting Maker Discussion List [mailto:MMXP-***@LISTSERV.EMORY.EDU] On
> Behalf Of Tim Gleason
> Sent: Tuesday, September 12, 2006 8:59 AM
> To: MMXP-***@LISTSERV.EMORY.EDU
> Subject: [MMXP-TALK] Daylight Saving Time effects on 7.5
>
>
>
>
>
> We were caught by surprise with the recent email sent by PeopleCube
> regarding the changes to Daylight Savings Time (DST) and the effects on
> Meeting Maker. We have an installation of version 7.5 supporting 2100 users
> which now appears we will be forced to upgrade to 8.6 once it is released in
> October. I have attached the email to the end of this message in case you
> missed it. This announcement comes at a bad time for us given may other
> projects we need to complete in the same timeframe. Cost is the least of
> our worries since we are entitled to the upgrade under maintenance. The
> ideal situation is deferring the upgrade so that we can ease the pain on our
> users and staff with changes to multiple applications.
>
>
>
> We are in the process of testing our current 7.5 installation and the
> effects these DST changes. Has anyone done similar tests and have some
> results they are willing to share? Can the application be tricked by
> changing the clocks on the server or client, altering the time zone or a
> combination of both? What impact will this have on the calendar and other
> clients like PDAs both on March 11 and the traditional April date? I will
> send our results once they have been compiled.
>
>
>
> Regards
>
>
>
> Tim Gleason
>
> Sr. Technical Architect
>
> University Information Systems
>
> Harvard University
>
> 617.495.5811
>
> ***@harvard.edu
>
>
>
>
>
> -------- Original Message --------
> Subject: Important Daylight Saving Time Information for Meeting Maker Users
> Date: Wed, 23 Aug 2006 10:24:40 -0400
> From: PeopleCube <***@peoplecube.com>
>
>
>
>
>
> Dear Meeting Maker User,
>
> Exciting things continue to happen within our Meeting Maker product line.
> However, it is important for us to communicate some very important
> information that will affect all of our Meeting Maker customers. In 2005,
> Congress passed the Energy Policy Act of 2005. A significant provision of
> the act extends daylight saving time (DST) by 4 weeks beginning in March of
> 2007. This change will obviously affect all Meeting Maker calendars, as any
> appointments or meetings scheduled during these four weeks will appear at
> the incorrect time.
>
> As a result of this new law, PeopleCube will release Meeting Maker 8.6
> specifically to address the upcoming change in DST. We have targeted a
> release date of October 2006 that should provide you with enough time to
> test and deploy this new release. It will require a full upgrade including
> both a database and client upgrade. To ensure continuous value of your
> Meeting Maker solution, we strongly recommend you prepare to upgrade your
> Meeting Maker installation to comply with this new guideline.
>
> This new release will be made available for free to all Meeting Maker
> customers with an active maintenance contract via the PeopleCube Online
> Support Portal at http://connect.peoplecube.com/support/.
> If you have any questions or would like to inquire about joining our
> Maintenance Advantage Program, contact us at 1-800-282-7319 or
> ***@peoplecube.com. Our staff is available to assist you in any way
> possible.
>
> We will continue to provide updates to these changes through eNews, our
> quarterly electronic newsletter. If you are not currently subscribed to
> eNews but would like to start receiving it, simply send an email to
> ***@peoplecube.com with “Subscribe” in the subject line.
>
> From all of us here at PeopleCube, we thank you for your continued support.
>
>
>
>
>
> 411 Waverley Oaks Road
> Waltham, MA 02452
> North America - 1 [phone] | Europe - 31 (0)20 777 2277
> www.peoplecube.com | ***@peoplecube.com
> 2006 PeopleCube | All rights reserved.
>
>
> All trademarks, service marks and product names mentioned herein are the
> property of PeopleCube or their respective owners.
>
> You are receiving this notice because you are currently listed as a
> PeopleCube customer. If this is in error, please contact us at
> ***@peoplecube.com.
>
>
>
> * MMXP-TALK Web Page:
> http://WWW

[Jack C Newton]

This issue will really only effect you if you cross time zones. So if all
your users do not schedule outside of the same time zone, then you wilol not
see an issue because your OS system clocks will change as they should for
your local time zone and you will perceive no issues.

Viewing or scheduling across time zones however will show one hour off until
the normal previous daylight savings time dates pass.

-Jack Newton


From: Tim Gleason <***@HARVARD.EDU>
Date: 2006/09/12 Tue AM 07:58:50 CDT
To: MMXP-***@LISTSERV.EMORY.EDU
Subject: Daylight Saving Time effects on 7.5

<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-
com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word"
xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://
www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=Content-Type content="text/html; charset=utf-8">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PostalCode"/
>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="State"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="City"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="PlaceType"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="PlaceName"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="place"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="Street"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="address"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:Arial;
color:windowtext;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>

<body lang=EN-US link=blue vlink=purple>

<div class=Section1>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>We were caught by surprise with the recent email sent by
PeopleCube regarding the changes to Daylight Savings Time (DST) and the
effects
on Meeting Maker.  We have an installation of version 7.5 supporting 2100
users
which now appears we will be forced to upgrade to 8.6 once it is released in
October.  I have attached the email to the end of this message in case you
missed it.  This announcement comes at a bad time for us given may other
projects we need to complete in the same timeframe.  Cost is the least of our
worries since we are entitled to the upgrade under maintenance.  The ideal
situation is deferring the upgrade so that we can ease the pain on our users
and staff with changes to multiple applications.<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>We are in the process of testing our current 7.5
installation
and the effects these DST changes.  Has anyone done similar tests and have
some
results they are willing to share?  Can the application be tricked by
changing
the clocks on the server or client, altering the time zone or a combination
of
both?  What impact will this have on the calendar and other clients like PDAs
both on March 11 and the traditional April date?  I will send our results
once
they have been compiled.<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Regards<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>

<p class=MsoNormal><strong><b><font size=1 face=Arial><span style='font-size:
7.5pt;font-family:Arial'>Tim Gleason</span></font></b></strong><o:p></o:p></
p>

<p class=MsoNormal><font size=1 face=Arial><span style='font-size:7.5pt;
font-family:Arial'>Sr. Technical Architect</span></font><o:p></o:p></p>

<p class=MsoNormal><font size=1 face=Arial><span style='font-size:7.5pt;
font-family:Arial'>University Information Systems</span></font><o:p></o:p></
p>

<p class=MsoNormal><st1:place w:st="on"><st1:PlaceName w:st="on"><font size=1
face=Arial><span style='font-size:7.5pt;font-family:Arial'>Harvard</span></
font></st1:PlaceName><font
size=1 face=Arial><span style='font-size:7.5pt;font-family:Arial'>
<st1:PlaceType
w:st="on">University</st1:PlaceType></span></font></st1:place><o:p></o:p></
p>

<p class=MsoNormal><font size=1 face=Arial><span style='font-size:7.5pt;
font-family:Arial'>617.495.5811</span></font><o:p></o:p></p>

<p class=MsoNormal><font size=1 face=Arial><span style='font-size:7.5pt;
font-family:Arial'><a
href="mailto:***@harvard.edu">***@harvard.edu</a></span></
font><o:p></o:p></p>

<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-
size:
12.0pt'><o:p> </o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-
size:
12.0pt'><o:p> </o:p></span></font></p>

<p class=MsoNormal style='margin-bottom:12.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>-------- Original
Message
-------- <br>
Subject: Important Daylight Saving Time Information for Meeting Maker Users
<br>
Date: Wed, 23 Aug 2006 10:24:40 -0400 <br>
From: PeopleCube <a href="mailto:***@peoplecube.com"
title="mailto:***@peoplecube.com"><***@peoplecube.com></a>
<br>
<br>
<br>
<br>
<img border=0 width=576 height=216 id="_x0000_i1025"
src="HttpNimletDriver?
nimlet=DownloadAttachmentNimlet&fileName=image001.jpg&folderName=INBOX&messag
eID=50&partIndex=4&disposition=inline" alt=878e78e2.jpg></span></font><font
size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'> <br>
<br>
Dear Meeting Maker User,<br>
<br>
Exciting things continue to happen within our Meeting Maker product line.
However, it is important for us to communicate some very important
information
that will affect all of our Meeting Maker customers. In 2005, Congress passed
the Energy Policy Act of 2005. A significant provision of the act extends
daylight saving time (DST) by 4 weeks beginning in March of 2007. This change
will obviously affect all Meeting Maker calendars, as any appointments or
meetings scheduled during these four weeks will appear at the incorrect time.
<br>
<br>
As a result of this new law, PeopleCube will release Meeting Maker 8.6
specifically to address the upcoming change in DST. We have targeted a
release
date of October 2006 that should provide you with enough time to test and
deploy this new release. It will require a full upgrade including both a
database
and client upgrade. To ensure continuous value of your Meeting Maker
solution,
we strongly recommend you prepare to upgrade your Meeting Maker installation
to
comply with this new guideline. <br>
<br>
This new release will be made available for free to all Meeting Maker
customers
with an active maintenance contract via the PeopleCube Online Support Portal
at
<a href="http://connect.peoplecube.com/support/"
title="http://connect.peoplecube.com/support/">http://connect.peoplecube.com/
support/</a>.
If you have any questions or would like to inquire about joining our
Maintenance Advantage Program, contact us at 1-800-282-7319 or <a
href="mailto:***@peoplecube.com"
title="mailto:***@peoplecube.com">***@peoplecube.com</a>.
Our staff is available to assist you in any way possible. <br>
<br>
We will continue to provide updates to these changes through eNews, our
quarterly electronic newsletter. If you are not currently subscribed to eNews
but would like to start receiving it, simply send an email to <a
href="mailto:***@peoplecube.com?Subject=Subscribe%20to%20eNews"
title="mailto:***@peoplecube.com?Subject=Subscribe to
eNews">***@peoplecube.com</a>
with “Subscribeâ€? in the subject line.<br>
<br>
From all of us here at PeopleCube, we thank you for your continued
support.<br>
<br>
<img border=0 width=576 height=41 id="_x0000_i1026"
src="HttpNimletDriver?
nimlet=DownloadAttachmentNimlet&fileName=image002.jpg&folderName=INBOX&messag
eID=50&partIndex=3&disposition=inline" alt=878e78f2.jpg><br>
<img border=0 width=600 height=5 id="_x0000_i1027"
src="HttpNimletDriver?
nimlet=DownloadAttachmentNimlet&fileName=image003.jpg&folderName=INBOX&messag
eID=50&partIndex=2&disposition=inline" alt=878e7911.jpg> <o:p></o:p></span></
font></p>

<p class=MsoNormal align=center style='text-align:center'><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'><img border=0
width=98 height=43 id="_x0000_i1028" src="HttpNimletDriver?
nimlet=DownloadAttachmentNimlet&fileName=image004.jpg&folderName=INBOX&messag
eID=50&partIndex=1&disposition=inline"
alt=878e7930.jpg><br>
411 <st1:City w:st="on"><st1:place w:st="on">Waverley</st1:place></st1:City>
<st1:Street
w:st="on"><st1:address w:st="on">Oaks Road</st1:address></st1:Street><br>
<st1:place w:st="on"><st1:City w:st="on">Waltham</st1:City>, <st1:State
w:st="on">MA</st1:State>
<st1:PostalCode w:st="on">02452</st1:PostalCode></st1:place><br>
North America - 1 [phone] | <st1:place w:st="on">Europe</st1:place> -
31
(0)20 777 2277<br>
<a href="http://www.peoplecube.com" title="http://
www.peoplecube.com">www.peoplecube.com</a>
| <a href="mailto:***@peoplecube.com"
title="mailto:***@peoplecube.com">***@peoplecube.com</a><br>
2006 PeopleCube | All rights reserved.<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><br>
All trademarks, service marks and product names mentioned herein are the
property of PeopleCube or their respective owners. <br>
<br>
You are receiving this notice because you are currently listed as a
PeopleCube
customer. If this is in error, please contact us at <a
href="mailto:***@peoplecube.com"
title="mailto:***@peoplecube.com">***@peoplecube.com</a>.
<br>
<br>
</span></font><o:p></o:p></p>

</div>

</body>

</html>
<p>
* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[Jay Hauben]

Hi,

Does anyone know if the following also applies to server version
7.1g(74)? Our clients are version 7.3.0(36).

Thanks.

Jay

On Tue, 12 Sep 2006, Jack C Newton wrote:

> This issue will really only effect you if you cross time zones. So
> if all your users do not schedule outside of the same time zone,
> then you will not see an issue because your OS system clocks will
> change as they should for your local time zone and you will perceive
> no issues.
>
> Viewing or scheduling across time zones however will show one hour
> off until the normal previous daylight savings time dates pass.
>
> -Jack Newton
>


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[Ian Eiloart]

--On 12 September 2006 08:35:25 -0500 Jack C Newton
<***@VERIZON.NET> wrote:

> This issue will really only effect you if you cross time zones. So if all
> your users do not schedule outside of the same time zone, then you wilol
> not see an issue because your OS system clocks will change as they
> should for your local time zone and you will perceive no issues.

That's unlikely for a University. Here, we're all in the UK timezone, but I
still schedule across timezones for travel abroad, and for reminders of
events abroad.

For example, just yesterday, I switched my Display Time Zone to US Pacific
in order to add the schedule for Apple's media event. Last week, I took a
holiday in France, and used the Display Time Zone feature to schedule my
train and ferry journeys. Of course, the latter isn't going to be affected
by this update.

> Viewing or scheduling across time zones however will show one hour off
> until the normal previous daylight savings time dates pass.
>
> -Jack Newton
>
>
> From: Tim Gleason <***@HARVARD.EDU>
> Date: 2006/09/12 Tue AM 07:58:50 CDT
> To: MMXP-***@LISTSERV.EMORY.EDU
> Subject: Daylight Saving Time effects on 7.5
>
> <html xmlns:v="urn:schemas-microsoft-com:vml"
> xmlns:o="urn:schemas-microsoft- com:office:office"
> xmlns:w="urn:schemas-microsoft-com:office:word"
> xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://
> www.w3.org/TR/REC-html40">
>
> <head>
> <meta http-equiv=Content-Type content="text/html; charset=utf-8">
> <meta name=Generator content="Microsoft Word 11 (filtered medium)">
> <!--[if !mso]>
> <style>
> v\:* {behavior:url(#default#VML);}
> o\:* {behavior:url(#default#VML);}
> w\:* {behavior:url(#default#VML);}
> .shape {behavior:url(#default#VML);}
> </style>
> <![endif]--><o:SmartTagType
> namespaceuri="urn:schemas-microsoft-com:office:smarttags"
> name="PostalCode"/
>>
> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
> name="State"/>
> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
> name="City"/>
> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
> name="PlaceType"/>
> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
> name="PlaceName"/>
> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
> name="place"/>
> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
> name="Street"/>
> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
> name="address"/>
> <!--[if !mso]>
> <style>
> st1\:*{behavior:url(#default#ieooui) }
> </style>
> <![endif]-->
> <style>
> <!--
> /* Style Definitions */
> p.MsoNormal, li.MsoNormal, div.MsoNormal
> {margin:0in;
> margin-bottom:.0001pt;
> font-size:12.0pt;
> font-family:"Times New Roman";}
> a:link, span.MsoHyperlink
> {color:blue;
> text-decoration:underline;}
> a:visited, span.MsoHyperlinkFollowed
> {color:purple;
> text-decoration:underline;}
> span.EmailStyle17
> {mso-style-type:personal-compose;
> font-family:Arial;
> color:windowtext;}
> @page Section1
> {size:8.5in 11.0in;
> margin:1.0in 1.25in 1.0in 1.25in;}
> div.Section1
> {page:Section1;}
> -->
> </style>
> <!--[if gte mso 9]><xml>
> <o:shapedefaults v:ext="edit" spidmax="1026" />
> </xml><![endif]--><!--[if gte mso 9]><xml>
> <o:shapelayout v:ext="edit">
> <o:idmap v:ext="edit" data="1" />
> </o:shapelayout></xml><![endif]-->
> </head>
>
> <body lang=EN-US link=blue vlink=purple>
>
> <div class=Section1>
>
> <p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
> font-family:Arial'>We were caught by surprise with the recent email sent
> by PeopleCube regarding the changes to Daylight Savings Time (DST) and
> the effects
> on Meeting Maker.  We have an installation of version 7.5 supporting
> 2100 users
> which now appears we will be forced to upgrade to 8.6 once it is released
> in October.  I have attached the email to the end of this message in
> case you missed it.  This announcement comes at a bad time for us given
> may other projects we need to complete in the same timeframe.  Cost is
> the least of our worries since we are entitled to the upgrade under
> maintenance.  The ideal situation is deferring the upgrade so that we
> can ease the pain on our users and staff with changes to multiple
> applications.<o:p></o:p></span></font></p>
>
> <p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
> font-family:Arial'><o:p> </o:p></span></font></p>
>
> <p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
> font-family:Arial'>We are in the process of testing our current 7.5
> installation
> and the effects these DST changes.  Has anyone done similar tests and
> have some
> results they are willing to share?  Can the application be tricked by
> changing
> the clocks on the server or client, altering the time zone or a
> combination of
> both?  What impact will this have on the calendar and other clients like
> PDAs both on March 11 and the traditional April date?  I will send our
> results once
> they have been compiled.<o:p></o:p></span></font></p>
>
> <p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
> font-family:Arial'><o:p> </o:p></span></font></p>
>
> <p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
> font-family:Arial'>Regards<o:p></o:p></span></font></p>
>
> <p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
> font-family:Arial'><o:p> </o:p></span></font></p>
>
> <p class=MsoNormal><strong><b><font size=1 face=Arial><span
> style='font-size: 7.5pt;font-family:Arial'>Tim
> Gleason</span></font></b></strong><o:p></o:p></ p>
>
> <p class=MsoNormal><font size=1 face=Arial><span style='font-size:7.5pt;
> font-family:Arial'>Sr. Technical Architect</span></font><o:p></o:p></p>
>
> <p class=MsoNormal><font size=1 face=Arial><span style='font-size:7.5pt;
> font-family:Arial'>University Information
> Systems</span></font><o:p></o:p></ p>
>
> <p class=MsoNormal><st1:place w:st="on"><st1:PlaceName w:st="on"><font
> size=1 face=Arial><span
> style='font-size:7.5pt;font-family:Arial'>Harvard</span></
> font></st1:PlaceName><font
> size=1 face=Arial><span style='font-size:7.5pt;font-family:Arial'>
> <st1:PlaceType
> w:st="on">University</st1:PlaceType></span></font></st1:place><o:p></o:p
> ></ p>
>
> <p class=MsoNormal><font size=1 face=Arial><span style='font-size:7.5pt;
> font-family:Arial'>617.495.5811</span></font><o:p></o:p></p>
>
> <p class=MsoNormal><font size=1 face=Arial><span style='font-size:7.5pt;
> font-family:Arial'><a
> href="mailto:***@harvard.edu">***@harvard.edu</a></span></
> font><o:p></o:p></p>
>
> <p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-
> size:
> 12.0pt'><o:p> </o:p></span></font></p>
>
> <p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-
> size:
> 12.0pt'><o:p> </o:p></span></font></p>
>
> <p class=MsoNormal style='margin-bottom:12.0pt'><font size=3
> face="Times New Roman"><span style='font-size:12.0pt'>-------- Original
> Message
> -------- <br>
> Subject: Important Daylight Saving Time Information for Meeting Maker
> Users <br>
> Date: Wed, 23 Aug 2006 10:24:40 -0400 <br>
> From: PeopleCube <a href="mailto:***@peoplecube.com"
> title="mailto:***@peoplecube.com"><***@peoplecube.com></a>
> <br>
> <br>
> <br>
> <br>
> <img border=0 width=576 height=216 id="_x0000_i1025"
> src="HttpNimletDriver?
> nimlet=DownloadAttachmentNimlet&fileName=image001.jpg&folderName=INBOX&me
> ssag eID=50&partIndex=4&disposition=inline"
> alt=878e78e2.jpg></span></font><font size=2 face=Arial><span
> style='font-size:10.0pt;font-family:Arial'> <br> <br>
> Dear Meeting Maker User,<br>
> <br>
> Exciting things continue to happen within our Meeting Maker product line.
> However, it is important for us to communicate some very important
> information
> that will affect all of our Meeting Maker customers. In 2005, Congress
> passed the Energy Policy Act of 2005. A significant provision of the act
> extends daylight saving time (DST) by 4 weeks beginning in March of 2007.
> This change will obviously affect all Meeting Maker calendars, as any
> appointments or meetings scheduled during these four weeks will appear at
> the incorrect time. <br>
> <br>
> As a result of this new law, PeopleCube will release Meeting Maker 8.6
> specifically to address the upcoming change in DST. We have targeted a
> release
> date of October 2006 that should provide you with enough time to test and
> deploy this new release. It will require a full upgrade including both a
> database
> and client upgrade. To ensure continuous value of your Meeting Maker
> solution,
> we strongly recommend you prepare to upgrade your Meeting Maker
> installation to
> comply with this new guideline. <br>
> <br>
> This new release will be made available for free to all Meeting Maker
> customers
> with an active maintenance contract via the PeopleCube Online Support
> Portal at
> <a href="http://connect.peoplecube.com/support/"
> title="http://connect.peoplecube.com/support/">http://connect.peoplecube.
> com/ support/</a>.
> If you have any questions or would like to inquire about joining our
> Maintenance Advantage Program, contact us at 1-800-282-7319 or <a
> href="mailto:***@peoplecube.com"
> title="mailto:***@peoplecube.com">***@peoplecube.com</a>.
> Our staff is available to assist you in any way possible. <br>
> <br>
> We will continue to provide updates to these changes through eNews, our
> quarterly electronic newsletter. If you are not currently subscribed to
> eNews but would like to start receiving it, simply send an email to <a
> href="mailto:***@peoplecube.com?Subject=Subscribe%20to%20eNews"
> title="mailto:***@peoplecube.com?Subject=Subscribe to
> eNews">***@peoplecube.com</a>
> with “Subscribe� in the subject line.<br>
> <br>
>> From all of us here at PeopleCube, we thank you for your continued
> support.<br>
> <br>
> <img border=0 width=576 height=41 id="_x0000_i1026"
> src="HttpNimletDriver?
> nimlet=DownloadAttachmentNimlet&fileName=image002.jpg&folderName=INBOX&me
> ssag eID=50&partIndex=3&disposition=inline" alt=878e78f2.jpg><br>
> <img border=0 width=600 height=5 id="_x0000_i1027"
> src="HttpNimletDriver?
> nimlet=DownloadAttachmentNimlet&fileName=image003.jpg&folderName=INBOX&me
> ssag eID=50&partIndex=2&disposition=inline"
> alt=878e7911.jpg> <o:p></o:p></span></ font></p>
>
> <p class=MsoNormal align=center style='text-align:center'><font size=2
> face=Arial><span style='font-size:10.0pt;font-family:Arial'><img border=0
> width=98 height=43 id="_x0000_i1028" src="HttpNimletDriver?
> nimlet=DownloadAttachmentNimlet&fileName=image004.jpg&folderName=INBOX&me
> ssag eID=50&partIndex=1&disposition=inline"
> alt=878e7930.jpg><br>
> 411 <st1:City w:st="on"><st1:place
> w:st="on">Waverley</st1:place></st1:City> <st1:Street
> w:st="on"><st1:address w:st="on">Oaks Road</st1:address></st1:Street><br>
> <st1:place w:st="on"><st1:City w:st="on">Waltham</st1:City>, <st1:State
> w:st="on">MA</st1:State>
> <st1:PostalCode w:st="on">02452</st1:PostalCode></st1:place><br>
> North America - 1 [phone] | <st1:place
> w:st="on">Europe</st1:place> - 31
> (0)20 777 2277<br>
> <a href="http://www.peoplecube.com" title="http://
> www.peoplecube.com">www.peoplecube.com</a>
>| <a href="mailto:***@peoplecube.com"
> title="mailto:***@peoplecube.com">***@peoplecube.com</a><br>
> 2006 PeopleCube | All rights reserved.<o:p></o:p></span></font></p>
>
> <p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
> font-family:Arial'><br>
> All trademarks, service marks and product names mentioned herein are the
> property of PeopleCube or their respective owners. <br>
> <br>
> You are receiving this notice because you are currently listed as a
> PeopleCube
> customer. If this is in error, please contact us at <a
> href="mailto:***@peoplecube.com"
> title="mailto:***@peoplecube.com">***@peoplecube.com</a>.
> <br>
> <br>
> </span></font><o:p></o:p></p>
>
> </div>
>
> </body>
>
> </html>
> <p>
> * MMXP-TALK Web Page:
> http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML
>
>
> * MMXP-TALK Web Page:
> http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML



--
Ian Eiloart
IT Services, University of Sussex


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[Jack C Newton]

Again, only an issues if you schedule in multiple time zones.

I accidently heard through a company called Notify (who I heard through
someone else) that they are currently running a Beta (though I honestly don't
know if it's an open beta or not) to use their product with Meeting Maker.
Now last I checked, Notify supports a metric buttload of devices. Looks to me
that Meeting Maker will be using Notify in the future and from what I can
tell, that looks like a good thing. No comments yet from Peoplecube on it
though...

-Jack Newton

From: Erik Froese <***@GMAIL.COM>
Date: 2006/09/12 Tue AM 08:20:18 CDT
To: MMXP-***@LISTSERV.EMORY.EDU
Subject: Re: Daylight Saving Time effects on 7.5

I have to say I'm completely fed up with Meeting Maker as a product.
Is there anything that supports handheld devices as well as Meeting
Maker does without putting all of our eggs in Outlook's basket?

Erik Froese

On 9/12/06, Stuenkel, MaryBeth <***@umich.edu> wrote:
>
>
>
>
> Tim,
>
>
>
> We are wrestling with the same issue. We, too, are currently using version
> 7.5. Ours is a hub environment, so an upgrade process is no simple task.
> Especially troublesome is the fact that 8.6 is still only a promise, and
> with the track record of Meetingmaker releases we are loathe to move to a
> new version without significant field testing.
>
>
>
> Time is critical to a calendaring application and we so haven't even
> considered the workarounds you mentioned. Ideally, PeopleCube would
provide
> a patch for all of their versions. This could be the final nail in
> Meetingmaker's coffin as a central calendaring service here.
>
>
>
>
> --MaryBeth Stuenkel
>
> University of Michigan
>
>
>
>
> ________________________________
>
>
> From: Meeting Maker Discussion List [mailto:MMXP-***@LISTSERV.EMORY.EDU]
On
> Behalf Of Tim Gleason
> Sent: Tuesday, September 12, 2006 8:59 AM
> To: MMXP-***@LISTSERV.EMORY.EDU
> Subject: Daylight Saving Time effects on 7.5
>
>
>
>
> We were caught by surprise with the recent email sent by PeopleCube
> regarding the changes to Daylight Savings Time (DST) and the effects on
> Meeting Maker. We have an installation of version 7.5 supporting 2100
users
> which now appears we will be forced to upgrade to 8.6 once it is released
in
> October. I have attached the email to the end of this message in case you
> missed it. This announcement comes at a bad time for us given may other
> projects we need to complete in the same timeframe. Cost is the least of
> our worries since we are entitled to the upgrade under maintenance. The
> ideal situation is deferring the upgrade so that we can ease the pain on
our
> users and staff with changes to multiple applications.
>
>
>
> We are in the process of testing our current 7.5 installation and the
> effects these DST changes. Has anyone done similar tests and have some
> results they are willing to share? Can the application be tricked by
> changing the clocks on the server or client, altering the time zone or a
> combination of both? What impact will this have on the calendar and other
> clients like PDAs both on March 11 and the traditional April date? I will
> send our results once they have been compiled.
>
>
>
> Regards
>
>
>
> Tim Gleason
>
> Sr. Technical Architect
>
> University Information Systems
>
> Harvard University
>
> 617.495.5811
>
> ***@harvard.edu
>
>
>
>
>
> -------- Original Message --------
> Subject: Important Daylight Saving Time Information for Meeting Maker
Users
> Date: Wed, 23 Aug 2006 10:24:40 -0400
> From: PeopleCube <***@peoplecube.com>
>
>
>
>
>
> Dear Meeting Maker User,
>
> Exciting things continue to happen within our Meeting Maker product line.
> However, it is important for us to communicate some very important
> information that will affect all of our Meeting Maker customers. In 2005,
> Congress passed the Energy Policy Act of 2005. A significant provision of
> the act extends daylight saving time (DST) by 4 weeks beginning in March of
> 2007. This change will obviously affect all Meeting Maker calendars, as any
> appointments or meetings scheduled during these four weeks will appear at
> the incorrect time.
>
> As a result of this new law, PeopleCube will release Meeting Maker 8.6
> specifically to address the upcoming change in DST. We have targeted a
> release date of October 2006 that should provide you with enough time to
> test and deploy this new release. It will require a full upgrade including
> both a database and client upgrade. To ensure continuous value of your
> Meeting Maker solution, we strongly recommend you prepare to upgrade your
> Meeting Maker installation to comply with this new guideline.
>
> This new release will be made available for free to all Meeting Maker
> customers with an active maintenance contract via the PeopleCube Online
> Support Portal at http://connect.peoplecube.com/support/.
> If you have any questions or would like to inquire about joining our
> Maintenance Advantage Program, contact us at 1-800-282-7319 or
> ***@peoplecube.com. Our staff is available to assist you in any way
> possible.
>
> We will continue to provide updates to these changes through eNews, our
> quarterly electronic newsletter. If you are not currently subscribed to
> eNews but would like to start receiving it, simply send an email to
> ***@peoplecube.com with “Subscribeâ€? in the subject line.
>
> From all of us here at PeopleCube, we thank you for your continued
support.
>
>
>
>
>
> 411 Waverley Oaks Road
> Waltham, MA 02452
> North America - 1 [phone] | Europe - 31 (0)20 777 2277
> www.peoplecube.com | ***@peoplecube.com
> 2006 PeopleCube | All rights reserved.
>
>
> All trademarks, service marks and product names mentioned herein are the
> property of PeopleCube or their respective owners.
>
> You are receiving this notice because you are currently listed as a
> PeopleCube customer. If this is in error, please contact us at
> ***@peoplecube.com.
>
>
>
> * MMXP-TALK Web Page:
> http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[Anderson, Kelly]

Hi Jack,

I think I'm not completely understanding what you're meaning about the non-issue with time zones. I just changed my OS clock, and MM did not recognize the OS time. It kept the time zone that was configured for my user (Eastern Time). I had to manually pick a time zone one hour earlier than Eastern to get it to switch.

From what I *think* I understand, the MM client gets the time zone from the user configuration that is specified on the server when the user is created. Then if the user travels, they can manually change the time zone as necessary. So, the MM client doesn't pay attention to the time zone of the OS.

I don't think it's wize to ask all our users to manually change their time zones when it goes into effect and then after the "old" date passes... . But, like I said, maybe I'm just confused about what you mean.

We're running 7.5...and my client is on Win XP.

Thanks.

--Kelly

-----Original Message-----
From: Meeting Maker Discussion List [mailto:MMXP-***@LISTSERV.EMORY.EDU] On Behalf Of Jack C Newton
Sent: Tuesday, September 12, 2006 9:43 AM
To: MMXP-***@LISTSERV.EMORY.EDU
Subject: Re: [MMXP-TALK] Daylight Saving Time effects on 7.5

Again, only an issues if you schedule in multiple time zones.

I accidently heard through a company called Notify (who I heard through someone else) that they are currently running a Beta (though I honestly don't know if it's an open beta or not) to use their product with Meeting Maker.
Now last I checked, Notify supports a metric buttload of devices. Looks to me that Meeting Maker will be using Notify in the future and from what I can tell, that looks like a good thing. No comments yet from Peoplecube on it though...

-Jack Newton

From: Erik Froese <***@GMAIL.COM>
Date: 2006/09/12 Tue AM 08:20:18 CDT
To: MMXP-***@LISTSERV.EMORY.EDU
Subject: Re: Daylight Saving Time effects on 7.5

I have to say I'm completely fed up with Meeting Maker as a product.
Is there anything that supports handheld devices as well as Meeting Maker does without putting all of our eggs in Outlook's basket?

Erik Froese

On 9/12/06, Stuenkel, MaryBeth <***@umich.edu> wrote:
>
>
>
>
> Tim,
>
>
>
> We are wrestling with the same issue. We, too, are currently using
> version 7.5. Ours is a hub environment, so an upgrade process is no simple task.
> Especially troublesome is the fact that 8.6 is still only a promise,
> and with the track record of Meetingmaker releases we are loathe to
> move to a new version without significant field testing.
>
>
>
> Time is critical to a calendaring application and we so haven't even
> considered the workarounds you mentioned. Ideally, PeopleCube would
provide
> a patch for all of their versions. This could be the final nail in
> Meetingmaker's coffin as a central calendaring service here.
>
>
>
>
> --MaryBeth Stuenkel
>
> University of Michigan
>
>
>
>
> ________________________________
>
>
> From: Meeting Maker Discussion List
> [mailto:MMXP-***@LISTSERV.EMORY.EDU]
On
> Behalf Of Tim Gleason
> Sent: Tuesday, September 12, 2006 8:59 AM
> To: MMXP-***@LISTSERV.EMORY.EDU
> Subject: Daylight Saving Time effects on 7.5
>
>
>
>
> We were caught by surprise with the recent email sent by PeopleCube
> regarding the changes to Daylight Savings Time (DST) and the effects
> on Meeting Maker. We have an installation of version 7.5 supporting
> 2100
users
> which now appears we will be forced to upgrade to 8.6 once it is
> released
in
> October. I have attached the email to the end of this message in case
> you missed it. This announcement comes at a bad time for us given may
> other projects we need to complete in the same timeframe. Cost is the
> least of our worries since we are entitled to the upgrade under
> maintenance. The ideal situation is deferring the upgrade so that we
> can ease the pain on
our
> users and staff with changes to multiple applications.
>
>
>
> We are in the process of testing our current 7.5 installation and the
> effects these DST changes. Has anyone done similar tests and have
> some results they are willing to share? Can the application be
> tricked by changing the clocks on the server or client, altering the
> time zone or a combination of both? What impact will this have on the
> calendar and other clients like PDAs both on March 11 and the
> traditional April date? I will send our results once they have been compiled.
>
>
>
> Regards
>
>
>
> Tim Gleason
>
> Sr. Technical Architect
>
> University Information Systems
>
> Harvard University
>
> 617.495.5811
>
> ***@harvard.edu
>
>
>
>
>
> -------- Original Message --------
> Subject: Important Daylight Saving Time Information for Meeting Maker
Users
> Date: Wed, 23 Aug 2006 10:24:40 -0400
> From: PeopleCube <***@peoplecube.com>
>
>
>
>
>
> Dear Meeting Maker User,
>
> Exciting things continue to happen within our Meeting Maker product line.
> However, it is important for us to communicate some very important
> information that will affect all of our Meeting Maker customers. In
> 2005, Congress passed the Energy Policy Act of 2005. A significant
> provision of the act extends daylight saving time (DST) by 4 weeks
> beginning in March of 2007. This change will obviously affect all
> Meeting Maker calendars, as any appointments or meetings scheduled
> during these four weeks will appear at the incorrect time.
>
> As a result of this new law, PeopleCube will release Meeting Maker
> 8.6 specifically to address the upcoming change in DST. We have
> targeted a release date of October 2006 that should provide you with
> enough time to test and deploy this new release. It will require a
> full upgrade including both a database and client upgrade. To ensure
> continuous value of your Meeting Maker solution, we strongly recommend
> you prepare to upgrade your Meeting Maker installation to comply with this new guideline.
>
> This new release will be made available for free to all Meeting Maker
> customers with an active maintenance contract via the PeopleCube
> Online Support Portal at http://connect.peoplecube.com/support/.
> If you have any questions or would like to inquire about joining our
> Maintenance Advantage Program, contact us at 1-800-282-7319 or
> ***@peoplecube.com. Our staff is available to assist you in any way
> possible.
>
> We will continue to provide updates to these changes through eNews,
> our quarterly electronic newsletter. If you are not currently
> subscribed to eNews but would like to start receiving it, simply send
> an email to ***@peoplecube.com with “Subscribe� in the subject line.
>
> From all of us here at PeopleCube, we thank you for your continued
support.
>
>
>
>
>
> 411 Waverley Oaks Road
> Waltham, MA 02452
> North America - 1 [phone] | Europe - 31 (0)20 777 2277
> www.peoplecube.com | ***@peoplecube.com
> 2006 PeopleCube | All rights reserved.
>
>
> All trademarks, service marks and product names mentioned herein are
> the property of PeopleCube or their respective owners.
>
> You are receiving this notice because you are currently listed as a
> PeopleCube customer. If this is in error, please contact us at
> ***@peoplecube.com.
>
>
>
> * MMXP-TALK Web Page:
> http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-T

[Ian Eiloart]

--On 12 September 2006 09:32:29 -0400 "Anderson, Kelly"
<***@UMICH.EDU> wrote:

> Some additional considerations, as I've been doing some research:
>
> The Web Client, which was a Java applet in v7.5.3 (which we run) is now
> an Apache Tomcat based Java Servlet, and we are now required to run an
> Apache web server to support web clients (currently we "borrow" the space
> from our web group, which does not support Tomcat at this time). More
> hardware and support will cost money.

Hardware cost should be minimal. We run our entire MM setup on a single
Apple XServe, with 10 calendars, hub and webcalendar. Of course, if we
followed Meeting Maker's recommendations, we'd be using a dozen different
machines!

It took me a day to set up the webcalendar, with a new install of Tomcat
(which we don't use for anything else), and a half day to upgrade the
calendar once.

> And I've heard that the release date is now the end of November, not the
> end of October. How are we supposed to make time for testing if this
> slips with the holidays approaching, the end of term, production service
> freezes, not to mention our current projects, before March?
>
> --Kelly
>
> University of Michigan
>
>
>
>
> ________________________________
>
> From: Meeting Maker Discussion List [mailto:MMXP-***@LISTSERV.EMORY.EDU]
> On Behalf Of Tim Gleason Sent: Tuesday, September 12, 2006 8:59 AM
> To: MMXP-***@LISTSERV.EMORY.EDU
> Subject: [MMXP-TALK] Daylight Saving Time effects on 7.5
>
>
>
> We were caught by surprise with the recent email sent by PeopleCube
> regarding the changes to Daylight Savings Time (DST) and the effects on
> Meeting Maker. We have an installation of version 7.5 supporting 2100
> users which now appears we will be forced to upgrade to 8.6 once it is
> released in October. I have attached the email to the end of this
> message in case you missed it. This announcement comes at a bad time for
> us given may other projects we need to complete in the same timeframe.
> Cost is the least of our worries since we are entitled to the upgrade
> under maintenance. The ideal situation is deferring the upgrade so that
> we can ease the pain on our users and staff with changes to multiple
> applications.
>
>
>
> We are in the process of testing our current 7.5 installation and the
> effects these DST changes. Has anyone done similar tests and have some
> results they are willing to share? Can the application be tricked by
> changing the clocks on the server or client, altering the time zone or a
> combination of both? What impact will this have on the calendar and
> other clients like PDAs both on March 11 and the traditional April date?
> I will send our results once they have been compiled.
>
>
>
> Regards
>
>
>
> Tim Gleason
>
> Sr. Technical Architect
>
> University Information Systems
>
> Harvard University
>
> 617.495.5811
>
> ***@harvard.edu
>
>
>
>
>
> -------- Original Message --------
> Subject: Important Daylight Saving Time Information for Meeting Maker
> Users Date: Wed, 23 Aug 2006 10:24:40 -0400
> From: PeopleCube <***@peoplecube.com>
> <mailto:***@peoplecube.com>
>
>
>
>
>
> Dear Meeting Maker User,
>
> Exciting things continue to happen within our Meeting Maker product line.
> However, it is important for us to communicate some very important
> information that will affect all of our Meeting Maker customers. In 2005,
> Congress passed the Energy Policy Act of 2005. A significant provision of
> the act extends daylight saving time (DST) by 4 weeks beginning in March
> of 2007. This change will obviously affect all Meeting Maker calendars,
> as any appointments or meetings scheduled during these four weeks will
> appear at the incorrect time.
>
> As a result of this new law, PeopleCube will release Meeting Maker 8.6
> specifically to address the upcoming change in DST. We have targeted a
> release date of October 2006 that should provide you with enough time to
> test and deploy this new release. It will require a full upgrade
> including both a database and client upgrade. To ensure continuous value
> of your Meeting Maker solution, we strongly recommend you prepare to
> upgrade your Meeting Maker installation to comply with this new
> guideline.
>
> This new release will be made available for free to all Meeting Maker
> customers with an active maintenance contract via the PeopleCube Online
> Support Portal at http://connect.peoplecube.com/support/. If you have any
> questions or would like to inquire about joining our Maintenance
> Advantage Program, contact us at 1-800-282-7319 or ***@peoplecube.com.
> Our staff is available to assist you in any way possible.
>
> We will continue to provide updates to these changes through eNews, our
> quarterly electronic newsletter. If you are not currently subscribed to
> eNews but would like to start receiving it, simply send an email to
> ***@peoplecube.com
> <mailto:***@peoplecube.com?Subject=Subscribe%20to%20eNews> with
> “Subscribe” in the subject line.
>
> From all of us here at PeopleCube, we thank you for your continued
> support.
>
>
>
>
>
> 411 Waverley Oaks Road
> Waltham, MA 02452
> North America - 1 [phone] | Europe - 31 (0)20 777 2277
> www.peoplecube.com | ***@peoplecube.com
> 2006 PeopleCube | All rights reserved.
>
>
> All trademarks, service marks and product names mentioned herein are the
> property of PeopleCube or their respective owners.
>
> You are receiving this notice because you are currently listed as a
> PeopleCube customer. If this is in error, please contact us at
> ***@peoplecube.com.
>
>
>
> * MMXP-TALK Web Page:
> http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML
>



--
Ian Eiloart
IT Services, University of Sussex


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[Ian Eiloart]

--On 12 September 2006 09:52:13 -0400 "Anderson, Kelly"
<***@UMICH.EDU> wrote:

> Hi Jack,
>
> I think I'm not completely understanding what you're meaning about the
> non-issue with time zones. I just changed my OS clock, and MM did not
> recognize the OS time.

Of course that wouldn't be a great workaround anyway - break everything
else time dependent (like email timestamps, file timestamps, backup
schedules, etc) to fix Meeting Maker.

> It kept the time zone that was configured for my
> user (Eastern Time). I had to manually pick a time zone one hour earlier
> than Eastern to get it to switch.
>
> From what I *think* I understand, the MM client gets the time zone from
> the user configuration that is specified on the server when the user is
> created. Then if the user travels, they can manually change the time
> zone as necessary. So, the MM client doesn't pay attention to the time
> zone of the OS.
>
> I don't think it's wize to ask all our users to manually change their
> time zones when it goes into effect and then after the "old" date
> passes... . But, like I said, maybe I'm just confused about what you
> mean.
>
> We're running 7.5...and my client is on Win XP.
>
> Thanks.
>
> --Kelly
>
> -----Original Message-----
> From: Meeting Maker Discussion List [mailto:MMXP-***@LISTSERV.EMORY.EDU]
> On Behalf Of Jack C Newton Sent: Tuesday, September 12, 2006 9:43 AM
> To: MMXP-***@LISTSERV.EMORY.EDU
> Subject: Re: [MMXP-TALK] Daylight Saving Time effects on 7.5
>
> Again, only an issues if you schedule in multiple time zones.
>
> I accidently heard through a company called Notify (who I heard through
> someone else) that they are currently running a Beta (though I honestly
> don't know if it's an open beta or not) to use their product with Meeting
> Maker. Now last I checked, Notify supports a metric buttload of devices.
> Looks to me that Meeting Maker will be using Notify in the future and
> from what I can tell, that looks like a good thing. No comments yet from
> Peoplecube on it though...
>
> -Jack Newton
>
> From: Erik Froese <***@GMAIL.COM>
> Date: 2006/09/12 Tue AM 08:20:18 CDT
> To: MMXP-***@LISTSERV.EMORY.EDU
> Subject: Re: Daylight Saving Time effects on 7.5
>
> I have to say I'm completely fed up with Meeting Maker as a product.
> Is there anything that supports handheld devices as well as Meeting Maker
> does without putting all of our eggs in Outlook's basket?
>
> Erik Froese
>
> On 9/12/06, Stuenkel, MaryBeth <***@umich.edu> wrote:
>>
>>
>>
>>
>> Tim,
>>
>>
>>
>> We are wrestling with the same issue. We, too, are currently using
>> version 7.5. Ours is a hub environment, so an upgrade process is no
>> simple task. Especially troublesome is the fact that 8.6 is still only a
>> promise, and with the track record of Meetingmaker releases we are
>> loathe to move to a new version without significant field testing.
>>
>>
>>
>> Time is critical to a calendaring application and we so haven't even
>> considered the workarounds you mentioned. Ideally, PeopleCube would
> provide
>> a patch for all of their versions. This could be the final nail in
>> Meetingmaker's coffin as a central calendaring service here.
>>
>>
>>
>>
>> --MaryBeth Stuenkel
>>
>> University of Michigan
>>
>>
>>
>>
>> ________________________________
>>
>>
>> From: Meeting Maker Discussion List
>> [mailto:MMXP-***@LISTSERV.EMORY.EDU]
> On
>> Behalf Of Tim Gleason
>> Sent: Tuesday, September 12, 2006 8:59 AM
>> To: MMXP-***@LISTSERV.EMORY.EDU
>> Subject: Daylight Saving Time effects on 7.5
>>
>>
>>
>>
>> We were caught by surprise with the recent email sent by PeopleCube
>> regarding the changes to Daylight Savings Time (DST) and the effects
>> on Meeting Maker. We have an installation of version 7.5 supporting
>> 2100
> users
>> which now appears we will be forced to upgrade to 8.6 once it is
>> released
> in
>> October. I have attached the email to the end of this message in case
>> you missed it. This announcement comes at a bad time for us given may
>> other projects we need to complete in the same timeframe. Cost is the
>> least of our worries since we are entitled to the upgrade under
>> maintenance. The ideal situation is deferring the upgrade so that we
>> can ease the pain on
> our
>> users and staff with changes to multiple applications.
>>
>>
>>
>> We are in the process of testing our current 7.5 installation and the
>> effects these DST changes. Has anyone done similar tests and have
>> some results they are willing to share? Can the application be
>> tricked by changing the clocks on the server or client, altering the
>> time zone or a combination of both? What impact will this have on the
>> calendar and other clients like PDAs both on March 11 and the
>> traditional April date? I will send our results once they have been
>> compiled.
>>
>>
>>
>> Regards
>>
>>
>>
>> Tim Gleason
>>
>> Sr. Technical Architect
>>
>> University Information Systems
>>
>> Harvard University
>>
>> 617.495.5811
>>
>> ***@harvard.edu
>>
>>
>>
>>
>>
>> -------- Original Message --------
>> Subject: Important Daylight Saving Time Information for Meeting Maker
> Users
>> Date: Wed, 23 Aug 2006 10:24:40 -0400
>> From: PeopleCube <***@peoplecube.com>
>>
>>
>>
>>
>>
>> Dear Meeting Maker User,
>>
>> Exciting things continue to happen within our Meeting Maker product
>> line. However, it is important for us to communicate some very
>> important information that will affect all of our Meeting Maker
>> customers. In 2005, Congress passed the Energy Policy Act of 2005. A
>> significant provision of the act extends daylight saving time (DST) by
>> 4 weeks beginning in March of 2007. This change will obviously affect
>> all Meeting Maker calendars, as any appointments or meetings scheduled
>> during these four weeks will appear at the incorrect time.
>>
>> As a result of this new law, PeopleCube will release Meeting Maker
>> 8.6 specifically to address the upcoming change in DST. We have
>> targeted a release date of October 2006 that should provide you with
>> enough time to test and deploy this new release. It will require a
>> full upgrade including both a database and client upgrade. To ensure
>> continuous value of your Meeting Maker solution, we strongly recommend
>> you prepare to upgrade your Meeting Maker installation to comply with
>> this new guideline.
>>
>> This new release will be made available for free to all Meeting Maker
>> customers with an active maintenance contract via the PeopleCube
>> Online Support Portal at http://connect.peoplecube.com/support/.
>> If you have any questions or would like to inquire about joining our
>> Maintenance Advantage Program, contact us at 1-800-282-7319 or
>> ***@peoplecube.com. Our staff is available to assist you in any way
>> possible.
>>
>> We will continue to provide updates to these changes through eNews,
>> our quarterly electronic newsletter. If you are not currently
>> subscribed to eNews but would like to start receiving it, simply send
>> an email to ***@peoplecube.com with “Subscribe� in the
>> subject line.
>>
>> From all of us here at PeopleCube, we thank you for your continued
> support.
>>
>>
>>
>>
>>
>> 411 Waverley Oaks Road
>> Waltham, MA 02452
>> North America - 1 [phone] | Europe - 31 (0)20 777 2277
>> www.peoplecube.com | ***@peoplecube.com
>> 2006 PeopleCube | All rights reserved.
>>
>>
>> All trademarks, service marks and product names mentioned herein are
>> the property of PeopleCube or their respective owners.
>>
>> You are receiving this notice because you are currently listed as a
>> PeopleCube customer. If this is in error, please contact us at
>> ***@peoplecube.com.
>>
>>
>>
>> * MMXP-TALK Web Page:
>> http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML
>
>
> * MMXP-TALK Web Page:
> http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML



--
Ian Eiloart
IT Services, University of Sussex


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[Ian Eiloart]

--On 12 September 2006 08:58:50 -0400 Tim Gleason <***@HARVARD.EDU>
wrote:

> We were caught by surprise with the recent email sent by PeopleCube
> regarding the changes to Daylight Savings Time (DST) and the effects on
> Meeting Maker....

I wonder whether Meeting Maker can assure us that the new version of
Meeting Maker will be able to handle future DST changes more smoothly?
After all, it's only a Time Zone database that needs updating. It should
not be too hard to have a mechanism whereby the client checks the db
version against the server, and updates as necessary.


--
Ian Eiloart
IT Services, University of Sussex


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[Jack C Newton]

According to what I heard, they designed MeetingMaker 8.6 so that the
timzezone database can just be swapped out if there are any other future
surprise changes to timezones.

-Jack Newton

From: Ian Eiloart <***@SUSSEX.AC.UK>
Date: 2006/09/13 Wed AM 04:59:49 CDT
To: MMXP-***@LISTSERV.EMORY.EDU
Subject: Re: Daylight Saving Time effects on 7.5

--On 12 September 2006 08:58:50 -0400 Tim Gleason <***@HARVARD.EDU>
wrote:

> We were caught by surprise with the recent email sent by PeopleCube
> regarding the changes to Daylight Savings Time (DST) and the effects on
> Meeting Maker....

I wonder whether Meeting Maker can assure us that the new version of
Meeting Maker will be able to handle future DST changes more smoothly?
After all, it's only a Time Zone database that needs updating. It should
not be too hard to have a mechanism whereby the client checks the db
version against the server, and updates as necessary.


--
Ian Eiloart
IT Services, University of Sussex


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[David A. Woyciesjes]

At 08:23 AM 9/13/2006, Jack C Newton wrote:
>According to what I heard, they designed MeetingMaker 8.6 so that the
>timzezone database can just be swapped out if there are any other future
>surprise changes to timezones.
>
>-Jack Newton

This makes me wonder. Is there a time zone info file that
can just be edited to reflect the changes? Might need to use a hex
editor or something, but there must be a hack to fix this. Has
anybody investigated this?


--
--- David Woyciesjes
--- C&IS Support Specialist
--- Yale University School Of Medicine
--- Dermatology Department

NOTICE:
The information contained in this message may be privileged
and confidential. If you are NOT the intended recipient, please
notify the sender immediately with a copy to ***@Yale.edu
and destroy this message. Please be aware that email communication
can be intercepted in transmission or misdirected.
Your use of email to communicate protected health
information to us indicates that you acknowledge and accept the
possible risks associated with such communication. Please consider
communicating any sensitive information by telephone, fax or mail. If
you do not wish to have your information sent by email, please
contact the sender immediately.


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[Ian Eiloart]

--On 13 September 2006 08:35:33 -0400 "David A. Woyciesjes"
<***@YALE.EDU> wrote:

> At 08:23 AM 9/13/2006, Jack C Newton wrote:
>> According to what I heard, they designed MeetingMaker 8.6 so that the
>> timzezone database can just be swapped out if there are any other future
>> surprise changes to timezones.
>>
>> -Jack Newton
>
> This makes me wonder. Is there a time zone info file that can
> just be edited to reflect the changes? Might need to use a hex editor or
> something, but there must be a hack to fix this. Has anybody investigated
> this?

My guess it that a problem arises if your client has a different database
from the server.

--
Ian Eiloart
IT Services, University of Sussex


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[David A. Woyciesjes]

At 09:35 AM 9/13/2006, Ian Eiloart wrote:
>--On 13 September 2006 08:35:33 -0400 "David A. Woyciesjes"
><***@YALE.EDU> wrote:
>
>>At 08:23 AM 9/13/2006, Jack C Newton wrote:
>>>According to what I heard, they designed MeetingMaker 8.6 so that the
>>>timzezone database can just be swapped out if there are any other future
>>>surprise changes to timezones.
>>>
>>>-Jack Newton
>>
>> This makes me wonder. Is there a time zone info file that can
>>just be edited to reflect the changes? Might need to use a hex editor or
>>something, but there must be a hack to fix this. Has anybody investigated
>>this?
>
>My guess it that a problem arises if your client has a different
>database from the server.

Hmmm, definite possibility. But for small installations, it
may not be such an issue.

I did find this file - C:\Program Files\Meeting
Maker\mmtzdb.mdb. Judging by the name, it's the time zone file, for
v.7.5.0 here.. I'll have to poke around and see if I can find
something that can read the info in it. Maybe it could be edited,
then passed around somehow to the clients.
If anyone else can "read" the file, do speak up.

Of course, this is the work that MeetingMaker/PeopleCube
should be doing...;-)


--
--- David Woyciesjes
--- C&IS Support Specialist
--- Yale University School Of Medicine
--- Dermatology Department

NOTICE:
The information contained in this message may be privileged
and confidential. If you are NOT the intended recipient, please
notify the sender immediately with a copy to ***@Yale.edu
and destroy this message. Please be aware that email communication
can be intercepted in transmission or misdirected.
Your use of email to communicate protected health
information to us indicates that you acknowledge and accept the
possible risks associated with such communication. Please consider
communicating any sensitive information by telephone, fax or mail. If
you do not wish to have your information sent by email, please
contact the sender immediately.


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[Craft, Robert]

Given that 8.x will not work for us here, this may be GOOD news.

-----Original Message-----
From: Meeting Maker Discussion List
[mailto:MMXP-***@listserv.cc.EMORY.EDU] On Behalf Of David A.
Woyciesjes
Sent: Wednesday, September 13, 2006 10:08 AM
To: MMXP-***@listserv.cc.EMORY.EDU
Subject: Re: Daylight Saving Time effects on 7.5


Hmmm, definite possibility. But for small installations, it
may not be such an issue.

I did find this file - C:\Program Files\Meeting
Maker\mmtzdb.mdb. Judging by the name, it's the time zone file, for
v.7.5.0 here.. I'll have to poke around and see if I can find
something that can read the info in it. Maybe it could be edited,
then passed around somehow to the clients.
If anyone else can "read" the file, do speak up.

Of course, this is the work that MeetingMaker/PeopleCube
should be doing...;-)



*******************************************
Confidentiality Notice: This e-mail message, including any attachments, from AtlantiCare contains information which is CONFIDENTIAL AND/OR LEGALLY PRIVILEGED.
The information is intended only for the use of the individual named above and may not be disseminated to any other party without AtlantiCare's written permission.
If you are not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination,
disclosure, distribution, copying or taking of any action in reliance on the contents of this e-mailed information is strictly prohibited.
If you have received this e-mail in error, please notify us immediately by telephone at 609-569-7070 or notify us by e-mail at ***@Atlanticare.org
to arrange for the return of these documents to us without cost to you.


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[Jack C Newton]

Ah but you just answered your own question. Meeting Maker doesn't shift times
based on the system clock. So if you were to change you system clock from 4
pm to 5 pm, your noon time meeting in Meeting Maker is still at noontime.
Meeting Maker uses the system clock to let it know what time it currently is
for past meetings, reminders and the like.

Try it.

-Jack Newton

From: "Anderson, Kelly" <***@UMICH.EDU>
Date: 2006/09/12 Tue AM 08:52:13 CDT
To: MMXP-***@LISTSERV.EMORY.EDU
Subject: Re: Daylight Saving Time effects on 7.5

Hi Jack,

I think I'm not completely understanding what you're meaning about the non-
issue with time zones. I just changed my OS clock, and MM did not recognize
the OS time. It kept the time zone that was configured for my user (Eastern
Time). I had to manually pick a time zone one hour earlier than Eastern to
get it to switch.

>From what I *think* I understand, the MM client gets the time zone from the
user configuration that is specified on the server when the user is created.
Then if the user travels, they can manually change the time zone as
necessary. So, the MM client doesn't pay attention to the time zone of the
OS.

I don't think it's wize to ask all our users to manually change their time
zones when it goes into effect and then after the "old" date passes... .
But, like I said, maybe I'm just confused about what you mean.

We're running 7.5...and my client is on Win XP.

Thanks.

--Kelly

-----Original Message-----
From: Meeting Maker Discussion List [mailto:MMXP-***@LISTSERV.EMORY.EDU] On
Behalf Of Jack C Newton
Sent: Tuesday, September 12, 2006 9:43 AM
To: MMXP-***@LISTSERV.EMORY.EDU
Subject: Re: [MMXP-TALK] Daylight Saving Time effects on 7.5

Again, only an issues if you schedule in multiple time zones.

I accidently heard through a company called Notify (who I heard through
someone else) that they are currently running a Beta (though I honestly don't
know if it's an open beta or not) to use their product with Meeting Maker.
Now last I checked, Notify supports a metric buttload of devices. Looks to me
that Meeting Maker will be using Notify in the future and from what I can
tell, that looks like a good thing. No comments yet from Peoplecube on it
though...

-Jack Newton

From: Erik Froese <***@GMAIL.COM>
Date: 2006/09/12 Tue AM 08:20:18 CDT
To: MMXP-***@LISTSERV.EMORY.EDU
Subject: Re: Daylight Saving Time effects on 7.5

I have to say I'm completely fed up with Meeting Maker as a product.
Is there anything that supports handheld devices as well as Meeting Maker
does without putting all of our eggs in Outlook's basket?

Erik Froese

On 9/12/06, Stuenkel, MaryBeth <***@umich.edu> wrote:
>
>
>
>
> Tim,
>
>
>
> We are wrestling with the same issue. We, too, are currently using
> version 7.5. Ours is a hub environment, so an upgrade process is no simple
task.
> Especially troublesome is the fact that 8.6 is still only a promise,
> and with the track record of Meetingmaker releases we are loathe to
> move to a new version without significant field testing.
>
>
>
> Time is critical to a calendaring application and we so haven't even
> considered the workarounds you mentioned. Ideally, PeopleCube would
provide
> a patch for all of their versions. This could be the final nail in
> Meetingmaker's coffin as a central calendaring service here.
>
>
>
>
> --MaryBeth Stuenkel
>
> University of Michigan
>
>
>
>
> ________________________________
>
>
> From: Meeting Maker Discussion List
> [mailto:MMXP-***@LISTSERV.EMORY.EDU]
On
> Behalf Of Tim Gleason
> Sent: Tuesday, September 12, 2006 8:59 AM
> To: MMXP-***@LISTSERV.EMORY.EDU
> Subject: Daylight Saving Time effects on 7.5
>
>
>
>
> We were caught by surprise with the recent email sent by PeopleCube
> regarding the changes to Daylight Savings Time (DST) and the effects
> on Meeting Maker. We have an installation of version 7.5 supporting
> 2100
users
> which now appears we will be forced to upgrade to 8.6 once it is
> released
in
> October. I have attached the email to the end of this message in case
> you missed it. This announcement comes at a bad time for us given may
> other projects we need to complete in the same timeframe. Cost is the
> least of our worries since we are entitled to the upgrade under
> maintenance. The ideal situation is deferring the upgrade so that we
> can ease the pain on
our
> users and staff with changes to multiple applications.
>
>
>
> We are in the process of testing our current 7.5 installation and the
> effects these DST changes. Has anyone done similar tests and have
> some results they are willing to share? Can the application be
> tricked by changing the clocks on the server or client, altering the
> time zone or a combination of both? What impact will this have on the
> calendar and other clients like PDAs both on March 11 and the
> traditional April date? I will send our results once they have been
compiled.
>
>
>
> Regards
>
>
>
> Tim Gleason
>
> Sr. Technical Architect
>
> University Information Systems
>
> Harvard University
>
> 617.495.5811
>
> ***@harvard.edu
>
>
>
>
>
> -------- Original Message --------
> Subject: Important Daylight Saving Time Information for Meeting Maker
Users
> Date: Wed, 23 Aug 2006 10:24:40 -0400
> From: PeopleCube <***@peoplecube.com>
>
>
>
>
>
> Dear Meeting Maker User,
>
> Exciting things continue to happen within our Meeting Maker product line.
> However, it is important for us to communicate some very important
> information that will affect all of our Meeting Maker customers. In
> 2005, Congress passed the Energy Policy Act of 2005. A significant
> provision of the act extends daylight saving time (DST) by 4 weeks
> beginning in March of 2007. This change will obviously affect all
> Meeting Maker calendars, as any appointments or meetings scheduled
> during these four weeks will appear at the incorrect time.
>
> As a result of this new law, PeopleCube will release Meeting Maker
> 8.6 specifically to address the upcoming change in DST. We have
> targeted a release date of October 2006 that should provide you with
> enough time to test and deploy this new release. It will require a
> full upgrade including both a database and client upgrade. To ensure
> continuous value of your Meeting Maker solution, we strongly recommend
> you prepare to upgrade your Meeting Maker installation to comply with this
new guideline.
>
> This new release will be made available for free to all Meeting Maker
> customers with an active maintenance contract via the PeopleCube
> Online Support Portal at http://connect.peoplecube.com/support/.
> If you have any questions or would like to inquire about joining our
> Maintenance Advantage Program, contact us at 1-800-282-7319 or
> ***@peoplecube.com. Our staff is available to assist you in any way
> possible.
>
> We will continue to provide updates to these changes through eNews,
> our quarterly electronic newsletter. If you are not currently
> subscribed to eNews but would like to start receiving it, simply send
> an email to ***@peoplecube.com with “Subscribeâ€? in the subject
line.
>
> From all of us here at PeopleCube, we thank you for your continued
support.
>
>
>
>
>
> 411 Waverley Oaks Road
> Waltham, MA 02452
> North America - 1 [phone] | Europe - 31 (0)20 777 2277
> www.peoplecube.com | ***@peoplecube.com
> 2006 PeopleCube | All rights reserved.
>
>
> All trademarks, service marks and product names mentioned herein are
> the property of PeopleCube or their respective owners.
>
> You are receiving this notice because you are currently listed as a
> PeopleCube customer. If this is in error, please contact us at
> ***@peoplecube.com.
>
>
>
> * MMXP-TALK Web Page:
> http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[Jack C Newton]

As most of Europe is used to country hopping with comes with moving from time
zone to time zone as well because your countries are located so close
together. Also the reason why most europeans speak 2-3 languages fluently
(yup, jealous of that).

But most companies in the US rarely need to use cross time zone scheduling
unless they have another branch in a different part of the US or another
country. Those companies will of course want to upgrade to 8.6.

-Jack Newton


From: Ian Eiloart <***@SUSSEX.AC.UK>
Date: 2006/09/13 Wed AM 04:50:38 CDT
To: MMXP-***@LISTSERV.EMORY.EDU
Subject: Re: Daylight Saving Time effects on 7.5

--On 12 September 2006 08:35:25 -0500 Jack C Newton
<***@VERIZON.NET> wrote:

> This issue will really only effect you if you cross time zones. So if all
> your users do not schedule outside of the same time zone, then you wilol
> not see an issue because your OS system clocks will change as they
> should for your local time zone and you will perceive no issues.

That's unlikely for a University. Here, we're all in the UK timezone, but I
still schedule across timezones for travel abroad, and for reminders of
events abroad.

For example, just yesterday, I switched my Display Time Zone to US Pacific
in order to add the schedule for Apple's media event. Last week, I took a
holiday in France, and used the Display Time Zone feature to schedule my
train and ferry journeys. Of course, the latter isn't going to be affected
by this update.

> Viewing or scheduling across time zones however will show one hour off
> until the normal previous daylight savings time dates pass.
>
> -Jack Newton
>
>
> From: Tim Gleason <***@HARVARD.EDU>
> Date: 2006/09/12 Tue AM 07:58:50 CDT
> To: MMXP-***@LISTSERV.EMORY.EDU
> Subject: Daylight Saving Time effects on 7.5
>
> <html xmlns:v="urn:schemas-microsoft-com:vml"
> xmlns:o="urn:schemas-microsoft- com:office:office"
> xmlns:w="urn:schemas-microsoft-com:office:word"
> xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://
> www.w3.org/TR/REC-html40">
>
> <head>
> <meta http-equiv=Content-Type content="text/html; charset=utf-8">
> <meta name=Generator content="Microsoft Word 11 (filtered medium)">
> <!--[if !mso]>
> <style>
> v\:* {behavior:url(#default#VML);}
> o\:* {behavior:url(#default#VML);}
> w\:* {behavior:url(#default#VML);}
> .shape {behavior:url(#default#VML);}
> </style>
> <![endif]--><o:SmartTagType
> namespaceuri="urn:schemas-microsoft-com:office:smarttags"
> name="PostalCode"/
>>
> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
> name="State"/>
> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
> name="City"/>
> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
> name="PlaceType"/>
> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
> name="PlaceName"/>
> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
> name="place"/>
> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
> name="Street"/>
> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
> name="address"/>
> <!--[if !mso]>
> <style>
> st1\:*{behavior:url(#default#ieooui) }
> </style>
> <![endif]-->
> <style>
> <!--
> /* Style Definitions */
> p.MsoNormal, li.MsoNormal, div.MsoNormal
> {margin:0in;
> margin-bottom:.0001pt;
> font-size:12.0pt;
> font-family:"Times New Roman";}
> a:link, span.MsoHyperlink
> {color:blue;
> text-decoration:underline;}
> a:visited, span.MsoHyperlinkFollowed
> {color:purple;
> text-decoration:underline;}
> span.EmailStyle17
> {mso-style-type:personal-compose;
> font-family:Arial;
> color:windowtext;}
> @page Section1
> {size:8.5in 11.0in;
> margin:1.0in 1.25in 1.0in 1.25in;}
> div.Section1
> {page:Section1;}
> -->
> </style>
> <!--[if gte mso 9]><xml>
> <o:shapedefaults v:ext="edit" spidmax="1026" />
> </xml><![endif]--><!--[if gte mso 9]><xml>
> <o:shapelayout v:ext="edit">
> <o:idmap v:ext="edit" data="1" />
> </o:shapelayout></xml><![endif]-->
> </head>
>
> <body lang=EN-US link=blue vlink=purple>
>
> <div class=Section1>
>
> <p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
> font-family:Arial'>We were caught by surprise with the recent email sent
> by PeopleCube regarding the changes to Daylight Savings Time (DST) and
> the effects
> on Meeting Maker.  We have an installation of version 7.5 supporting
> 2100 users
> which now appears we will be forced to upgrade to 8.6 once it is released
> in October.  I have attached the email to the end of this message in
> case you missed it.  This announcement comes at a bad time for us given
> may other projects we need to complete in the same timeframe.  Cost is
> the least of our worries since we are entitled to the upgrade under
> maintenance.  The ideal situation is deferring the upgrade so that we
> can ease the pain on our users and staff with changes to multiple
> applications.<o:p></o:p></span></font></p>
>
> <p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
> font-family:Arial'><o:p> </o:p></span></font></p>
>
> <p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
> font-family:Arial'>We are in the process of testing our current 7.5
> installation
> and the effects these DST changes.  Has anyone done similar tests and
> have some
> results they are willing to share?  Can the application be tricked by
> changing
> the clocks on the server or client, altering the time zone or a
> combination of
> both?  What impact will this have on the calendar and other clients like
> PDAs both on March 11 and the traditional April date?  I will send our
> results once
> they have been compiled.<o:p></o:p></span></font></p>
>
> <p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
> font-family:Arial'><o:p> </o:p></span></font></p>
>
> <p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
> font-family:Arial'>Regards<o:p></o:p></span></font></p>
>
> <p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
> font-family:Arial'><o:p> </o:p></span></font></p>
>
> <p class=MsoNormal><strong><b><font size=1 face=Arial><span
> style='font-size: 7.5pt;font-family:Arial'>Tim
> Gleason</span></font></b></strong><o:p></o:p></ p>
>
> <p class=MsoNormal><font size=1 face=Arial><span style='font-size:7.5pt;
> font-family:Arial'>Sr. Technical Architect</span></font><o:p></o:p></p>
>
> <p class=MsoNormal><font size=1 face=Arial><span style='font-size:7.5pt;
> font-family:Arial'>University Information
> Systems</span></font><o:p></o:p></ p>
>
> <p class=MsoNormal><st1:place w:st="on"><st1:PlaceName w:st="on"><font
> size=1 face=Arial><span
> style='font-size:7.5pt;font-family:Arial'>Harvard</span></
> font></st1:PlaceName><font
> size=1 face=Arial><span style='font-size:7.5pt;font-family:Arial'>
> <st1:PlaceType
> w:st="on">University</st1:PlaceType></span></font></st1:place><o:p></o:p
> ></ p>
>
> <p class=MsoNormal><font size=1 face=Arial><span style='font-size:7.5pt;
> font-family:Arial'>617.495.5811</span></font><o:p></o:p></p>
>
> <p class=MsoNormal><font size=1 face=Arial><span style='font-size:7.5pt;
> font-family:Arial'><a
> href="mailto:***@harvard.edu">***@harvard.edu</a></span></
> font><o:p></o:p></p>
>
> <p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-
> size:
> 12.0pt'><o:p> </o:p></span></font></p>
>
> <p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-
> size:
> 12.0pt'><o:p> </o:p></span></font></p>
>
> <p class=MsoNormal style='margin-bottom:12.0pt'><font size=3
> face="Times New Roman"><span style='font-size:12.0pt'>-------- Original
> Message
> -------- <br>
> Subject: Important Daylight Saving Time Information for Meeting Maker
> Users <br>
> Date: Wed, 23 Aug 2006 10:24:40 -0400 <br>
> From: PeopleCube <a href="mailto:***@peoplecube.com"
> title="mailto:***@peoplecube.com"><***@peoplecube.com></a>
> <br>
> <br>
> <br>
> <br>
> <img border=0 width=576 height=216 id="_x0000_i1025"
> src="HttpNimletDriver?
> nimlet=DownloadAttachmentNimlet&fileName=image001.jpg&folderName=INBOX&me
> ssag eID=50&partIndex=4&disposition=inline"
> alt=878e78e2.jpg></span></font><font size=2 face=Arial><span
> style='font-size:10.0pt;font-family:Arial'> <br> <br>
> Dear Meeting Maker User,<br>
> <br>
> Exciting things continue to happen within our Meeting Maker product line.
> However, it is important for us to communicate some very important
> information
> that will affect all of our Meeting Maker customers. In 2005, Congress
> passed the Energy Policy Act of 2005. A significant provision of the act
> extends daylight saving time (DST) by 4 weeks beginning in March of 2007.
> This change will obviously affect all Meeting Maker calendars, as any
> appointments or meetings scheduled during these four weeks will appear at
> the incorrect time. <br>
> <br>
> As a result of this new law, PeopleCube will release Meeting Maker 8.6
> specifically to address the upcoming change in DST. We have targeted a
> release
> date of October 2006 that should provide you with enough time to test and
> deploy this new release. It will require a full upgrade including both a
> database
> and client upgrade. To ensure continuous value of your Meeting Maker
> solution,
> we strongly recommend you prepare to upgrade your Meeting Maker
> installation to
> comply with this new guideline. <br>
> <br>
> This new release will be made available for free to all Meeting Maker
> customers
> with an active maintenance contract via the PeopleCube Online Support
> Portal at
> <a href="http://connect.peoplecube.com/support/"
> title="http://connect.peoplecube.com/support/">http://connect.peoplecube.
> com/ support/</a>.
> If you have any questions or would like to inquire about joining our
> Maintenance Advantage Program, contact us at 1-800-282-7319 or <a
> href="mailto:***@peoplecube.com"
> title="mailto:***@peoplecube.com">***@peoplecube.com</a>.
> Our staff is available to assist you in any way possible. <br>
> <br>
> We will continue to provide updates to these changes through eNews, our
> quarterly electronic newsletter. If you are not currently subscribed to
> eNews but would like to start receiving it, simply send an email to <a
> href="mailto:***@peoplecube.com?Subject=Subscribe%20to%20eNews"
> title="mailto:***@peoplecube.com?Subject=Subscribe to
> eNews">***@peoplecube.com</a>
> with “Subscribeâ€? in the subject line.<br>
> <br>
>> From all of us here at PeopleCube, we thank you for your continued
> support.<br>
> <br>
> <img border=0 width=576 height=41 id="_x0000_i1026"
> src="HttpNimletDriver?
> nimlet=DownloadAttachmentNimlet&fileName=image002.jpg&folderName=INBOX&me
> ssag eID=50&partIndex=3&disposition=inline" alt=878e78f2.jpg><br>
> <img border=0 width=600 height=5 id="_x0000_i1027"
> src="HttpNimletDriver?
> nimlet=DownloadAttachmentNimlet&fileName=image003.jpg&folderName=INBOX&me
> ssag eID=50&partIndex=2&disposition=inline"
> alt=878e7911.jpg> <o:p></o:p></span></ font></p>
>
> <p class=MsoNormal align=center style='text-align:center'><font size=2
> face=Arial><span style='font-size:10.0pt;font-family:Arial'><img border=0
> width=98 height=43 id="_x0000_i1028" src="HttpNimletDriver?
> nimlet=DownloadAttachmentNimlet&fileName=image004.jpg&folderName=INBOX&me
> ssag eID=50&partIndex=1&disposition=inline"
> alt=878e7930.jpg><br>
> 411 <st1:City w:st="on"><st1:place
> w:st="on">Waverley</st1:place></st1:City> <st1:Street
> w:st="on"><st1:address w:st="on">Oaks Road</st1:address></st1:Street><br>
> <st1:place w:st="on"><st1:City w:st="on">Waltham</st1:City>, <st1:State
> w:st="on">MA</st1:State>
> <st1:PostalCode w:st="on">02452</st1:PostalCode></st1:place><br>
> North America - 1 [phone] | <st1:place
> w:st="on">Europe</st1:place> - 31
> (0)20 777 2277<br>
> <a href="http://www.peoplecube.com" title="http://
> www.peoplecube.com">www.peoplecube.com</a>
>| <a href="mailto:***@peoplecube.com"
> title="mailto:***@peoplecube.com">***@peoplecube.com</a><br>
> 2006 PeopleCube | All rights reserved.<o:p></o:p></span></font></p>
>
> <p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
> font-family:Arial'><br>
> All trademarks, service marks and product names mentioned herein are the
> property of PeopleCube or their respective owners. <br>
> <br>
> You are receiving this notice because you are currently listed as a
> PeopleCube
> customer. If this is in error, please contact us at <a
> href="mailto:***@peoplecube.com"
> title="mailto:***@peoplecube.com">***@peoplecube.com</a>.
> <br>
> <br>
> </span></font><o:p></o:p></p>
>
> </div>
>
> </body>
>
> </html>
> <p>
> * MMXP-TALK Web Page:
> http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML
>
>
> * MMXP-TALK Web Page:
> http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML



--
Ian Eiloart
IT Services, University of Sussex


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[Ian Eiloart]

--On 13 September 2006 07:33:51 -0500 Jack C Newton
<***@VERIZON.NET> wrote:

> As most of Europe is used to country hopping with comes with moving from
> time zone to time zone as well because your countries are located so
> close together.

The first 12 EU nations had 2 time zones, with UK, Eire and Portugal in
one, and the rest in the second. The EU standardises daylight savings start
and end times, I suspect. Even adding Greece, Romania (and eventually
Turkey) we still have just three time zones.

I see four in the mainland US, and I know there are complications with some
not observing daylight savings.

> Also the reason why most europeans speak 2-3 languages
> fluently (yup, jealous of that).

Ha, that's a myth. Bits of 2-3 languages, maybe. Generally native speakers
of minority languages like Dutch and Danish do speak English pretty well.
Scandinavians do pretty well, too. In France, Germany and Spain it's quite
a different story.

> But most companies in the US rarely need to use cross time zone
> scheduling unless they have another branch in a different part of the US
> or another country. Those companies will of course want to upgrade to
> 8.6.

They won't want to because a major upgrade is a major PITA. They will have
to, of course. Or, they'll figure that switching to something standards
compliant will stop these problems.

> -Jack Newton
>
>
> From: Ian Eiloart <***@SUSSEX.AC.UK>
> Date: 2006/09/13 Wed AM 04:50:38 CDT
> To: MMXP-***@LISTSERV.EMORY.EDU
> Subject: Re: Daylight Saving Time effects on 7.5
>
> --On 12 September 2006 08:35:25 -0500 Jack C Newton
> <***@VERIZON.NET> wrote:
>
>> This issue will really only effect you if you cross time zones. So if all
>> your users do not schedule outside of the same time zone, then you wilol
>> not see an issue because your OS system clocks will change as they
>> should for your local time zone and you will perceive no issues.
>
> That's unlikely for a University. Here, we're all in the UK timezone, but
> I still schedule across timezones for travel abroad, and for reminders
> of events abroad.
>
> For example, just yesterday, I switched my Display Time Zone to US
> Pacific in order to add the schedule for Apple's media event. Last week,
> I took a holiday in France, and used the Display Time Zone feature to
> schedule my train and ferry journeys. Of course, the latter isn't going
> to be affected by this update.
>
>> Viewing or scheduling across time zones however will show one hour off
>> until the normal previous daylight savings time dates pass.
>>
>> -Jack Newton
>>
>>
>> From: Tim Gleason <***@HARVARD.EDU>
>> Date: 2006/09/12 Tue AM 07:58:50 CDT
>> To: MMXP-***@LISTSERV.EMORY.EDU
>> Subject: Daylight Saving Time effects on 7.5
>>
>> <html xmlns:v="urn:schemas-microsoft-com:vml"
>> xmlns:o="urn:schemas-microsoft- com:office:office"
>> xmlns:w="urn:schemas-microsoft-com:office:word"
>> xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://
>> www.w3.org/TR/REC-html40">
>>
>> <head>
>> <meta http-equiv=Content-Type content="text/html; charset=utf-8">
>> <meta name=Generator content="Microsoft Word 11 (filtered medium)">
>> <!--[if !mso]>
>> <style>
>> v\:* {behavior:url(#default#VML);}
>> o\:* {behavior:url(#default#VML);}
>> w\:* {behavior:url(#default#VML);}
>> .shape {behavior:url(#default#VML);}
>> </style>
>> <![endif]--><o:SmartTagType
>> namespaceuri="urn:schemas-microsoft-com:office:smarttags"
>> name="PostalCode"/
>>>
>> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
>> name="State"/>
>> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
>> name="City"/>
>> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
>> name="PlaceType"/>
>> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
>> name="PlaceName"/>
>> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
>> name="place"/>
>> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
>> name="Street"/>
>> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
>> name="address"/>
>> <!--[if !mso]>
>> <style>
>> st1\:*{behavior:url(#default#ieooui) }
>> </style>
>> <![endif]-->
>> <style>
>> <!--
>> /* Style Definitions */
>> p.MsoNormal, li.MsoNormal, div.MsoNormal
>> {margin:0in;
>> margin-bottom:.0001pt;
>> font-size:12.0pt;
>> font-family:"Times New Roman";}
>> a:link, span.MsoHyperlink
>> {color:blue;
>> text-decoration:underline;}
>> a:visited, span.MsoHyperlinkFollowed
>> {color:purple;
>> text-decoration:underline;}
>> span.EmailStyle17
>> {mso-style-type:personal-compose;
>> font-family:Arial;
>> color:windowtext;}
>> @page Section1
>> {size:8.5in 11.0in;
>> margin:1.0in 1.25in 1.0in 1.25in;}
>> div.Section1
>> {page:Section1;}
>> -->
>> </style>
>> <!--[if gte mso 9]><xml>
>> <o:shapedefaults v:ext="edit" spidmax="1026" />
>> </xml><![endif]--><!--[if gte mso 9]><xml>
>> <o:shapelayout v:ext="edit">
>> <o:idmap v:ext="edit" data="1" />
>> </o:shapelayout></xml><![endif]-->
>> </head>
>>
>> <body lang=EN-US link=blue vlink=purple>
>>
>> <div class=Section1>
>>
>> <p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
>> font-family:Arial'>We were caught by surprise with the recent email sent
>> by PeopleCube regarding the changes to Daylight Savings Time (DST) and
>> the effects
>> on Meeting Maker.  We have an installation of version 7.5 supporting
>> 2100 users
>> which now appears we will be forced to upgrade to 8.6 once it is released
>> in October.  I have attached the email to the end of this message in
>> case you missed it.  This announcement comes at a bad time for us given
>> may other projects we need to complete in the same timeframe.  Cost is
>> the least of our worries since we are entitled to the upgrade under
>> maintenance.  The ideal situation is deferring the upgrade so that we
>> can ease the pain on our users and staff with changes to multiple
>> applications.<o:p></o:p></span></font></p>
>>
>> <p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
>> font-family:Arial'><o:p> </o:p></span></font></p>
>>
>> <p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
>> font-family:Arial'>We are in the process of testing our current 7.5
>> installation
>> and the effects these DST changes.  Has anyone done similar tests and
>> have some
>> results they are willing to share?  Can the application be tricked by
>> changing
>> the clocks on the server or client, altering the time zone or a
>> combination of
>> both?  What impact will this have on the calendar and other clients like
>> PDAs both on March 11 and the traditional April date?  I will send our
>> results once
>> they have been compiled.<o:p></o:p></span></font></p>
>>
>> <p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
>> font-family:Arial'><o:p> </o:p></span></font></p>
>>
>> <p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
>> font-family:Arial'>Regards<o:p></o:p></span></font></p>
>>
>> <p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
>> font-family:Arial'><o:p> </o:p></span></font></p>
>>
>> <p class=MsoNormal><strong><b><font size=1 face=Arial><span
>> style='font-size: 7.5pt;font-family:Arial'>Tim
>> Gleason</span></font></b></strong><o:p></o:p></ p>
>>
>> <p class=MsoNormal><font size=1 face=Arial><span style='font-size:7.5pt;
>> font-family:Arial'>Sr. Technical Architect</span></font><o:p></o:p></p>
>>
>> <p class=MsoNormal><font size=1 face=Arial><span style='font-size:7.5pt;
>> font-family:Arial'>University Information
>> Systems</span></font><o:p></o:p></ p>
>>
>> <p class=MsoNormal><st1:place w:st="on"><st1:PlaceName w:st="on"><font
>> size=1 face=Arial><span
>> style='font-size:7.5pt;font-family:Arial'>Harvard</span></
>> font></st1:PlaceName><font
>> size=1 face=Arial><span style='font-size:7.5pt;font-family:Arial'>
>> <st1:PlaceType
>> w:st="on">University</st1:PlaceType></span></font></st1:place><o:p></o:p
>> > </ p>
>>
>> <p class=MsoNormal><font size=1 face=Arial><span style='font-size:7.5pt;
>> font-family:Arial'>617.495.5811</span></font><o:p></o:p></p>
>>
>> <p class=MsoNormal><font size=1 face=Arial><span style='font-size:7.5pt;
>> font-family:Arial'><a
>> href="mailto:***@harvard.edu">***@harvard.edu</a></span>
>> </ font><o:p></o:p></p>
>>
>> <p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-
>> size:
>> 12.0pt'><o:p> </o:p></span></font></p>
>>
>> <p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-
>> size:
>> 12.0pt'><o:p> </o:p></span></font></p>
>>
>> <p class=MsoNormal style='margin-bottom:12.0pt'><font size=3
>> face="Times New Roman"><span style='font-size:12.0pt'>-------- Original
>> Message
>> -------- <br>
>> Subject: Important Daylight Saving Time Information for Meeting Maker
>> Users <br>
>> Date: Wed, 23 Aug 2006 10:24:40 -0400 <br>
>> From: PeopleCube <a href="mailto:***@peoplecube.com"
>> title="mailto:***@peoplecube.com"><***@peoplecube.com></
>> a> <br>
>> <br>
>> <br>
>> <br>
>> <img border=0 width=576 height=216 id="_x0000_i1025"
>> src="HttpNimletDriver?
>> nimlet=DownloadAttachmentNimlet&fileName=image001.jpg&folderName=INBOX&me
>> ssag eID=50&partIndex=4&disposition=inline"
>> alt=878e78e2.jpg></span></font><font size=2 face=Arial><span
>> style='font-size:10.0pt;font-family:Arial'> <br> <br>
>> Dear Meeting Maker User,<br>
>> <br>
>> Exciting things continue to happen within our Meeting Maker product line.
>> However, it is important for us to communicate some very important
>> information
>> that will affect all of our Meeting Maker customers. In 2005, Congress
>> passed the Energy Policy Act of 2005. A significant provision of the act
>> extends daylight saving time (DST) by 4 weeks beginning in March of 2007.
>> This change will obviously affect all Meeting Maker calendars, as any
>> appointments or meetings scheduled during these four weeks will appear at
>> the incorrect time. <br>
>> <br>
>> As a result of this new law, PeopleCube will release Meeting Maker 8.6
>> specifically to address the upcoming change in DST. We have targeted a
>> release
>> date of October 2006 that should provide you with enough time to test and
>> deploy this new release. It will require a full upgrade including both a
>> database
>> and client upgrade. To ensure continuous value of your Meeting Maker
>> solution,
>> we strongly recommend you prepare to upgrade your Meeting Maker
>> installation to
>> comply with this new guideline. <br>
>> <br>
>> This new release will be made available for free to all Meeting Maker
>> customers
>> with an active maintenance contract via the PeopleCube Online Support
>> Portal at
>> <a href="http://connect.peoplecube.com/support/"
>> title="http://connect.peoplecube.com/support/">http://connect.peoplecube.
>> com/ support/</a>.
>> If you have any questions or would like to inquire about joining our
>> Maintenance Advantage Program, contact us at 1-800-282-7319 or <a
>> href="mailto:***@peoplecube.com"
>> title="mailto:***@peoplecube.com">***@peoplecube.com</a>.
>> Our staff is available to assist you in any way possible. <br>
>> <br>
>> We will continue to provide updates to these changes through eNews, our
>> quarterly electronic newsletter. If you are not currently subscribed to
>> eNews but would like to start receiving it, simply send an email to <a
>> href="mailto:***@peoplecube.com?Subject=Subscribe%20to%20eNews"
>> title="mailto:***@peoplecube.com?Subject=Subscribe to
>> eNews">***@peoplecube.com</a>
>> with “Subscribe� in the subject line.<br>
>> <br>
>>> From all of us here at PeopleCube, we thank you for your continued
>> support.<br>
>> <br>
>> <img border=0 width=576 height=41 id="_x0000_i1026"
>> src="HttpNimletDriver?
>> nimlet=DownloadAttachmentNimlet&fileName=image002.jpg&folderName=INBOX&me
>> ssag eID=50&partIndex=3&disposition=inline" alt=878e78f2.jpg><br>
>> <img border=0 width=600 height=5 id="_x0000_i1027"
>> src="HttpNimletDriver?
>> nimlet=DownloadAttachmentNimlet&fileName=image003.jpg&folderName=INBOX&me
>> ssag eID=50&partIndex=2&disposition=inline"
>> alt=878e7911.jpg> <o:p></o:p></span></ font></p>
>>
>> <p class=MsoNormal align=center style='text-align:center'><font size=2
>> face=Arial><span style='font-size:10.0pt;font-family:Arial'><img border=0
>> width=98 height=43 id="_x0000_i1028" src="HttpNimletDriver?
>> nimlet=DownloadAttachmentNimlet&fileName=image004.jpg&folderName=INBOX&me
>> ssag eID=50&partIndex=1&disposition=inline"
>> alt=878e7930.jpg><br>
>> 411 <st1:City w:st="on"><st1:place
>> w:st="on">Waverley</st1:place></st1:City> <st1:Street
>> w:st="on"><st1:address w:st="on">Oaks Road</st1:address></st1:Street><br>
>> <st1:place w:st="on"><st1:City w:st="on">Waltham</st1:City>, <st1:State
>> w:st="on">MA</st1:State>
>> <st1:PostalCode w:st="on">02452</st1:PostalCode></st1:place><br>
>> North America - 1 [phone] | <st1:place
>> w:st="on">Europe</st1:place> - 31
>> (0)20 777 2277<br>
>> <a href="http://www.peoplecube.com" title="http://
>> www.peoplecube.com">www.peoplecube.com</a>
>>| <a href="mailto:***@peoplecube.com"
>> title="mailto:***@peoplecube.com">***@peoplecube.com</a><br>
>> 2006 PeopleCube | All rights reserved.<o:p></o:p></span></font></p>
>>
>> <p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
>> font-family:Arial'><br>
>> All trademarks, service marks and product names mentioned herein are the
>> property of PeopleCube or their respective owners. <br>
>> <br>
>> You are receiving this notice because you are currently listed as a
>> PeopleCube
>> customer. If this is in error, please contact us at <a
>> href="mailto:***@peoplecube.com"
>> title="mailto:***@peoplecube.com">***@peoplecube.com</a>.
>> <br>
>> <br>
>> </span></font><o:p></o:p></p>
>>
>> </div>
>>
>> </body>
>>
>> </html>
>> <p>
>> * MMXP-TALK Web Page:
>> http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML
>>
>>
>> * MMXP-TALK Web Page:
>> http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML



--
Ian Eiloart
IT Services, University of Sussex


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[Jack C Newton]

Oracle? The whole idea of Meeting Maker for us is a LOW COST solution (that
isn't pront to viruses or hacking). I wouldn't call Oracle cheap....and I've
had nightmare with their support unless you are one large company/customer.
Of course many Universities can get around that as they get special pricing
if they're large enough.

-Jack Newton


From: Chris Colebank <***@SONOMA.EDU>
Date: 2006/09/12 Tue AM 09:44:42 CDT
To: MMXP-***@LISTSERV.EMORY.EDU
Subject: Re: Daylight Saving Time effects on 7.5

Kyle,

You say you will be migrating to Oracle Calendar. Have you found a
tool to migrate all the user calendars from Meeting Maker for import
into another application? Or will you be 'starting over' in the new
application, as in recreating all the users in the new application
without their schedules.

thanks, Chris

Kyle Johnson wrote:
> On 9/12/06 at 9:20 AM, Erik Froese wrote:
>
>> I have to say I'm completely fed up with Meeting Maker as a product.
>> Is there anything that supports handheld devices as well as Meeting
>> Maker does without putting all of our eggs in Outlook's basket?
>>
>
> Duke recently went to Oracle Calendar centrally. We'll be migrating our
> Meeting Maker installation to that sometime this year. It appears to
> have very good mobile support and doesn't require you to swallow the
> Microsoft koolaid to use it. '-)
>
> /kyle
> ---
> Kyle Johnson : Director, Information Technology Services
> Duke University Student Affairs
> ***@duke.edu : http://www.studentaffairs.duke.edu
> jabber- ***@jabber.duke.edu : aim- dukekej
> -----------------------------------------------------------------------
> Do you have change for a paradigm?
>
>
> * MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-
TALK.HTML
>


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[Max Legault]

PeopleCube strongly recommends not editing the Meeting Maker time zone
files. This database is encoded for security like other Meeting Maker
databases. Experimenting with these files could result in database
corruption. Please be aware that any corruption due to modifying this fil
e
invalidates a company's support contract.

Changes to daylight saving time have been made in the past. A similar
change to Daylight Saving Time was passed
for the 1974-1975 time frame. This change was repealed after 1975 (possi
bly
due to a spike in school bus accidents due to much darker mornings).

We believe Meeting Maker's 8.6 time zone modifications are, to our
knowledge, the most thorough in the industry. It is our
understanding that other manufacturers are going to provide a mass time z
one
definition update during the winter
and leave the job of fixing data corruption to the users.

Meeting Maker 8.6 will provide a tool that will fix such data corruption
automatically. Further, customers will be able to adapt to any future ti
me
zone changes (including the potential repeal of the 2007 DST changes) by
simply downloading a new time zone file and running the new tool.

_________________________________________
Max Legault
Senior Technical Support Engineer

PeopleCube
411 Waverly Oaks Road, Suite 310
Waltham, MA 02452



* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[Craft, Robert]

Which does nothing to address the 7.5 issue.

After being told by MM support that the 8.5 release was "functioning as intended" with our problem, I see NO reason to even suggest upgrading to 8.6


-----Original Message-----
From: Meeting Maker Discussion List on behalf of Max Legault
Sent: Tue 9/19/2006 11:52 AM
To: MMXP-***@LISTSERV.EMORY.EDU
Subject: Re: Daylight Saving Time effects on 7.5

PeopleCube strongly recommends not editing the Meeting Maker time zone
files. This database is encoded for security like other Meeting Maker
databases. Experimenting with these files could result in database
corruption. Please be aware that any corruption due to modifying this file
invalidates a company's support contract.

Changes to daylight saving time have been made in the past. A similar
change to Daylight Saving Time was passed
for the 1974-1975 time frame. This change was repealed after 1975 (possibly
due to a spike in school bus accidents due to much darker mornings).

We believe Meeting Maker's 8.6 time zone modifications are, to our
knowledge, the most thorough in the industry. It is our
understanding that other manufacturers are going to provide a mass time zone
definition update during the winter
and leave the job of fixing data corruption to the users.

Meeting Maker 8.6 will provide a tool that will fix such data corruption
automatically. Further, customers will be able to adapt to any future time
zone changes (including the potential repeal of the 2007 DST changes) by
simply downloading a new time zone file and running the new tool.

_________________________________________
Max Legault
Senior Technical Support Engineer

PeopleCube
411 Waverly Oaks Road, Suite 310
Waltham, MA 02452



* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML


*******************************************
Confidentiality Notice: This e-mail message, including any attachments, from AtlantiCare contains information which is CONFIDENTIAL AND/OR LEGALLY PRIVILEGED.
The information is intended only for the use of the individual named above and may not be disseminated to any other party without AtlantiCare's written permission.
If you are not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination,
disclosure, distribution, copying or taking of any action in reliance on the contents of this e-mailed information is strictly prohibited.
If you have received this e-mail in error, please notify us immediately by telephone at 609-569-7070 or notify us by e-mail at ***@Atlanticare.org
to arrange for the return of these documents to us without cost to you.



* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[Matthew Keller]

On Tue, 2006-09-19 at 11:52 -0400, Max Legault wrote:
> PeopleCube strongly recommends not editing the Meeting Maker time zone
> files. This database is encoded for security like other Meeting Maker
> databases. Experimenting with these files could result in database
> corruption. Please be aware that any corruption due to modifying this file
> invalidates a company's support contract.

Then perhaps PeopleCube should release a new time zone database for the
7.x series instead of needlessly forcing us to upgrade. We pay annual
maintenance and as such can do so for "free", however as we have seen
with EVERY MeetingMaker upgrade, "free" is quite expensive in terms of
locally spent manhours.

Said differently: 7.5 is working wonderfully fine and we have no
interest in upgrading. Release one stupid file that you KNOW you could
trivially update, please.

--
Matthew Keller
Enterprise Systems Analyst
Computing & Technology Services
State University of New York @ Potsdam
Potsdam, NY, USA
http://mattwork.potsdam.edu/


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[jonesey]

Max -

Thank you for the explanation. It is really great that
representatives from PeopleCube read this mailing list; it shows a
dedication to customer support that is rare among software companies
these days.

Please release a time zone / DST patch for 7.5. Our school does
not have the resources or the need to upgrade to 8.5 or 8.6 at this
time.

Chris Jones
University of Oregon


At 11:52 -0400 9/19/06, Max Legault wrote:
>PeopleCube strongly recommends not editing the Meeting Maker time zone
>files. This database is encoded for security like other Meeting Maker
>databases. Experimenting with these files could result in database
>corruption. Please be aware that any corruption due to modifying this file
>invalidates a company's support contract.
>
>Changes to daylight saving time have been made in the past. A similar
>change to Daylight Saving Time was passed
>for the 1974-1975 time frame. This change was repealed after 1975 (possibly
>due to a spike in school bus accidents due to much darker mornings).
>
>We believe Meeting Maker's 8.6 time zone modifications are, to our
>knowledge, the most thorough in the industry. It is our
>understanding that other manufacturers are going to provide a mass time zone
>definition update during the winter
>and leave the job of fixing data corruption to the users.
>
>Meeting Maker 8.6 will provide a tool that will fix such data corruption
>automatically. Further, customers will be able to adapt to any future time
>zone changes (including the potential repeal of the 2007 DST changes) by
>simply downloading a new time zone file and running the new tool.
>
>_________________________________________
>Max Legault
>Senior Technical Support Engineer
>
>PeopleCube
>411 Waverly Oaks Road, Suite 310
>Waltham, MA 02452
>
>
>
>* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[Stuenkel, MaryBeth]

Max,

I would like to echo Chris' sentiments. We appreciate your responses to
the list and we also do not have the resources or the need to upgrade to
8.5 or 8.6. Please release a patch for 7.5.

--MaryBeth Stuenkel

> -----Original Message-----
> From: Meeting Maker Discussion List
[mailto:MMXP-***@LISTSERV.EMORY.EDU]
> On Behalf Of jonesey
> Sent: Tuesday, September 19, 2006 4:50 PM
> To: MMXP-***@LISTSERV.EMORY.EDU
> Subject: Re: Daylight Saving Time effects on 7.5
>
> Max -
>
> Thank you for the explanation. It is really great that
> representatives from PeopleCube read this mailing list; it shows a
> dedication to customer support that is rare among software companies
> these days.
>
> Please release a time zone / DST patch for 7.5. Our school does
> not have the resources or the need to upgrade to 8.5 or 8.6 at this
> time.
>
> Chris Jones
> University of Oregon
>
>
> At 11:52 -0400 9/19/06, Max Legault wrote:
> >PeopleCube strongly recommends not editing the Meeting Maker time
zone
> >files. This database is encoded for security like other Meeting Maker
> >databases. Experimenting with these files could result in database
> >corruption. Please be aware that any corruption due to modifying this
> file
> >invalidates a company's support contract.
> >
> >Changes to daylight saving time have been made in the past. A
similar
> >change to Daylight Saving Time was passed
> >for the 1974-1975 time frame. This change was repealed after 1975
> (possibly
> >due to a spike in school bus accidents due to much darker mornings).
> >
> >We believe Meeting Maker's 8.6 time zone modifications are, to our
> >knowledge, the most thorough in the industry. It is our
> >understanding that other manufacturers are going to provide a mass
time
> zone
> >definition update during the winter
> >and leave the job of fixing data corruption to the users.
> >
> >Meeting Maker 8.6 will provide a tool that will fix such data
corruption
> >automatically. Further, customers will be able to adapt to any
future
> time
> >zone changes (including the potential repeal of the 2007 DST changes)
by
> >simply downloading a new time zone file and running the new tool.
> >
> >_________________________________________
> >Max Legault
> >Senior Technical Support Engineer
> >
> >PeopleCube
> >411 Waverly Oaks Road, Suite 310
> >Waltham, MA 02452
> >
> >
> >
> >* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-
> TALK.HTML
>
>
> * MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-
> TALK.HTML


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[Ian Eiloart]

--On 19 September 2006 13:49:43 -0700 jonesey <***@UOREGON.EDU> wrote:

> Max -
>
> Thank you for the explanation. It is really great that
> representatives from PeopleCube read this mailing list; it shows a
> dedication to customer support that is rare among software companies
> these days.

Rare among companies, but commonplace among open source projects.

> Please release a time zone / DST patch for 7.5. Our school does not
> have the resources or the need to upgrade to 8.5 or 8.6 at this time.
>
> Chris Jones
> University of Oregon
>
>
> At 11:52 -0400 9/19/06, Max Legault wrote:
>> PeopleCube strongly recommends not editing the Meeting Maker time zone
>> files. This database is encoded for security like other Meeting Maker
>> databases. Experimenting with these files could result in database
>> corruption. Please be aware that any corruption due to modifying this
>> file invalidates a company's support contract.
>>
>> Changes to daylight saving time have been made in the past. A similar
>> change to Daylight Saving Time was passed
>> for the 1974-1975 time frame. This change was repealed after 1975
>> (possibly due to a spike in school bus accidents due to much darker
>> mornings).
>>
>> We believe Meeting Maker's 8.6 time zone modifications are, to our
>> knowledge, the most thorough in the industry. It is our
>> understanding that other manufacturers are going to provide a mass time
>> zone definition update during the winter
>> and leave the job of fixing data corruption to the users.
>>
>> Meeting Maker 8.6 will provide a tool that will fix such data corruption
>> automatically. Further, customers will be able to adapt to any future
>> time zone changes (including the potential repeal of the 2007 DST
>> changes) by simply downloading a new time zone file and running the new
>> tool.
>>
>> _________________________________________
>> Max Legault
>> Senior Technical Support Engineer
>>
>> PeopleCube
>> 411 Waverly Oaks Road, Suite 310
>> Waltham, MA 02452
>>
>>
>>
>> * MMXP-TALK Web Page:
>> http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML
>
>
> * MMXP-TALK Web Page:
> http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML



--
Ian Eiloart
IT Services, University of Sussex


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[J.Lance Wilkinson]

At 05:34 PM 9/19/2006 -0400, you wrote:
>Max,
>
>I would like to echo Chris' sentiments. We appreciate your responses to
>the list and we also do not have the resources or the need to upgrade to
>8.5 or 8.6. Please release a patch for 7.5.
>
>--MaryBeth Stuenkel

Hi, MaryBeth!

At Penn State's University Libraries, we did the "upgrade"
from v7.5 to v8.5 back in June 2005. It
was without a doubt the worst "upgrade" I have ever been
involved with in my 30+ years in the Data
Processing business.

If it weren't for the fact that the databases could not be
rolled back (which our CIO could NOT believe! and
in hindsight I have to admit is something that should have
been considered, but it had NEVER been this
bad before in all my upgrades since starting w/ MM
v2.3), we would have moved back to v7.5 within 3
days of completing the upgrade (we did it on a Thursday
night/Friday morning, and by Monday there was
not a single user really happy with it).

We run a MM hub on the same Win2K server (since upgraded to
Win2003) as two MM servers, and then
two other organizations on campus run their own MM servers
connecting to our hub. Needless to say,
coordinating the shift of more than 500 users on this campus
and 23 other campuses BACK to v7.5, along
with loss of data from the weekend of v8.5 use, was the
primary factor in our choosing to stick it out.

MM v8.5 (and v8.x before it, apparently) is a COMPLETE
REWRITE from v7.5, MM tech support folks
explained to me. The interface is totally different,
clearly an attempt to lure MS Outlook users to MM,
but no effort to retain the look/feel of the prior MM
product our users were used to. For us, memory leaks
were the biggest problem, followed quickly by the culture
shock of the extreme DIFFERENCE between
v7.5's interface and v8.5's and other "philosophical"
changes which affected smaller clusters of users
adversely.

It took well into NOVEMBER to resolve the memory leaks,
including having MM DEVELOPERS spend
literally hours on the phone talking with individual power
users trying to figure out what was going wrong.
Said users had to share their MM passwords with the
developer so the developer could log in AS THEM
to see firsthand what was wrong.

In many respects the problems were caused by the simple fact
that we use the product differently than the
vendor had EVER conceived it to be used; users with more
than 20 read/write proxies open simultaneously
is not uncommon here, and worked just fine under v7.5 but
crashed and burned [or rather simply hung]
miserably under v8.5). Another whole organization (one of
those groups with their own server connecting
to our hub) used to use read proxies EXCLUSIVELY to
determine availability -- they never even knew that
you could PROPOSE meetings between individuals until they
learned that from us. So the usage patterns
which v7.5 allowed, which were prevented by the rewritten
code in v8.5, were the biggest culprit. Had we
upgraded to v8.0 when it first came out, we might have been
prepared for a lot of these issues. Hindsight,
you know the rest.

So it's not just not having the need or resources to move to
v8.5 or v8.6 that should be preventing you from
upgrading to it. You should seriously consider if DST is
important or not (from my years '76-'86 at Grand
Valley State there in Michigan, I doubt that it's
*really* that important ;-P) and avoid moving to v8.x like
the plague. It certainly is NOT a better product than v7.5 was.


"Never Underestimate the bandwidth of a station wagon full
of mag tapes"
J.Lance Wilkinson
("Lance") InterNet: ***@psu.edu
Systems Design Specialist -
Lead AT&T: [phone]
Digital Library
Technologies FAX: [phone]
E3 Paterno Library "I'd rather
be dancing..."
Penn State University A host is a host
from coast to coast,
University Park, PA 16802 And no one will talk
to a host that's close
<***@psulias.psu.edu> Unless the host that
isn't close
EMail Professional since 1978 Is busy, hung or dead.
"He's dead, Jim. I'll get his tricorder. You take his wallet."
[apologies to DeForest Kelley, 1920-1999]
<A Href="http://perdita.lcs.psu.edu">home page</a>
<a Href="http://perdita.lcs.psu.edu/junkdec.htm">junk mail
declaration</a>
--
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[Jack C Newton]

Well let's face it, the inerface was real old and people were complaining
about that too (looked simplistic to me). At some point they had to design a
new interface but ended up adding a "Classic View" option to help ease the
transition. So people who didn't want the new interface would hate them and
people who did would hate them if they didn't change it. Damned if you do,
damned if you don't....

I guess my question is, didn't you test before you upgraded? As an IT manager
I would never upgrade an enterprise application without doing at least a
modicum of testing....especially if so many people depended on it. It's
obvious the interface is completely different as soon as you sign on to the
client and use the basic functions.

Now that certainly doesn't excuse the bugs they has on release but we make it
a policy to not go to a first version of a release of any enterprise software
unless we're sure it's really solid.

Jack Newton


From: "J.Lance Wilkinson" <***@PSULIAS.PSU.EDU>
Date: 2006/09/21 Thu AM 08:19:04 CDT
To: MMXP-***@LISTSERV.EMORY.EDU
Subject: Re: Daylight Saving Time effects on 7.5

At 05:34 PM 9/19/2006 -0400, you wrote:
>Max,
>
>I would like to echo Chris' sentiments. We appreciate your responses to
>the list and we also do not have the resources or the need to upgrade to
>8.5 or 8.6. Please release a patch for 7.5.
>
>--MaryBeth Stuenkel

Hi, MaryBeth!

At Penn State's University Libraries, we did the "upgrade"
from v7.5 to v8.5 back in June 2005. It
was without a doubt the worst "upgrade" I have ever been
involved with in my 30+ years in the Data
Processing business.

If it weren't for the fact that the databases could not be
rolled back (which our CIO could NOT believe! and
in hindsight I have to admit is something that should have
been considered, but it had NEVER been this
bad before in all my upgrades since starting w/ MM
v2.3), we would have moved back to v7.5 within 3
days of completing the upgrade (we did it on a Thursday
night/Friday morning, and by Monday there was
not a single user really happy with it).

We run a MM hub on the same Win2K server (since upgraded to
Win2003) as two MM servers, and then
two other organizations on campus run their own MM servers
connecting to our hub. Needless to say,
coordinating the shift of more than 500 users on this campus
and 23 other campuses BACK to v7.5, along
with loss of data from the weekend of v8.5 use, was the
primary factor in our choosing to stick it out.

MM v8.5 (and v8.x before it, apparently) is a COMPLETE
REWRITE from v7.5, MM tech support folks
explained to me. The interface is totally different,
clearly an attempt to lure MS Outlook users to MM,
but no effort to retain the look/feel of the prior MM
product our users were used to. For us, memory leaks
were the biggest problem, followed quickly by the culture
shock of the extreme DIFFERENCE between
v7.5's interface and v8.5's and other "philosophical"
changes which affected smaller clusters of users
adversely.

It took well into NOVEMBER to resolve the memory leaks,
including having MM DEVELOPERS spend
literally hours on the phone talking with individual power
users trying to figure out what was going wrong.
Said users had to share their MM passwords with the
developer so the developer could log in AS THEM
to see firsthand what was wrong.

In many respects the problems were caused by the simple fact
that we use the product differently than the
vendor had EVER conceived it to be used; users with more
than 20 read/write proxies open simultaneously
is not uncommon here, and worked just fine under v7.5 but
crashed and burned [or rather simply hung]
miserably under v8.5). Another whole organization (one of
those groups with their own server connecting
to our hub) used to use read proxies EXCLUSIVELY to
determine availability -- they never even knew that
you could PROPOSE meetings between individuals until they
learned that from us. So the usage patterns
which v7.5 allowed, which were prevented by the rewritten
code in v8.5, were the biggest culprit. Had we
upgraded to v8.0 when it first came out, we might have been
prepared for a lot of these issues. Hindsight,
you know the rest.

So it's not just not having the need or resources to move to
v8.5 or v8.6 that should be preventing you from
upgrading to it. You should seriously consider if DST is
important or not (from my years '76-'86 at Grand
Valley State there in Michigan, I doubt that it's
*really* that important ;-P) and avoid moving to v8.x like
the plague. It certainly is NOT a better product than v7.5 was.


"Never Underestimate the bandwidth of a station wagon full
of mag tapes"
J.Lance Wilkinson
("Lance") InterNet: ***@psu.edu
Systems Design Specialist -
Lead AT&T: [phone]
Digital Library
Technologies FAX: [phone]
E3 Paterno Library "I'd rather
be dancing..."
Penn State University A host is a host
from coast to coast,
University Park, PA 16802 And no one will talk
to a host that's close
<***@psulias.psu.edu> Unless the host that
isn't close
EMail Professional since 1978 Is busy, hung or dead.
"He's dead, Jim. I'll get his tricorder. You take his
wallet."
[apologies to DeForest Kelley, 1920-1999]
<A Href="http://perdita.lcs.psu.edu">home page</a>
<a Href="http://perdita.lcs.psu.edu/junkdec.htm">junk mail
declaration</a>
--
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[Raoul Armfield]

Jack C Newton wrote:
> Now that certainly doesn't excuse the bugs they has on release but
we make it
> a policy to not go to a first version of a release of any enterprise software
> unless we're sure it's really solid.
>
> Jack Newton
>
>
> From: "J.Lance Wilkinson" <***@PSULIAS.PSU.EDU>
> Date: 2006/09/21 Thu AM 08:19:04 CDT
> To: MMXP-***@LISTSERV.EMORY.EDU
> Subject: Re: Daylight Saving Time effects on 7.5
> In many respects the problems were caused by the simple fact
> that we use the product differently than the
> vendor had EVER conceived it to be used; users with more
> than 20 read/write proxies open simultaneously
> is not uncommon here, and worked just fine under v7.5 but
> crashed and burned [or rather simply hung]
> miserably under v8.5). Another whole organization (one of
> those groups with their own server connecting
> to our hub) used to use read proxies EXCLUSIVELY to
> determine availability -- they never even knew that
> you could PROPOSE meetings between individuals until they
> learned that from us. So the usage patterns
> which v7.5 allowed, which were prevented by the rewritten
> code in v8.5, were the biggest culprit. Had we
> upgraded to v8.0 when it first came out, we might have been
> prepared for a lot of these issues. Hindsight,
> you know the rest.
>

I agree with Jack, it seems that thorough testing would show some of
these problems before you went live with the product. In addition, it
also seem that some of the problems you experienced may not have been
directly caused by meetingmaker but a lack of training of the users.
Meetingmaker's most basic premise is the ability to propose meetings.
What did they suppose the invite guest button was for when they created
an activity?

While it is great that v7 was able to handle the unusual way your users
used meetingmaker it was still not in the way it was designed to be used
and as such you can not blame those issues on meetingmaker calling the
new software badly written.


--
Raoul Armfield
rarmfield at amnh dot org


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[J.Lance Wilkinson]

At 10:49 AM 9/21/2006 -0500, you wrote:
>Well let's face it, the inerface was real old and people were complaining
>about that too (looked simplistic to me). At some point they had to design a
>new interface but ended up adding a "Classic View" option to help ease the
>transition. So people who didn't want the new interface would hate them and
>people who did would hate them if they didn't change it. Damned if you do,
>damned if you don't....

Simplistic is good. It's a CALENDAR. A matrix of boxes
with numbers
and notes in them. OUTLOOK is BAD so making things look like OUTLOOK
is NOT an improvement. The washed out label colors are my biggest
new interface complaint. When you choose a label color
the colors are
distinct, but in use you cannot tell the difference between
the 7th label and
the 14th label colors on a calendar itself. Why increase
the label choices
when they can't be differentiated in practice?


>I guess my question is, didn't you test before you upgraded? As an IT manager
>I would never upgrade an enterprise application without doing at least a
>modicum of testing....especially if so many people depended on it. It's
>obvious the interface is completely different as soon as you sign on to the
>client and use the basic functions.

We tested for 6 weeks before upgrading. Many of the
interface problems
were detected then, but the powers who were pressing for the upgrade
(Oh, this new version supports Blackberry! We've GOT to have that, so
who cares about the retraining needed?) were able to force that thru.

The sheer volume of our usage was the cause of the Memory Leaks
which had been there from the start but were apparently
never encountered
by the (what did MM tech support say? Oh, yes...) 3 MILLION
other users.

Problems caused by having calendars that reach back 6+ years
instead of the
6months that MM/PeopleCube wants you to purge down to when
upgrading.
Important histories are stored solely in MM calendars here.

Problems caused by single administrative aides having 20+
read/write proxies
open simultaneously. Availability scheduling is fine, but
sometimes a new
proposal is more important than what it's conflicting with,
and so said aides
need to shuffle multiple administrator's schedules to comply
with changing needs.

Problems caused by proxy viewers changing the presentation
for the owner
of a calendar (sometimes resulting in a font choice that's
imcompatibile with
the owner's monitor drivers, making the proxy viewer the
only person who can
even SEE/READ the calendar).

Problems caused by web publishing having been changed so that only the
individual with read proxies open at the time can publish
the calendar.

The list goes on, but you can see that without completely DUPLICATING
our entire user base and DUPLICATING our entire user USAGE PATTERNS
we would never have seen the problems which we encountered. Since MM
can only have one client on a machine at a given time, to
test that out we
would have had to have deployed 600+ additional machines,
with the v8.5
client on them instead of the v7.5 client, pointing to a
v8.5 server/hub set
instead of a v7.5 server/hub set, and then let that go on
for 6 weeks of parallel
content duplication.

No, instead we set up a small test case with 3 or 4 users
authorized and
had select MM user experts play with it as time permitted in
their already
busy schedules (let's face it, if you're not busy you don't NEED MM or
Steltor or Outlook or a Blackberry or a Palm.... and if you
are, you don't duplicate
effort just to help the techies test something). The users
looked, bitched, were
told that this was what was going to be done, said fine
let's do it then and get
it over with.


>Now that certainly doesn't excuse the bugs they has on release but we make it
>a policy to not go to a first version of a release of any enterprise software
>unless we're sure it's really solid.

We tend to use past experience in determining if we've done
enough testing.
Past experience (we've used MM since v2.3) suggested that
the 6 weeks of
testing was sufficient. Clearly we were wrong. They won't
catch us again.


"Never Underestimate the bandwidth of a station wagon full
of mag tapes"
J.Lance Wilkinson
("Lance") InterNet: ***@psu.edu
Systems Design Specialist -
Lead AT&T: [phone]
Digital Library
Technologies FAX: [phone]
E3 Paterno Library "I'd rather
be dancing..."
Penn State University A host is a host
from coast to coast,
University Park, PA 16802 And no one will talk
to a host that's close
<***@psulias.psu.edu> Unless the host that
isn't close
EMail Professional since 1978 Is busy, hung or dead.
"He's dead, Jim. I'll get his tricorder. You take his wallet."
[apologies to DeForest Kelley, 1920-1999]
<A Href="http://perdita.lcs.psu.edu">home page</a>
<a Href="http://perdita.lcs.psu.edu/junkdec.htm">junk mail
declaration</a>
--
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[Kyle Johnson]

On 9/22/06 at 8:53 AM, J.Lance Wilkinson wrote:
> (Oh, this new version supports Blackberry! We've GOT to have that, so
> who cares about the retraining needed?) were able to force that thru.

How ironic that the new version requires you to purchase yet more
hardware and software to do wireless syncing and doesn't actually
support Blackberry (even though MM said it would, and now they blame
their partner for the delay). Or at least it didn't six months or so
ago when we abandoned wireless sync.

/kyle
---
Kyle Johnson : Director, Information Technology Services
Duke University Student Affairs
***@duke.edu : http://www.studentaffairs.duke.edu
jabber- ***@jabber.duke.edu : aim- dukekej
-----------------------------------------------------------------------
Do you have change for a paradigm?


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[Damon Palyka]

Notifylink is beta testing MM support right now...
Im in on the beta and it works great...

Kyle Johnson wrote:
> On 9/22/06 at 8:53 AM, J.Lance Wilkinson wrote:
>> (Oh, this new version supports Blackberry! We've GOT to have that, so
>> who cares about the retraining needed?) were able to force that thru.
>
> How ironic that the new version requires you to purchase yet more
> hardware and software to do wireless syncing and doesn't actually
> support Blackberry (even though MM said it would, and now they blame
> their partner for the delay). Or at least it didn't six months or so
> ago when we abandoned wireless sync.
>
> /kyle
> ---
> Kyle Johnson : Director, Information Technology Services
> Duke University Student Affairs
> ***@duke.edu : http://www.studentaffairs.duke.edu
> jabber- ***@jabber.duke.edu : aim- dukekej
> -----------------------------------------------------------------------
> Do you have change for a paradigm?
>
>
> * MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML
>
>


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[Jack C Newton]

Right, I heard about Puma Tech promising Blackberry support and then pulling
it. Suppossedly one of the results of the lawsuit against RIM.

I'm sure that's probably why Peoplecube checked in to having Notify handle
the syncing instead since they handle most devices, including Blackberry. If
the rumor I heard is true, I think they intend on offering free licenses to
existing Intellisync owners. Again, I know not the details....

Jack Newton

From: Kyle Johnson <***@DUKE.EDU>
Date: 2006/09/22 Fri AM 08:05:40 CDT
To: MMXP-***@LISTSERV.EMORY.EDU
Subject: Re: Daylight Saving Time effects on 7.5

On 9/22/06 at 8:53 AM, J.Lance Wilkinson wrote:
> (Oh, this new version supports Blackberry! We've GOT to have that, so
> who cares about the retraining needed?) were able to force that thru.

How ironic that the new version requires you to purchase yet more
hardware and software to do wireless syncing and doesn't actually
support Blackberry (even though MM said it would, and now they blame
their partner for the delay). Or at least it didn't six months or so
ago when we abandoned wireless sync.

/kyle
---
Kyle Johnson : Director, Information Technology Services
Duke University Student Affairs
***@duke.edu : http://www.studentaffairs.duke.edu
jabber- ***@jabber.duke.edu : aim- dukekej
-----------------------------------------------------------------------
Do you have change for a paradigm?


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[Jack C Newton]

Phew, you sure seem to enjoy long emails. I'll try to keep it short.

The view preferences that you don't like: it's an opinion, not a way to base
future releases on.

So out of the thousands of users that you have you tested with 4-6 when they
had the time, found some problems and were told to upgrade anyway where you
revealed more problems. Sounds more like issues with your bosses more than
anything. Yes it was not the best upgrade they ever released, that was
established. Glad you won't get caught in that hole again.

We will of course be testing 8.6 fairly rigorously before we upgrade but have
high hopes since it is still based on the same 8.5 framework and not a
complete rewrite as it was from 7.5 to 8.5.

Jack Newton

From: "J.Lance Wilkinson" <***@PSULIAS.PSU.EDU>
Date: 2006/09/22 Fri AM 07:53:39 CDT
To: MMXP-***@LISTSERV.EMORY.EDU
Subject: Re: Daylight Saving Time effects on 7.5

At 10:49 AM 9/21/2006 -0500, you wrote:
>Well let's face it, the inerface was real old and people were complaining
>about that too (looked simplistic to me). At some point they had to design a
>new interface but ended up adding a "Classic View" option to help ease the
>transition. So people who didn't want the new interface would hate them and
>people who did would hate them if they didn't change it. Damned if you do,
>damned if you don't....

Simplistic is good. It's a CALENDAR. A matrix of boxes
with numbers
and notes in them. OUTLOOK is BAD so making things look like
OUTLOOK
is NOT an improvement. The washed out label colors are my biggest
new interface complaint. When you choose a label color
the colors are
distinct, but in use you cannot tell the difference between
the 7th label and
the 14th label colors on a calendar itself. Why increase
the label choices
when they can't be differentiated in practice?


>I guess my question is, didn't you test before you upgraded? As an IT
manager
>I would never upgrade an enterprise application without doing at least a
>modicum of testing....especially if so many people depended on it. It's
>obvious the interface is completely different as soon as you sign on to the
>client and use the basic functions.

We tested for 6 weeks before upgrading. Many of the
interface problems
were detected then, but the powers who were pressing for the upgrade
(Oh, this new version supports Blackberry! We've GOT to have that,
so
who cares about the retraining needed?) were able to force that
thru.

The sheer volume of our usage was the cause of the Memory Leaks
which had been there from the start but were apparently
never encountered
by the (what did MM tech support say? Oh, yes...) 3 MILLION
other users.

Problems caused by having calendars that reach back 6+ years
instead of the
6months that MM/PeopleCube wants you to purge down to when
upgrading.
Important histories are stored solely in MM calendars here.

Problems caused by single administrative aides having 20+
read/write proxies
open simultaneously. Availability scheduling is fine, but
sometimes a new
proposal is more important than what it's conflicting with,
and so said aides
need to shuffle multiple administrator's schedules to comply
with changing needs.

Problems caused by proxy viewers changing the presentation
for the owner
of a calendar (sometimes resulting in a font choice that's
imcompatibile with
the owner's monitor drivers, making the proxy viewer the
only person who can
even SEE/READ the calendar).

Problems caused by web publishing having been changed so that only
the
individual with read proxies open at the time can publish
the calendar.

The list goes on, but you can see that without completely
DUPLICATING
our entire user base and DUPLICATING our entire user USAGE PATTERNS
we would never have seen the problems which we encountered. Since
MM
can only have one client on a machine at a given time, to
test that out we
would have had to have deployed 600+ additional machines,
with the v8.5
client on them instead of the v7.5 client, pointing to a
v8.5 server/hub set
instead of a v7.5 server/hub set, and then let that go on
for 6 weeks of parallel
content duplication.

No, instead we set up a small test case with 3 or 4 users
authorized and
had select MM user experts play with it as time permitted in
their already
busy schedules (let's face it, if you're not busy you don't NEED MM
or
Steltor or Outlook or a Blackberry or a Palm.... and if you
are, you don't duplicate
effort just to help the techies test something). The users
looked, bitched, were
told that this was what was going to be done, said fine
let's do it then and get
it over with.


>Now that certainly doesn't excuse the bugs they has on release but we make
it
>a policy to not go to a first version of a release of any enterprise
software
>unless we're sure it's really solid.

We tend to use past experience in determining if we've done
enough testing.
Past experience (we've used MM since v2.3) suggested that
the 6 weeks of
testing was sufficient. Clearly we were wrong. They won't
catch us again.


"Never Underestimate the bandwidth of a station wagon full
of mag tapes"
J.Lance Wilkinson
("Lance") InterNet: ***@psu.edu
Systems Design Specialist -
Lead AT&T: [phone]
Digital Library
Technologies FAX: [phone]
E3 Paterno Library "I'd rather
be dancing..."
Penn State University A host is a host
from coast to coast,
University Park, PA 16802 And no one will talk
to a host that's close
<***@psulias.psu.edu> Unless the host that
isn't close
EMail Professional since 1978 Is busy, hung or dead.
"He's dead, Jim. I'll get his tricorder. You take his
wallet."
[apologies to DeForest Kelley, 1920-1999]
<A Href="http://perdita.lcs.psu.edu">home page</a>
<a Href="http://perdita.lcs.psu.edu/junkdec.htm">junk mail
declaration</a>
--
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[J.Lance Wilkinson]

At 08:25 AM 9/22/2006 -0500, you wrote:
>Phew, you sure seem to enjoy long emails. I'll try to keep it short.

I'll try to keep it short.

>The view preferences that you don't like: it's an opinion, not a way to base
>future releases on.

You must not have 50-year-old eyes then. Or somehow you found
a way to make labels appear differently. SPECIFICALLY how do you
get label #7 and label #14 to appear different? I PERSONALLY would
like to know.

>So out of the thousands of users that you have you tested with 4-6 when they
>had the time, found some problems and were told to upgrade anyway where you
>revealed more problems. Sounds more like issues with your bosses more than
>anything. Yes it was not the best upgrade they ever released, that was
>established. Glad you won't get caught in that hole again.

No, this time we get caught in a hole created by idots in DC
who think that
their energy policy problems can be patched over by having
our kids go to
AND come home from school in the dead of night.

>We will of course be testing 8.6 fairly rigorously before we upgrade but have
>high hopes since it is still based on the same 8.5 framework and not a
>complete rewrite as it was from 7.5 to 8.5.

I would like to see your procedural plans for testing your 600+ users'
situations without deploying separate PCs for them to run MM clients
on. Please elucidate how you manage that.

"Never Underestimate the bandwidth of a station wagon full
of mag tapes"
J.Lance Wilkinson
("Lance") InterNet: ***@psu.edu
Systems Design Specialist -
Lead AT&T: [phone]
Digital Library
Technologies FAX: [phone]
E3 Paterno Library "I'd rather
be dancing..."
Penn State University A host is a host
from coast to coast,
University Park, PA 16802 And no one will talk
to a host that's close
<***@psulias.psu.edu> Unless the host that
isn't close
EMail Professional since 1978 Is busy, hung or dead.
"He's dead, Jim. I'll get his tricorder. You take his wallet."
[apologies to DeForest Kelley, 1920-1999]
<A Href="http://perdita.lcs.psu.edu">home page</a>
<a Href="http://perdita.lcs.psu.edu/junkdec.htm">junk mail
declaration</a>
--
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML