This link specifically mentions the install of Exchange 2007, but the manual procedures for cleaning up an old ADC should be the same:
http://www.exchangelog.info/2007/04/how-to-remove-active-directory.html On Fri, Jan 29, 2010 at 1:57 PM, Brian Desmond <[email protected]>wrote: > *Do you have an old ADC config in AD? I haven’t worked on this stuff in a > long time but you may need to clean that up. * > > * * > > *Thanks,* > > *Brian Desmond* > > *[email protected]* > > * * > > *c – 312.731.3132* > > * * > > *From:* Bill Lambert [mailto:[email protected]] > *Sent:* Friday, January 29, 2010 4:00 PM > > *To:* NT System Admin Issues > *Cc:* MS-Exchange Admin Issues > *Subject:* RE: a little gun shy (also sent to the Exchange list) > > > > Thanks, gents, for the replies and article from Sean. Very helpful. > > > > Now I’m at the point where I am installing E2K3 on the new box. Right > after the licensing agreement page, I get a screen that says “The Microsoft > Exchange Messaging and Collaboration Services component requires a user > name, domain, and password for the existing Exchange 5.5 installation > service account. Type the information in the fields below”. Below that is > a grayed out field for both Username and Domain. The Password is available > but I have no idea what password it wants. If I try to click next without a > password (or a guessed password) I get a window that says “This account > must be valid before continuing”. > > > > I’m adding this server to an org that only has one other *Exchange 2003 > server*. Google didn’t find anything relevant. Any ideas anyone? > > > > Thanks again in advance! > > > > *Bill Lambert* > > *Concuity* > > *Phone 847-941-9206* > > > > *The information contained in this e-mail message, including any attached > files, is intended only for the personal and confidential use of the > recipient(s) named above. If you are not the intended recipient (or > authorized to receive information for the recipient) you are hereby notified > that you have received this communication in error and that any review, > dissemination, distribution, or copying of this message is strictly > prohibited. If you have received this communication in error, please contact > the sender by reply email and delete all copies of this message. Thank you. > *** > > > > *From:* Sean Martin [mailto:[email protected]] > *Sent:* Thursday, January 28, 2010 4:53 PM > *To:* NT System Admin Issues > *Subject:* Re: a little gun shy (also sent to the Exchange list) > > > > Not necessarily a step-by-step guide, but pretty good information: > http://www.amset.info/exchange/migration.asp. > > > > To answer your question, there's no forest/domain prep required. The new > server will automatically join your existing organization. > > > > - Sean > > On Thu, Jan 28, 2010 at 1:07 PM, Bill Lambert <[email protected]> > wrote: > > Hello all… > > > > I have new hardware onto which I want to move my Exchange server. I’m > trying to find specific instructions on this but I’m getting more confused > the more I search. I will be using the move user method; that is, I want to > build the new box in the same org and use the move user wizard to swing the > users over. Then eventually, remove the old server. > > > > I have very basic questions like do I have to run forest and domain prep to > add a server to the org? > > > > I hope someone has a link to a step by step…or good advice. > > > > Thanks a million in advance! > > > > Environment is: > > Existing Exchange 2003 Enterprise is on W2K3 Standard server. This server > is also a domain controller and has Groupshield on it as well. It will > remain a DC. > > > > New server has W2K3 Enterprise and that’s all. It will not be a DC. > > > > > > *Bill Lambert* > > *Windows System Administrator* > > *Concuity* > > *A healthcare division of Trintech, Inc. * > > *Phone 847-941-9206* > > *Fax 847-465-9147* > > *[image: clip_image001]* > > > > > > *NASDAQ: TTPA* > > *The information contained in this e-mail message, including any attached > files, is intended only for the personal and confidential use of the > recipient(s) named above. If you are not the intended recipient (or > authorized to receive information for the recipient) you are hereby notified > that you have received this communication in error and that any review, > dissemination, distribution, or copying of this message is strictly > prohibited. If you have received this communication in error, please contact > the sender by reply email and delete all copies of this message. Thank you. > * > > > > > > > > > > > > > > > > > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
<<image001.gif>>
