An in place upgrade is the least desirable of all potential upgrade methodologies. I'd suggest a swing upgrade[1] unless there is no other mechanism available. What's the burning desire to get the Exchange migration completed so quickly on the heels of your as of yet unconfirmed successful W2K migration[2].
[1] And perhaps a good Exchange consultant. [2] When AD coughs, Exchange catches a cold. [3] [3] If AD aint right, your Exchange environment will be even less so. On 08/04/03 07:35, "Bridges, Samantha" <[EMAIL PROTECTED]> wrote: > Hello All. > > I will be upgrading my Exchange 5.5 to 2000 this weekend. I studied the > Microsoft White Paper on doing an In-Place Upgrade of Exchange and > understand that during the preparation of the Exchange 5.5 Organization, > there are utilities/diagnostic tools that need to be run. For instance, the > NTDSATRB to find mis-matches and MTACheck and the KCC. Can these tools be > run before the actual upgrade or should I wait until the weekend and do the > whole thing at once? > > Can utilities like NLTEST /switch, and the ADC w/Connection Agreements, > /ForestPrep and /DomainPrep be run during the week before the actual > upgrade? > > What can I do during the week that won't hinder services yet give me a > "jump" on the actual upgrade this weekend. > > What things were you able to run/fix before the actual upgrade? > > Thanks > > Samantha > _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
