Home
%3CLINGO-SUB%20id%3D%22lingo-sub-595909%22%20slang%3D%22en-US%22%3EVideo%20demos%20for%20running%20Exchange%20and%20Outlook%20DST%202007%20tools%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-595909%22%20slang%3D%22en-US%22%3E%3CP%3E%3C%2FP%3E%3CP%3E%3CFONT%20face%3D%22Verdana%22%20size%3D%222%22%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%20face%3D%22Verdana%22%20color%3D%22%23ff0000%22%20size%3D%222%22%3E%3CSTRONG%3EEDIT%3A%20This%20post%20has%20been%20edited%20on%209%2F14%2F2007%20to%20point%20to%20new%20versions%20of%20videos.%3C%2FSTRONG%3E%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%20face%3D%22Verdana%22%20size%3D%222%22%3EWe%20have%20put%20together%20three%20demos%20that%20you%20can%20use%20to%20familiarize%20yourself%20with%20the%20process%20of%20running%20the%20DST%20tools.%20We%20think%20that%20the%20following%20three%20scenarios%20cover%20what%20people%20need%20to%20run%20most%20often.%20%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%20face%3D%22Verdana%22%20size%3D%222%22%3E%3C%2FFONT%3E%3C%2FP%3E%3CFONT%20color%3D%22%23ff0000%22%3E%3CP%20class%3D%22MsoNormal%22%3E%3CFONT%20size%3D%222%22%3E%3CFONT%20face%3D%22Verdana%22%3E%3CFONT%20color%3D%22%23000000%22%3E%3CB%3E%3CSPAN%3EDST%3A%20How%20to%20Address%20Daylight%20Saving%20Time%20by%20Using%20the%20Exchange%20%26nbsp%3BCalendar%20Data%20Update%20Tool%3C%2FSPAN%3E%3C%2FB%3E%3CSPAN%3E%3C%2FSPAN%3E%3C%2FFONT%3E%3C%2FFONT%3E%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3C%2FP%3E%3C%2FFONT%3E%3CP%3E%3C%2FP%3E%0A%3CP%20class%3D%22MsoNormal%22%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fchannel9.msdn.com%2FShowPost.aspx%3FPostID%3D341747%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3E%3CFONT%20face%3D%22Verdana%22%20size%3D%222%22%3Ehttps%3A%2F%2Fchannel9.msdn.com%2FShowPost.aspx%3FPostID%3D341747%3C%2FFONT%3E%3C%2FA%3E%3CFONT%20face%3D%22Verdana%22%20size%3D%222%22%3E%20%3C%2FFONT%3E%3C%2FSPAN%3E%3CSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3C%2FP%3E%3CP%3E%3C%2FP%3E%0A%3CP%20class%3D%22MsoNormal%22%3E%3CSPAN%3E%3CFONT%20size%3D%222%22%3E%3CFONT%20face%3D%22Verdana%22%3E%26nbsp%3B%3C%2FFONT%3E%3C%2FFONT%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3C%2FP%3E%3CP%3E%3C%2FP%3E%0A%3CP%20class%3D%22MsoNormal%22%3E%3CB%3E%3CFONT%20color%3D%22%23000000%22%3E%3CFONT%20size%3D%222%22%3E%3CFONT%20face%3D%22Verdana%22%3EDST%3A%20Using%20the%20Outlook%20v2.0%20Time%20Zone%20Data%20Update%20Tool%3C%2FFONT%3E%3C%2FFONT%3E%3C%2FFONT%3E%3C%2FB%3E%3C%2FP%3E%3CP%3E%3C%2FP%3E%3CP%3E%3C%2FP%3E%0A%3CP%20class%3D%22MsoNormal%22%3E%3CA%20href%3D%22https%3A%2F%2Fchannel9.msdn.com%2FShowPost.aspx%3FPostID%3D341649%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3E%3CFONT%20face%3D%22Verdana%22%20color%3D%22%230000ff%22%20size%3D%222%22%3Ehttps%3A%2F%2Fchannel9.msdn.com%2FShowPost.aspx%3FPostID%3D341649%3C%2FFONT%3E%3C%2FA%3E%3CFONT%20face%3D%22Verdana%22%20color%3D%22%23000000%22%20size%3D%222%22%3E%20%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%20class%3D%22MsoNormal%22%3E%3C%2FP%3E%3CP%3E%3CFONT%20face%3D%22Verdana%22%20color%3D%22%23000000%22%20size%3D%222%22%3E%26nbsp%3B%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3C%2FP%3E%0A%3CP%20class%3D%22MsoNormal%22%3E%3CB%3E%3CFONT%20color%3D%22%23000000%22%3E%3CFONT%20size%3D%222%22%3E%3CFONT%20face%3D%22Verdana%22%3EDST%3A%20Cumulative%20Time%20Zone%20Update%20for%20Microsoft%20Windows%3C%2FFONT%3E%3C%2FFONT%3E%3C%2FFONT%3E%3C%2FB%3E%3C%2FP%3E%3CP%3E%3C%2FP%3E%3CP%3E%3C%2FP%3E%0A%3CP%20class%3D%22MsoNormal%22%3E%3CA%20href%3D%22https%3A%2F%2Fchannel9.msdn.com%2FShowPost.aspx%3FPostID%3D341535%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3E%3CFONT%20face%3D%22Verdana%22%20color%3D%22%230000ff%22%20size%3D%222%22%3Ehttps%3A%2F%2Fchannel9.msdn.com%2FShowPost.aspx%3FPostID%3D341535%3C%2FFONT%3E%3C%2FA%3E%3CFONT%20face%3D%22Verdana%22%20color%3D%22%23000000%22%20size%3D%222%22%3E%20%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%20size%3D%222%22%3E%3CFONT%20face%3D%22Verdana%22%3E%3CSTRONG%3E%3CFONT%20color%3D%22%23ff0000%22%3EEDIT%203%2F1%2F07%3A%3C%2FFONT%3E%3C%2FSTRONG%3E%20We%20have%20added%20additional%20video%20for%20resource%20mailboxes%20%3C%2FFONT%3E%3C%2FFONT%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Farchive%2F2007%2F03%2F01%2F436164.aspx%22%20target%3D%22_blank%22%3E%3CFONT%20face%3D%22Verdana%22%20size%3D%222%22%3Ehere%3C%2FFONT%3E%3C%2FA%3E%3CFONT%20face%3D%22Verdana%22%20size%3D%222%22%3E.%20%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%20face%3D%22Verdana%22%20size%3D%222%22%3E-%20%3C%2FFONT%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Farticles%2F435481.aspx%22%20target%3D%22_blank%22%3E%3CFONT%20face%3D%22Verdana%22%20size%3D%222%22%3ESteve%20Justice%3C%2FFONT%3E%3C%2FA%3E%3CFONT%20face%3D%22Verdana%22%20size%3D%222%22%3E%2C%20Chris%20Burnham%3C%2FFONT%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E

