1. Depends on what 100% means. I'd want all users migrated before starting Exchange, but it isn't necessary that every file server be moved.
2. I don't like putting Exchange on domain controllers. It makes disaster recovery, future migraton, and maintenance more difficult. You should have at least three domain controllers if your organization is any size, too. Edgar J. Crowley Jr. Technical Consultant Windows & Messaging Platforms Practice hp Services * 510-612-3365 * [EMAIL PROTECTED] -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Miller, Robert Sent: Thursday, September 19, 2002 12:27 PM To: Exchange Discussions Subject: AD & Exchange2K co-existence All, Quick question: We are in the process of rolling out AD, and the Exchange2K upgrade will immediately follow. We are planning on housing Exchange2K on the AD Domain controller, and then retiring both the NT4.0 DC and Exchange 5.5 server (management is all about server consolidation). 1. Would it be wise to wait until AD is 100% deployed and stable before any Exchange upgrades/migrations, or is it safe to do the projects in parallel? 2. If its best to wait for AD to be 100% deployed, would it be feasible to at least get Exchange2K installed on the new AD DC's during the build - and then when we are ready for the Exchange piece to commence all we have to do is the actual migration??? Thanks, _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
