a. Time Zone Change FAQ
1. When does Daylight Saving Time begin in Tippecanoe County?
Sunday, April 2, at 2 a.m.
2. For those campus users who need to change the time zone setting manually on computers and electronic devices, when is the best time for them to make the change?
Wednesday, March 22.
3. What devices are affected?
All desktop computers, laptops, and personal electronic devices such as BlackBerry devices and other personal digital assistants used from work or from home to open Microsoft Outlook Calendar. This includes all devices at work and home.
4. Do I need to change my profile in Macromedia Breeze?
Yes, users of Macromedia Breeze need to change the time zone setting in their user profile. For details, contact Tamera Clark, email@example.com
5. How can I safeguard the information in my calendar before changes to the time zone setting are made?
It is recommended that users print out their calendars before changing the time zone setting on computers or personal electronic devices. Users whose computers are supported by Desktop Computing Support (DCS) need to print out calendars during business hours on Tuesday, March 21, before the time zone setting change is pushed to DCS-supported machines.
6. How can I change the time zone setting on my computers and personal electronic devices?
For those users whose machines are not receiving time zone changes from local IT support services, there are step-by-step details on how to manually change the time zone found at the "Instructions" link on the left side of this page.
7. Will my computers and personal electronic devices work together to be synchronized?
Yes, but the synchronization will be affected by the settings on your devices. For example, if your personal electronic device is set to override your computer or merge with your computer, and you change the time zone setting on your computer first, then your calendar in Microsoft Outlook might display two identical entries for every meeting. For details, follow the "Instructions" link at the left side of this page.
8. Will I have to change my time zone setting again when Daylight Saving Time ends in the fall?
No, once you have set all computers and other electronic devices to the correct time zone setting, there will be no need for further adjustments. The time change in the fall will be automatically adjusted for, because the time zone setting recognizes the spring-forward, fall-back routine of Daylight Saving Time.
9. What is a DCS-supported machine?
A DCS-support machine is a computer or laptop that is under a service agreement with Desktop Computing Support, a service of Information Technology at Purdue (ITaP). Your technical coordinator can advise you whether an agreement is in place for your machine. DCS-supported machines are usually identified by an alphanumeric code printed in black on a white label.
10. Where can I turn for help?
Campus users are getting support for making the time zone change from Desktop Computing Support (DCS) and from IT systems administrators in their own academic and business units of campus. Departmental resources are linked from this site. Follow the "Departmental Support Contacts" link on the left side of this page.
b. Microsoft Outlook Exchange Script FAQ
1. What does the script do?
The script will take all appointments that were created with the Indiana time zone and moves them back an hour for those events that occur between April 2 and October 29. That way when users observe Daylight Saving Time, and clocks are moved forward, the event will still be scheduled at the intended time. The script will also append a time stamp on all events that are moved to show the original time the event was scheduled. You will notice some meetings do not have the time stamp appended; that is because those meetings were scheduled in a time zone other than Indiana. If the meeting was scheduled for Daylight Saving Time, then the meeting is correct and does not need to be moved.
2. What will a calendar item look like after the script has been run?
Events that occur after April 2 that were scheduled in the Indiana time zone will have a meeting date and time stamp appended to the subject of the meeting. The format looks like this:
“-- Orig. Scheduled for 8/25/2005 10:15:00 AM in IND Time Zone”
Events that occur after April 2 that do not have the date and time stamp appended were NOT scheduled in the Indiana time zone.
3. Can I remove the formatting that the script added to the time stamp? The formatting adds length to the field making it difficult to read on handheld devices.
We understand the additional information in the subject line noting the original schedule date of the meeting adds to the length of the field making it cumbersome to view on handheld devices. Please do NOT make any changes to the time stamp. We understand this is an inconvenience, but it is our only visible means to know what was actually scheduled for a meeting. Because some users may still be scheduling meetings with the Ind. time zone setting we may need to run the script again - we would hate to see anyone remove the tags and a second run of the script put them all back again. We could consider an automated means of removing the tags on an individual basis once we know the calendars are observing EST/DST correctly.
4. What about users who have been on vacation or extended leave and did not print their calendar?
Calendar appointments will still be automatically adjusted by the script as described. The user will not have an authoritative source for reference.
5. Will appointments appear correct in Outlook Web Access (OWA)?
6. Should I change my time zone settings in Outlook Web Access (OWA)?
Yes, if your appointments do not appear correct after the script has run.
Outlook's Web client contains a setting for "current time zone". In
some browsers, this is the time used when creating a new appointment
from the web-based client. To ensure all appointment times reflect
Indiana's new time zone, please follow the instructions below for
changing the time zone in Outlook's Web client's setting to "Eastern Time":
7. Can I access my calendar on the evening of March 21 while you are running the script?
Give yourself a break from your calendar tonight. Although you can view information in Outlook while the script is running, we prefer you don’t.
8. After the change, if I update a meeting, and send an update request to an attendee, will everything be okay?
Yes, as long as the machine you are sending the update from is in the proper time zone. If you update a meeting from a machine with the Indiana time zone, the issue will remain.
9. Will this script update calendar events for people I have sent meeting requests to outside the ITaP exchange server?
10. What are all of these old reminders that are showing up?
The script generates a few old reminders that will show up in the reminder pop-up window; delete unnecessary reminders that appear.
11. Does the script adjust for anyone moving from Central time to Eastern or Indiana to Central?
No, the script was written to address the majority of West Lafayette Exchange users with the assumption that most, if not all, using the ITaP Exchange services would fall into the scenario of moving from Indiana to Eastern.
12. Will the script modify meetings created in the Eastern time zone?
No, the script does nothing with items created in the Eastern Time Zone, or any other non-Indiana time zone; therefore, the script will only correct Indiana (East) items, fixing the calendars of those who have moved to the Eastern Time Zone but have not completely fixed their calendars.
13. Why isn’t Microsoft doing something to fix the problem?
Outlook isn’t the problem. The calendaring tool is performing as it should. According to Microsoft, time zones in Windows are based on Greenwich Mean Time (GMT). Many calendar and schedule programs, such as Microsoft Outlook, use GMT time to store appointment information. For these programs, appointments typically adjust automatically to the correct local time based on the computer’s time zone setting.
In calendar programs that store appointments by using GMT, appointments change to the correct time when the time zone is changed.
• Jason is in the Indiana (East) time zone.
• Ben is in the Central Time (US & Canada) zone.
• Lynn is in the Eastern Time (US & Canada) zone.
On January 24, 2006, Jason scheduled a 9:00 A.M. Indiana (East) time zone appointment with Ben and with Lynn to occur April 4, 2006. The scheduled appointment automatically appears in Ben’s calendar as 8:00 A.M. and in Lynn’s calendar as 10:00 A.M. This behavior occurs because Ben's calendar program displays appointments based on the local time zone.
When the time changes on April 2, 2006, in Indiana, Jason’s network administrator uses Group Policy to change the local computer time to Eastern Time. Jason’s appointments that are scheduled after April 2, 2006, are automatically updated to reflect the new time zone. Therefore, the appointment on April 4, 2006, is automatically changed to 10:00 A.M. Although this behavior may appear confusing to Indiana residents, it is correct and shows the time that Lynn already had on her calendar.
If Jason wants the appointment to occur at 9:00 A.M. after the time zone change, he must manually move the appointment back in his calendar. After he does this, he can notify users that the appointment time has changed. However, Jason should consider that others who are invited to the appointment may have already been in the Eastern Time zone. These attendees may plan on attending the 10:00 A.M. appointment and may not be available at 9:00 A.M. Jason should examine the calendars of the other meeting attendees before he moves the appointment.
Note: For a meeting item sent from a different exchange server, the item *should* be pre-encoded with the time zone it was created in. For an item created in some other package, the event in your Outlook Calendar will have been made in the Indiana (East) time zone.
c. BlackBerry FAQ
Will appointments appear correct on my Blackberry?
Yes. If events do not appear correct on your Blackberry device please follow the instructions here
on how to change the time zone settings for Blackberry.