EDIT: This post has been edited on 9/14/2007 to point to new versions of videos.

We have put together three demos that you can use to familiarize yourself with the process of running the DST tools. We think that the following three scenarios cover what people need to run most often.

DST: How to Address Daylight Saving Time by Using the Exchange  Calendar Data Update Tool

https://channel9.msdn.com/ShowPost.aspx?PostID=341747

 

DST: Using the Outlook v2.0 Time Zone Data Update Tool

https://channel9.msdn.com/ShowPost.aspx?PostID=341649

 

DST: Cumulative Time Zone Update for Microsoft Windows

https://channel9.msdn.com/ShowPost.aspx?PostID=341535

EDIT 3/1/07: We have added additional video for resource mailboxes here.

- Steve Justice, Chris Burnham

127 Comments
Not applicable
That's brilliant, thank you! (I'm already done the updates so it's too late for me, but now I have somewhere to direct others.)
Not applicable
May I make this video available to my users, either by linking to it or by hosting it on our organization's support site?
Not applicable
LDP - sure, go for it.

Linking might work better to get most up to date info as we are looking to post updated videos for v2 version of the tool and then I plan to comment the post to include links to that.
Not applicable
These walkthroughs are extremely helpful. Thank you very much.
Not applicable
Where can I get the MsExTmz.exe referenced? I can only find MsExTmz.msi linked off the site which does not include MsExTmzcfg.msi. I am following the link from

http://support.microsoft.com/?kbid=930879 which takes me to

