We have put together a step-by-step walkthrough on how to run the Exchange Calendar Update Configuration Tool (MSExTMZCFG.EXE). This is a server-side tool that can be used as part of the 2007 DS...
Updated Jul 01, 2019
Version 2.0
Blog Post
5 MIN READ
Step by step run of the Exchange Calendar Update Configuration Tool (MSExTMZCFG.EXE)
I had some problems that others have mentioned. May I suggest the blog video is welll worth 24 mintues to watch (http://msexchangeteam.com/archive/2007/02/21/435543.aspx). My basic problem was that when I ran the tool, only the first mailbox was getting updated. Also, the screen filled up with multiple instances of Outlook. I’m not sure what fixed the issue, but here is what I changed that worked:
1/ I had assumed that I had full access because I had given a security group I was a member of full access to the mailbox store. I had no problem accessing everyone’s mailboxes from within Outlook. But just in case, I ran the script, as demonstrated in the video and KB930879, for the specific user account I was using.
2/ Instead of launching the tool’s batch file AFTER I had launched Outlook (as I had interpreted the instructions), I let the batch file launch Outlook.
3/ It probably didn’t matter, but I renamed the extend.dat file EXACTLY as described in the video… to extend.old. Previously I had renamed it to something like extend-old.dat.
Some combination of the above got the tool to run successfully for me. Your mileage may vary.
1/ I had assumed that I had full access because I had given a security group I was a member of full access to the mailbox store. I had no problem accessing everyone’s mailboxes from within Outlook. But just in case, I ran the script, as demonstrated in the video and KB930879, for the specific user account I was using.
2/ Instead of launching the tool’s batch file AFTER I had launched Outlook (as I had interpreted the instructions), I let the batch file launch Outlook.
3/ It probably didn’t matter, but I renamed the extend.dat file EXACTLY as described in the video… to extend.old. Previously I had renamed it to something like extend-old.dat.
Some combination of the above got the tool to run successfully for me. Your mileage may vary.