Friday, February 16, 2007

Understanding the Exchange DST tool in KB930879

For any of those who are actively working to prepare an Exchange 2003 environment for the 2007 Daylight Saving changes are probably looking at the Microsoft KB article 930879

If you are anyone like me, you might find this KB article a little vague and confusing at points.

Some of the issues I hit were:

  • Exchange tools (Exchange System Manager) were installed on my admin workstations, and had to be uninstalled. (Which also had it's issues, as I found I had to run the setup from the Exchange CD to remove all components from Add/Remove programs. Going to Add/Remove to uninstall would remove the tools, but leave the Exchange server parent entry and prevent the install of the CDO tools.)
  • I missed the mentioning of needing .Net 2 Framework installed, and it took a bit of searching on Google to determine the issue.
  • Lastly, it was not very clear how to format the Server DN name when running MSEXTMZCFG.exe. I stumbled across the correct formatting after examining the MSEXTMZ.ini file. (Silly me, I was using LDAP formatting.)
  • The registry key for Outlook (in my case) needed to be changed to the 11.0 hive from the 12.0 hive.

The Exchange Team blog has a much better
walkthrough on this than the KB article.

Unfortunately, it also brought to my attention the issue with these tools and the Auto Accept Agent for resource mailboxes. The current solution is to painfully unregister each mailbox before running the tool, but at least on Exchange team member says they want be able to come up with another solution.

Good luck!