http://www.microsoft.com/downloads/details.aspx?FamilyId=A9336886-4B28-4010-9416-36D38429438D&displaylang=en.

Not applicable
I see the Exchange tool V2 has been posted, but I didnt see any update on what has changed. Anyone know what changed or where the info is available
Not applicable
The MSEXTMZ 2.0 tool has indeed been released. The KB article (930879) has been updated, unfortunately, it is missing a very important piece! It reads:

"If you are using direct booking or the Auto Accept Agent, follow these steps to update the resource mailboxes."

There are no steps listed after this section, it jumps right to Public Folders. Can someone alert the KB article writers, and have them update that section? We are rolling out the updates this weekend. This section is very important as we have numerous resources using AutoAccept.
Not applicable
Rob D and MikeD,

What has been posted is the Exchange tool v2, yes. However, this is not what will help with resource mailboxes and is NOT the tool that will help with the resource mailboxes. the Exchange tool brings a bit more robustness in UI, logging etc - pretty much all of which you can see if you run the tool. No more need for server LegacyExchangeDN for example or Outlook registry path.

The updated Outlook tool is scheduled to come out next week, and that will provide additional relief for PF based calendars and recource mailboxes.
Not applicable
Thanks for that information. We have scheduled this Sunday for our update. Is there any chance that the updated tool will be released before then?
Not applicable
The original webcast mentioned that the server you run the Exchange Calendar Update Tool has to be in the time zone in which you are performing updates for.  So, we would have to parse out the users in different time zones.

The tool seems to address multiple time zones for mailboxes on the same server (ie. a server in PA that has users in NY, PA, MN, etc.).

Is this correct?
Not applicable
Rob D,

The chance of this coming this week is very small, I would not count on it.

agrajag42 - the new version of the Exchange tool - yes that is one of things that are improved in it.
Not applicable
This new version of the Exchange tool ensur that single instance items created after the date on which the operating system time zone updates were applied are not rebased?
Not applicable
Marius,

No - the new tool can not ensure that... the reason for the inability to solve that is because even the newly created appointments, created after OS was patched (unless tehy were created using Outlook 2007 client) do not have the timezone information embedded in them, so they will get moved by default. However if you run the Outlook tool, you will have the choice not to move those.
Not applicable
Thanks for that information.
Not applicable
I have been unable to install the new Exchange tool.  It insists I still have the previous version installed, which I don't.  I even tried the Installer Cleanup tool, but no dice.  I didn't see anything in the registry, but I suspect I'm looking at the wrong place.  Any ideas on how to get the v2 tool to install?
Not applicable
Not applicable
Do you have an idea on when version 2 of the VM will be released for download? We plan to start testing this weekend, with rollout/patching next weekend.

We currently are unable to install v2 of the exchange tool, it complains about v1 still being installed. Any help on that in the meantime before v2 of the VM is released so that we can continue with testing using v2 this weekend?
Not applicable
Tim and Spider,

When I moved from version 1 to version 2 of the Exchange tool, I had to uninstall both MSEXTMZ and MSEXTMZCFG separately. And another issue, the CFG tool needs to be uninstalled using the same account that was used to install it, as it appears to install per-user, not per-machine. It won't appear in add/remove programs for any other account. Version 2 uses a single installer to install both tools, thankfully.
Not applicable
The DST 2007 and Exchange product group have released an updated version of the Exchange Calendar Update
Not applicable
Is it normal for Version 2 of the tool not to open Outlook each time?  I just want to make sure that is correct because I am not sure it is working.
Not applicable
Also.. what does it mean when it says, "No log file written for user"?
Not applicable
Jason, yes - that is expected.
Not applicable
The tool looked like it was running fine and then every mailbox started to get the following error:

No Event log records written - Treated as failure.
HrProcessMailbox:Unable to process mailbox
Not applicable
If we decide to rebook the appointment manually, we don't have to run the tool again next year for recurring meeting, as long as we patched Exchange servers, WS, right?
Not applicable
I start having the same problem as Jason.
I have not got it working yet.
I noticed the utility is adding a bunch of outlook profiles.
Not applicable
I know you're saying you can can't update single instance appointments because of not having the Time Zone stamp, but why not by creation, accepted, or sent date instead?  If we know or were able to check on the local machine when the patch was applied, then only adjust for those appointments that were created/accepted/sent before the installation date?
Not applicable
Is there an estimate as to 'when' the new Outlook tool will be coming out?  We ran the updates this weekend, and are having NO luck getting resource accounts or Public Folders to update.  I've run the grant permissions script against all resource accounts, but cannot get those to update.  Every public folder I run the Outlook tool against tells me there are no items to be updated.

