SummaryThis document provides recommendations and prescriptive guidance for updating Outlook calendars to comply with the Daylight Saving Time (DST) 2007 rule changes. The goal is to provide an Outlook user with a 'personal touch' experience to help them understand what is happening with their calendar. I wonder if you could confirm my understanding of how the issue affects UK/Europe, and whether my approach is correct?I work in the UK, part of a global organisation. I am planning to update client and server OS's with the DST update; then update the Exchange server OS's and finally apply the Exchange server DST update.I do not think that I need to run the rebase tools for my UK user's calendars.
![]() ![]()
Time zone offset is the time for your geographic region in relation to UTC. For example, the Pacific Time zone is 8 hours behind UTC. Therefore, if it is 8 P.M. UTC, the time in the Pacific Time zone is noon. Daylight saving time rules are the rules by which certain regions seasonally change their time zone offset.
My colleagues in the US are going to be running rebase for their users. The reason I don't think I need to run rebase is that I think that any meetings organised by US/Canada colleagues, that UK people are attendees for, will result in meeting Updates being sent to UK people (generated by rebase), which when the UK people accept will then show the correct local and remote time; and any meetings that UK people have organised, and invited US/Canada people to, will also 'just work' because the originating time zone (GMT) is unaffected. Do you think this is correct? I am reluctant to run the rebase tool if I can avoid it.Thanks in advance for any help.RegardsRichard Read. Thanks for this article, which is very helpful. I am a little confused in the part that says:7. Ask the Outlook user if any appointments on this list appear to be incorrect (e.g., appear one hour ahead).
Any appointments that appear to be one hour ahead will need to be moved.8. Uncheck any appointments that are indicated as correct (e.g., not 1 hour ahead).In step 7, by incorrect, do you mean that the 'new time' displayed is an hour ahead of the desired time? Which would mean that the meeting is already at the correct time and would therefore get unchecked in step 8? So why would they need to be moved? I used to be a dedicated supporter of Microsoft for years but I can't respect that they are hiding behind technicalities in order to charge $4000 instead of releasing the Exchange 2000 patches. What Microsoft is doing may be legal but it is not ethical and it does not engender goodwill. I predict that this little DST 2007 technicality is going to fall out in the end to be a huge hit for Microsoft's public image among formerly supportive IT specialists and business owners.
I never thought I would say it.but time for me to take a Linux class. I have a situation.At one organization the Exchange servers were patched for the new time zone updates which starts on march 11th.On the desktops we ran the Time Zone Patches for XP OS.Running the OS patch moved the timings of the meetings between 10individuals to 9:30 to 11:30 instead of being 8:30 to 10:30The people for whom the OS patch was not added shows the correct time which is 8:30 to 10:30Is there any known method to fix this?NOTE:This is a reccuring meeting and these people have set up many other meetings till the year end. So, after spending the 3 hours on hold with MS we still have a messy problem on our hands. If we roll back to before the 666 patch will the appointments that MS changed go back to the regularly scheduled times?
Will our systems break on Sunday or will OWA show the wrong time for some appointments for the next 3 weeks? What I am thinking is that we were fine before we tried to update our exchange server and the tool approach is worthless. Our OWA is under utilized within our firm so if one place is broken it is better than every place being broken. We have gone through all of the steps that Microsoft provided plus we have gone to individual machines and run all of the patches and tools MS provided and told us to use and we are in the exact same place we were before the last 14 hours of work every calendar appointment is one hour ahead for the next 3 weeks. So I wanted to say THANK YOU for screwing up every single calendar in our office (sarcastic of course). I still cannot understand why anything in outlook needed to be changed, the entire calendar feature just needs a time to tell you when you have an appointment it shouldn't care if it is 9 PM DST or 9 PM STD time it only needs to know 9 PM period. I hope the Exchange Team test their patch and then test it again and again and again next time before releasing it.
The bad think is that Outlook uses the system DST table to write the Calendar time correctly in UMT time + or - for the timezone your in. The bad thing is if you haven't patched all your desktop OS systems in one fell swoop and then run the TZmove utility immediately you have that wonderfully screwed up grey area that should be spelled out at the top of KB articles. You have to know whether the items were created in Outlook prior to or after the DST patch was applied to OS, because if you don't the items created after the OS patch will be changed to be incorrect with the same TZmove utility tool designed to fix the prior patch appointments. This is one hell of a mess from my point of view. Microsoft should have wrote a smarter utility to deal with this mess.
Even if they had that wouldn't necassarily take into account the users that may have machines at different patch states and both have been used to schedule appoinmtents.One solution that enables to pick the items to correct is change the calendar to Event view and add the created field to the view before running TZmove and compare the install date and time for the OS patch and modify only the re-occuring and calendar items that fall into the Extended DST period created before you applied the OS patch and uncheck all that were created after the OS patch. Spent a long time Saturday and Sunday running updates on the XP PCs and running TZmove.exe. Now I have most computers that are an hour ahead! They changed 2 hours, not one.
I set the time correctly and they change back! I tried turning off 'Automatic DST change' to keep the correct time but now Outlook appointments for the rest of the year are incorrect. Any all day events now span an extra day. I just forgot the 30 Win 2000 machines and changed them manually.I'm sure saving a lot of energy on this fiasco. Wish I had never touched our PCs. Can uninstalling the KB-931836 patch fix the Outlook problem?? Sure glad I didn't touch our servers.
After nearly 36 hours of wrestling with DST problems in my Outlook calendar I am about to give up and have lost a great deal of respect for Microsoft in the process. The tzmove tool will not install on my system saying I have not set up outlook as default mail program even when I did. Likely the real problem is I don't have a MS mail account and do not intend to get one. Because of that, the instructions above also are not workable for me as they require a MS exchange account. I was only using the calendar function of outlook and that was all I wanted. This whole thing has been made too complicated to users.If that is not bad enough, I now also have a corrupted SQL server as a resullt of attempts to install microsoft updates last night. Boot message says it is corrupt and I should uninstall SQL server and rerun setup to fix it.
![]()
It gives no direction on how. I can find no help on how to even tell which version of SQL server I have. I did find instructions on web to manually uninstall but that requires using a Microsoft SQL Server compact disc which did not come with my system and its bundled software. I don't really want to buy one and I don't know what version to get if I do nor if it will work to remove the one on my system. I am more than a little frustrated by all this.I wish someone could show me an easy way out of the mess. Think this is complicated.wait till Congress decides we need to stick the the original DST zones and we have to undo all this mess.We have had little or no issues (knock on wood) but we just migrated from Sendmail to Exchange so folks don't have many affected appointments. And we're just now setting up shared calendars and resources.However.some old co-workers of mine have applied all patches and run the Update tool only to find it does not send meeting updates to attendees even though it fixes the organizer's meeting item.
Need help with small issue. I actually wound up calling MS to get help on DST updating and got everything up-to-date and working OK. There is one small issue though, which I'm guessing all of you will have as well. When using the Web interface for Outlook, if you set an all day recurring appointment on one of the DST change days, like the 2nd Sunday of March, it will span 2 days.
All other days work fine, and this is only an issue on Outlook Web.MS has a different order to follow for the steps for updating the exhange server, if users rely heavily on Outlook Web for scheduling appointments or not. I've tried both of these orders, and this problem remains.Occurring on MS Exchange 2003 Servic Pack 2, using WinXP Pro SP2, with IE 6.0 on the client side.
![]() Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2023
Categories |