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 t...
Updated Jul 01, 2019
Version 2.0
Blog Post
I've been working with the Exchange update tool on a test system and have come up with a few questions to kind of help my understanding of the workings of the tool itself. For example, what exactly is the Time Zone Extraction process doing? At first, I thought it was extracting the DN's of mailboxes that require updating (i.e. they have calendar events that are incorrect) but I've since come to suspect that it isn't that smart and that all it's doing is creating a list of ALL the recipient DN's on the exchange server, and while it's at it, it tries to provide time zone information for each user...IF it can find it. That sound about right?
When I run the extraction against our server that has roughly 2500 mail boxes, it comes back with 93 in the Output file. None of which are heavy calendar users. All the rest are in the Error file saying it couldn't find any time zone info. If my suspiciouns are correct, that's really no big deal as I can just dump all the DN's from both files into Excel and create a tab delimited file with server and time zone information for each DN. Lucky for me, we're all in the same Time zone.
My other question is about re-sending of meeting requests. What triggers this? I've run the tool a few times in my test environment, against meetings that have attendees, but never saw any extra meeting requests. I admit, though, that I *could* have missed them or thought they were the original meeting request. Still, it would be good to know how this is triggered so we can know how best to forewarn our users.
When I run the extraction against our server that has roughly 2500 mail boxes, it comes back with 93 in the Output file. None of which are heavy calendar users. All the rest are in the Error file saying it couldn't find any time zone info. If my suspiciouns are correct, that's really no big deal as I can just dump all the DN's from both files into Excel and create a tab delimited file with server and time zone information for each DN. Lucky for me, we're all in the same Time zone.
My other question is about re-sending of meeting requests. What triggers this? I've run the tool a few times in my test environment, against meetings that have attendees, but never saw any extra meeting requests. I admit, though, that I *could* have missed them or thought they were the original meeting request. Still, it would be good to know how this is triggered so we can know how best to forewarn our users.