Let's just say my boss is unhappy with the results thus far...
Not applicable
I used the demo and that was very helpful and we got the Exchange tool both V1 and V2 to run ok. But even though it ran it did not fix the calendar appointments as anticipated. It only provided one log file for a user instead of the 11 expected and said it fixed one appt. so we then logged back in under the user and the time did not change.  We tested the manual tzmove.exe outlook tool and that did show that it would fix the appts that the exchange tool missed but with several hundred users this is not the preferred method. Will there be any updates to the exchange tool? Any suggestions we can test in our lab to get the current exchange tool v1 or v2 to fix the appts.
Not applicable
I am trying to update my Exchange server using the Exchange Update Tool but when I enter in the LegacyExchangeDN is gives me the following error message:

"Invalid Server. Please make sure you have enetered valid server name"

This is the following Server Name I am entering (edited of course):

ServerDN=/o=DOMAINNAME/ou=First Administrative Group/cn=Configuration/cn=Servers/cn=EXCHANGESRVRNAME

I am also selecting the Outlook Profile name from the drop down menu, and selecting "Extract Recurring Meeting Time Zones"

Am I doing something wrong?
Not applicable
Greg,

Try downloading the V2 of Exchange tool, it does not require Legacy Exchange DN anymore...
Not applicable
Thanks Exchange. That was it. I am now running MsExTmzCfg.exe and it goes through all the mailboxes and I get the following on almost all of them (I think):

HrProcessMailboxTable:Unable find mailbox timezone:Error 0x80004005.

Any suggestions?
Not applicable
I have a question?  When I run the Exchange Update Tool I get to a screen called Map Time Zones:

My organization is only in 2 Time Zones. (Atlantic and Newfoundland)-

In the Map Time Zone Dialog box I see 3 time zones.
--------------------------------------------------
Atlantic Time (Canada)
GMT -4 (Standard)/GMT -300 (Daylight)
Central Time
Newfoundland
--------------------------
Fore the GMT -4 (Standard)/GMT -300 (Daylight) - "Someone may have made this custom zone and I think I can map it to Atlantic Time Canada since it is the same offset from GMT.

For the one that says central time I can use the correct central time zone.

When I move to the next screen called Calender update Configuration under Select Time Zones that need to be updated I only see one time zone listed (Atlantic Time - Canada).  Should I see multiple time zones?  Also do I have to somehow seperate out my users to update by thier time zones?

Not applicable
Greg,

"Unable find mailbox timezone:Error 0x800004005" during time zone extraction process is not a big deal, you do not have to worry about this much.

Simply add those users into mailboxes_1.txt, tab separated, in the format of "user <tab> server <tab> timezone". You can use Excel to make this easy (Excel is on the virtual machine that you can download from us with tools), hopefully most of your users are in the same timezone - then it becomes REALLY easy.
Not applicable
What if your users are spread across the globe, and 50% don't return a value?  What would you recommend in this case?  If I assume based on which mail server they're attached to (we have one in most timezones), what if I get some wrong?  Will all these people's appointments show up off?
Not applicable
I am still confused after reading all the documentation about whether meeting notices will be updated correctly when running the exchange tool.  Our DST patch has been applied to all user workstations.  Meetings scheduled prior to the patch are off by one hour.  I understand these will be corrected.  Will meetings that are NOT off by one hour also be affected when running the exchange tool?  Can the exchange tool be run for just select users?
Not applicable
Ben, you can select which users the exchange tool runs against, by editing the .txt files that list your exchange mailboxes.
Not applicable
Ben,

Meetings that are NOT wrong WILL also get moved... unless they were created using Outlook 2007. That is because only Outlook 2007 embeds the timezone info into the meeting request, other clients do not.

That is why you see it written that patching and rebasing should be done in rapid succession, so the amount of newly created appointments once the OS patches are applied is as low as possible.

