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 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Liz Vaibar Sent: Tuesday, February 13, 2007 11:18 AM To: Exchange Discussions Subject: RE: DST - Exchange Updater tool vs Outlook Updater tool Can someone please advise me on this subject, I confused. I was under the impression I could run a Windows patch for my desktop clients, and an Exchange patch and that would resolve the DST issue on the mail server. I am now thinking there is more to the story than meets the eye after reading everyone's posts this week. Am I understanding this correctly? Do I also have to run an Exchange Updater Tool to take care of existing calendar items? The patch I applied to the Exchange Server didn't seem to fix the calendar items that I have already existing in March. Any input would be appreciated! Also...has anyone noticed if the Windows patch was released for the client PC's through WSUS? I cannot seem to find a patch to approve that specifically refers to DST. Thanks! Liz -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Couch, Nate Sent: Tuesday, February 13, 2007 10:03 AM To: Exchange Discussions Subject: RE: DST - Exchange Updater tool vs Outlook Updater tool Robert, I have been testing the Desktop side patch and have found no major issues. The latest OS patch install seemlessly and the TZMOVE.EXE utility is pretty straight forward. All systems, save one, have had no problems, BSODès, or any other issues. The one system that did have a problem came back with an error concerning the Update.inf file along with a reference to the Cryptographic service (which was running as in all other systems tested). I have been scratching my head over that one for several days with no end in sight. All this to say I am not letting this one isntance hinder the rollout since it is just one machine. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Miller, Robert Sent: 13 février 2007 08:49 To: Exchange Discussions Subject: DST - Exchange Updater tool vs Outlook Updater tool All, Currently testing DST updates/patches in the our lab environment... The server OS (2000/2003) and the Exchange update are fairly straightforward... Has anyone tackled Calendar updating - either with the Exchange Updater tool or the client side Outlook Updater tool? If so - which one did you use, and did you have any issues??? Any and all feedback is appreciated... TIA This message may contain confidential and privileged information. If it has been sent to you in error, please reply to advise the sender of the error and then immediately delete this message. Click here or visit www.bakernet.com/disclaimer_bm for other important advice concerning this message. _________________________________________________________________ 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. _________________________________________________________________ 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. _________________________________________________________________ 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. _________________________________________________________________ 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.
_________________________________________________________________ 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.
