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)
We are find that there are a high percentage of our user mailboxes ending up in the NonExistent.txt file. Additionally, we have found that the time zone extraction is taking a very long time - 11 hours for some servers.
We are considering creating a script to extract the Legacy Exchange DN, Exchange Server and Time Zone from Active Directory. We would use our location fields from Active Directory to map to the appropriate Time Zone and would still create a seperate file per server.
This process would also make it easier to strip out our inactive/disabled users and would be much faster than performing the extracts.
Are we missing anything that would result in this method of extraction causing us problems?
We are considering creating a script to extract the Legacy Exchange DN, Exchange Server and Time Zone from Active Directory. We would use our location fields from Active Directory to map to the appropriate Time Zone and would still create a seperate file per server.
This process would also make it easier to strip out our inactive/disabled users and would be much faster than performing the extracts.
Are we missing anything that would result in this method of extraction causing us problems?