Well, a couple of things - most importantly, we want to maintaine the integrity of BOTH exchange servers. At any moments notice, we want to be able to point a user back to their orignal server and have it work. No data will change on those servers, Secondly, we do not have the money for swing servers - we don't have duplicate hardware of the exchange servers. Thirdly, we aren't exmegring data - we have purchanse NetIQ's Exchange Migrator which is a jewel of a utility. Expensive, but well worth it considering the users senstivity. It will also help us to do live migrations in the middle of the day. Having a parallel (new) org will enable all of this. The reason for avoidance of the ADC is the horror stories I have heard over the years. I have done a few migrations large and small and we always came back down to doing a paralle org and running a migration tool - all to maintain the original exchange environments and never changing anything on them or introducing a fast monster like the ADC. I have already run a "test" lab and there is no real way to truly immatate what we already have in production. Also, you mentioned the x400 addresses - using the exchange migrator, when migrating a user account, it also pulls these old addresses into the ad account so therefore, theoretically, responding to an old email will work. Again, a glitch like ADC can create is not acceptable.
Charlie wrote: What's your reason for wanting to avoid the ADC? If there's a specific reason for you that an org upgrade is bad, then your scenario should work, but it's a lot more work, IMO. My preference would be to migrate the largest or most stable org to E2K3 using new hardware and a swing server. I would then migrate the other org mailboxes into the new org. Reasons? First, the org update is easier on you and the end users; one less set of mailboxes to exmerge as well as one less set of profiles to change. If you create a new org, you are going to run into more user-level issues once done than you will with an org update. For example; users will not be able to reply to any old internal mail that they already have; the x400 addresses won't match. Outlook rules break much better when you create a new org, too. :-) My preference is always to upgrade an org if there are no underlying issues with the org, like naming problems or serious directory issues. I've also found the E2K3 ADC to be pretty solid. Perform your migration in a test lab at least once prior to attempting it in production. You will save lots of time and find all your gotchas that way. ********************** Charlie Kaiser MCSE, CCNA Systems Engineer Essex Credit / Brickwalk 510 595 5083 ********************** > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Steve B > Sent: Monday, October 18, 2004 3:33 PM > To: Exchange Discussions > Subject: RE: need some feedback > > Ok, let me run down what it is we have here. It is quite odd > and I have > never done any type of migration like this. We have two > exchange orgs, each > with one site one server. Each running nt 40 sp6 and one > running ex 5.5 sp3 > and the other running ex 5.5 sp4. They both authenticate to > the same 2000 AD > domain running in mixed mode. The original plan was to > install new hardware > that would replace the sp3 server, running win2k3 and e2k3, > joining it to > the one org and then using exchange migrator to migrate the > accounts off of > the old server in the other org onto the new one. Then using > oprofile to > create the proper templates for the users. Then the sp4 server we were > planning to do the inplace upgrade path e5.5 - e2k - e2k3. > With the events that took place this weekend, I have decided > to propose a > new path (I was not originally for the above path to begin > with). It is just > too dangerous doing these upgrades like this. Some of you > suggested swing > moves. So one of the things we are thinking is getting new > hardware for the > other server and doing it that way. But I want to take it a > step farther. I > want to avoid even using the ADC. I want to place the two new > servers into a > brand new org, and use the exchange migrator and bring over > the accounts. I > feel we can avoid disrupting service, avoid altogether any > kind of issues > that would involve a marathon day of restoring servers and > avoid any issues > with the ADC. > > Please provide some feedback to this idea. > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of > Robert Moir > Sent: Monday, October 18, 2004 9:14 AM > To: Exchange Discussions > Subject: RE: need some feedback > > > I'd make sure I got a good backup before I did anything else, > either way, > and then I'd do a swing upgrade. Move the accounts then wipe > the box and > rebuild once you've moved everything off it. Sure it takes > longer but you've > immediately cut out a lot of potential issues and hiccups. > > ________________________________ > > From: [EMAIL PROTECTED] on behalf > of Steve B > Sent: Mon 18/10/2004 13:52 > To: Exchange Discussions > Subject: need some feedback > > > > Yesterday was a rough day in my exchange world. We tried an > upgrade path > from nt 4.0 exchange 5.5 sp3 to windows 2000. It was on an old compaq > proliant 3000 333mhz 256 megs of ram. > > Windows 2000 installed but upon reboot, we got stop errors. > Eventually, we > went into recovery mode and after about 20 some hours, were > able to recovery > nt4.0 exchange 5.5 with no data loss. We believe the stop > errors were some > out of date drivers, perhaps old hardware on the system. > > What I want feedback on is this. We have another exchange server in a > separate org. It is running on a dual 1ghz with 640 megs of > ram. We were > considering an upgrade from windows nt 4.0 exchange 5.5 sp4 > to windows 2000 > exchange 2000 and then to win2k3 and e2k3. I am very > concerned about doing > this since this is a much bigger server with a much larger IS > and we may not > be so lucky in getting a good recovery. What do you guys > recommend? Is an > upgrade safe or should we think about a new server and then > migrating? Need > everyones thoughts. > > > _________________________________________________________________ > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > Web Interface: > http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&t > ext_mode=&lang > =english > <http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&; > text_mode=<=en > glish> > To unsubscribe send a blank email to %%email.unsub%% > 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/cgi-bin/lyris.pl?enter=exchange&t > ext_mode=&lang > =english > To unsubscribe send a blank email to > %%email.unsub%% > 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/cgi-bin/lyris.pl?enter=exchange&t > ext_mode=&lang=english > To unsubscribe send a blank email to > %%email.unsub%% > 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/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang =english To unsubscribe send a blank email to %%email.unsub%% Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management _________________________________________________________________ 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 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.