Yes you can run the tool only for some users. Just edit the files that the Exchange tool gives you as a result of a run, before you run the batch file. Take the mailboxes you do not want to run on out.
Not applicable
Since the Exchange tool uses its own version of tzmove.exe -  will it still require the updated Outlook Tool (v.2)  ?

Not applicable
President Carter,

From what we have learned, there seems to be no issue with "assigning" a time zone to a bunch of clients. If you are not sure where some of the clinet s are, assign them a timezone based on your best guess and run the tool. What happens (in our lab testing) is that Outlook actually displays things correctly once the client has logged on. Note that this is coming from what we have seen in support cases. I would suggest you test this for few test mailboxes and assign them a "wrong" timezone to make sure that nothing out of ordinary happens. Create a "complex" mailbox meaning if there are 3rd party mobile devices, OWA access etc, make sure this mailbox does it.
Not applicable
I have an issue, I ran the update on a PC that had not gotten the DST update, so all the appointments in the March 10 to April 1st range were moved one hour ahead. What's the easiest route to fix those appointments? I am in Eastern Standard and my file is set to Eastern Time. I was thinking of updating the mailboxes_1 file with Central so it would force the changes to those dates or is there a better way??
Not applicable
The hotfix for the Outlook tool is now available. Please see the following KB article:

http://support.microsoft.com/kb/933146

Please note that the original Outlook tool has to be installed before the hotfix is applied. The article contains information about new switches available in the tool. This IS what has been called a "V2" of Outlook tool, but it is not a new standalone version but is rather a hotfix for the original tool.
Not applicable
So since the old tool updated everything to the DST Updated time, all appointments in the 3 week period are one hour forward. What is the easiest way to correct them all? I see in the new tool there are more options, would those help?
Not applicable
I was successful with running the batch file. I did run into a few users who
errored out. What do you think of the error codes?

0x8004011C and 0x80070002
Not applicable
Interestingly.. it appears that even though the patch wasn't applied, the first time through it really didn't run against anything (no files were created for each user) However what I find interesting is there are certain recurring appts that DID change to their correct time, and then we have others that did not on the same day. Any clues as to why or perhaps how to check to make sure they are all correct?
Not applicable
Just an FYI.

The error I was receiving:
"No Event log records written - Treated as failure.
HrProcessMailbox:Unable to process mailbox"  

This was due to my application log in my event viewer was filling up.  I was keeping 7 days of events so I changed it to overwrite as needed.

Not applicable
Thank you so much for this BLOG and the videos. It has been VERY helpful.

Russ
Not applicable
I have the V2 for the Exchange Calendaring tool and it still comes up with the legacydn for Exchange and I cut and paste it from adsieditbut it still says invalid server. What am I doing wrong.
Not applicable
Anyone know what the following error messages mean?

0x8004011C and 0x80070002

Thanks.
Not applicable
The netbios name worked for me
Not applicable
We "successfully" used the Exchange V2 tool this weekend to update about 5k mailboxes.  We seemed to have some problems with exceptions to recurring meetings...  the original date and time seemed to come back in addition to the rescheduled meeting.



The video on this site was very helpful as was the virtual machine that was provided.  We ran one virtual machine for each mailbox being updated.  A summary of notes that may help others:



The V1 uninstall was not complete, so the v2 install complained.  I deleted some installation things from the registry to get the install to work (and installed to a new c:DSTV2 directory), but since then I have read that both the MSEXTMZ and MSEXTMZCFG tools need to be uninstalled from the original account that installed them.



We set up a new domain account to run this with "Exchange Calendar Update Tool" as its display name so that the meeting notices are sent as "Exchange Calendar Update Tool on behalf of ..."  This account was added to an Exchange Recovery Administrator group that we already had that has Receive As permission on each mail store.  No first step with running MSEXTMZ and the grant mailbox permission script.



The V2 MSEXTMZCFG tool was improved to allow the simple server name to be entered, but that had the effect of giving an error if you followed the old instructions for entering the legacy DN, including the same message as if you had typed the DN wrong.   It might have been nice to accept either one,  especially after struggling to get it right with v1, but no harm as long as you know.



The last thing was that we haven't rolled out Outlook 2007 or Exchange 2007, so about half of the mailboxes ended up in NonExistent.txt.  Added the time zone and ran them back through for a second run of MSEXTMZCFG.