Hi Jim. I can't speak to your migration plan, as we didn't migrate to a new org, nor use Exmerge to migrate the data.
As to the Exchange updater tool, from my reading of http://support.microsoft.com/kb/930879 Re: "the Exchange tool has to be run off the server, on one mailbox at a time" KB 930879, system requirements section: "The Exchange tool cannot be run on a computer that is running Exchange Server or the Exchange System Management tools." same KB, Risks and limitations section: "MSXTMZ.exe is single threaded.... To speed up the update process for all mailboxes, divide the users into batches, and then run instances of MSXTMZ.exe on separate computers to perform the updates." Re: "Run the Exchange tool on all mailboxes and PFs" same KB, Known Issues section: "The Exchange tool does not update Public Folder calendars. To update a Public Folder calendar, the user must run the Outlook tool in Interactive mode and then manually select the calendar folder to update." We're fortunate to not have any public folder calendars. During the Feb. 2nd webcast there were several questions on this, including one from someone who said their org has 3k+ calendars in public folders. That person asked "Will there be a way to read an input file for rebasing rather than browse to each one separately?" The answer was "No, folders are not the same as mailboxes so you really need to run the Outlook client tool for this case." If you have a lot of public folder calendars, you may want to call Microsoft to ask if they are doing anything more on that issue than they said two weeks ago. - Siobhan Siobhan Jackson Washington State AG's Office Siobhanj ~at~ atg ~dot~ wa ~dot~ gov -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jim Blunt Sent: Friday, February 16, 2007 7:06 PM To: Exchange Discussions Subject: Re: DST - Exchange Updater tool vs Outlook Updater tool James, Either I'm confused, or you are. It sounds in your post, like you are seriously contradicting yourself. First you are saying that the Outloook tool only does one mailbox (on the client) at a time and that the Exchange tool runs the Outlook tool in batch mode. Your last paragraph however says that the Exchange tool has to be run off the server, on one mailbox at a time. Or are you talking about a second Exchange tool that I haven't seen? We are right smack dab in the middle of our Exchange 5.5 --> 2003 migration, so we are going to do the rollout and the migration, all in one fell swoop. We are also going from one Org name to a new Org name, in a native Exchange 2003 environment...starting completely fresh. Because of that, our rollout of the patch is going to look like this: 1. Shut off all user access to the servers and apply the Windows patch. 2. Push the workstation patch to all users. 3. Export all the mailboxes and PFs to .pst files using the ExMerge tool. 4. Import all the mailboxes back into the new system, using ExMerge. 5. Apply the Exchange patch to the Exchange servers. 6. Run the Exchange tool on all mailboxes and PFs Any problems with that scenario anyone? TIA, Jim Blunt AD / Exchange / Anti-Virus Admin ========================== On 2/13/07, Wells, James Arthur <[EMAIL PROTECTED]> wrote: > There is much more to the story, unfortunately. > > See KB 930879. Existing appointments can be fixed one mailbox at a time with an Outlook tool, or you can use the Exchange tool (KB 930879), which basically runs the Outlook tool in a batch mode. Public folder calendars have to be run one at a time. > > The Exchange tool seems to run in 'input' mode to create input files of legacyExchangeDNs, then runs in a 'modify' mode to make intelligent guesses as to time zone and modify the meeting requests and/or appointments in the 'delta' period. > > PSS did imply last week that the OS patch (KB 931836) would release as a non-security critical patch, today. I had expected it on the FOURTH Tuesday, which is generally reserved for such patches...so we'll see. > > The Exchange tool is a pain, though. Without it, any patched client running Outlook (or server with the CDO patch and OWA) will show appointments at the wrong time during the two delta periods -- but the tool is NOT something to just install and run once easily. It must be run OFF the Exchange > server, and can only fix one mailbox calendar at a time. In order to get our environment fixed (about 14,000 mailboxes) within a few DAYS of run time, we'll have at least 10-12 XP machines running the tool simultaneously. > > --James > _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/read/?forum=exchange To subscribe: http://e-newsletters.internet.com/discussionlists.html/ To unsubscribe send a blank email to [EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with.
