Upgrading without testing isn't something I would do... Well, I might do it[1] since I've already done of couple of E2K migrations in the past. E2K3 has simplified a number of things, making the upgrade process more intuitive and less risky.[3] Still, understanding what the process is by actually attempting to complete each step in a lab, even if it's a VMWare instance or two on your desktop, is prudent and reasonable.[4]
BTW, there is no schema for your domain. There is a schema for the entire forest and the changes you make regarding Exchange to the schema will have effects on everyone else in your forest. No idea what the scope of your forest is, but just wanted to make sure you were aware of what the minor implications of that might be (like there can only be one Exchange org per forest). Oh, and in-place upgrades are the riskiest possible upgrades. I'd highly recommend against such a path even if you do get around to testing.[5] [1] If I still did E2K migrations.[2] [2] Which don't. [3] Which is part of the reason I only do those now. [4] If you don't have the money or time to test implementing E2K, then I can guarantee you don't have the time or money to troubleshoot and fix a broken install. [5] Another reason I like E2K3, since it doesn't allow in place upgrades. > From: Matt Hoffman <[EMAIL PROTECTED]> > Reply-To: "Exchange Discussions" <[EMAIL PROTECTED]> > Date: Mon, 11 Aug 2003 14:43:06 -0400 > To: "Exchange Discussions" <[EMAIL PROTECTED]> > Subject: RE: Upgrade from Exchange 5.5 SP4 to Exch. 2000 > > Well, these things are a matter of money and time. Money for a test lab and > a new copy of Exchange. We purchased E2K a while ago and have not had the > AD environment to install it in until recently. It's what we bought, so > it's what we're using... Off the top of your head, does E2K3 need to be in > a Win2K3 AD or can it run in a Win2K AD? > > -----Original Message----- > From: Chris Scharff [mailto:[EMAIL PROTECTED] > Sent: Monday, August 11, 2003 2:30 PM > To: Exchange Discussions > Subject: Re: Upgrade from Exchange 5.5 SP4 to Exch. 2000 > > > That's why test labs rock... And in addition to just reading the E2K3 help, > I'd strongly recommend migration to it over E2K. > >> From: Matt Hoffman <[EMAIL PROTECTED]> >> Reply-To: "Exchange Discussions" <[EMAIL PROTECTED]> >> Date: Mon, 11 Aug 2003 12:37:33 -0400 >> To: "Exchange Discussions" <[EMAIL PROTECTED]> >> Subject: RE: Upgrade from Exchange 5.5 SP4 to Exch. 2000 >> >> OK, wonderful. That will be a big help. Of course I understand that >> whitepapers are written to be the guides to a correct installation. >> However, my experiences have told me that you're much better off >> verifying that the information in such a document is correct first >> before trusting it completely. I've had too many such instructions >> leave out some critical component that meant many more hours of hassle >> instead of a nice clean install. >> >> Matt >> >> -----Original Message----- >> From: Peter Orlowski [mailto:[EMAIL PROTECTED] >> Sent: Monday, August 11, 2003 11:59 AM >> To: Exchange Discussions >> Subject: RE: Upgrade from Exchange 5.5 SP4 to Exch. 2000 >> >> >> Have a look at the Exchange 2003 help. They have a step by step >> walkthrough of all the upgrade/migration paths. Its basically a >> stripped down version of whats in the whitepapers but its layed out >> like a checklist. >> >> These whitepapers are not "junk". Understanding then can mean the >> difference between a failed or successful upgrade. >> >> - Peter >> >> >> >> -----Original Message----- >> From: Matt Hoffman [mailto:[EMAIL PROTECTED] >> Sent: Monday, August 11, 2003 8:49 AM >> To: Exchange Discussions >> Subject: Upgrade from Exchange 5.5 SP4 to Exch. 2000 >> >> I'm beginning the process of an in-place upgrade from Exchange 5.5 SP4 >> to Exchange 2000, and I wanted to make sure I had the right ideas >> about how to go about this. >> >> 1. I downloaded the In-Place Upgrade Whitepaper from Microsoft. Is >> this a definitive document or is there something in the document that >> is, in your experience, junk? I'd hate to follow this and find out MS >> has something wrong... >> >> 2. The server that 5.5 currently resides on is Windows 2000, SP 3, >> and is in an NT 4.0 domain at the moment. I assume I need to bring it >> into the AD before I can begin this upgrade process? Should I do this >> only if I want to avoid having to use the ASD connectors? I'm a bit >> confused on this point. >> >> 3. I'm trying to get my AD administrators to allow my domain admins >> to have the ability to update the schema (for my domain at least). I >> realize we need this, at least according to this whitepaper and the >> list FAQ. >> >> 4. My domain is already in native mode, so that isn't a problem. >> I've also transferred all the old user accounts from my NT 4.0 domain >> over using the migration wizard, so the SID's should be the same for >> the accounts when the users attempt to access their mailboxes after >> the upgrade. >> >> 5. I'm planning on doing a full online backup before doing anything, >> of course. >> >> I'm doing my best to read through all the information I can find on >> this topic, but there are often things that are missing from such >> documents. >> >> Is there anything obviously wrong with what I've talked about above? >> Any specific pointers to give on this process? >> >> Thank you very much, >> >> Matt _________________________________________________________________ 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]
