Great Stuff, I wish there was some sort of white paper with a check list to guide one through the process. Like Upgrade member servers first before DC's. How straightforward is the process, and what to watch out for. "Herchenbach, Jim" <jherchenbach@xxxxxxxxxx> wrote: you want to upgrade your exchange first because exchange 2003 has been tested on the 2000 platform, but exchange 2000, from what I have been told may not work correctly on a 2003 platform. JIM HERCHENBACH RVW Inc. --------------------------------- From: windows2000-bounce@xxxxxxxxxxxxx [mailto:windows2000-bounce@xxxxxxxxxxxxx] On Behalf Of Dave stevens Sent: Thursday, November 10, 2005 3:44 AM To: windows2000@xxxxxxxxxxxxx Subject: [windows2000] Re: Windows 2000 domain upgrade Thanks Ken, Great advice. Any white papers on this? So my understanding is that you upgrade your DC's first, before your file servers. Again would it be better to upgrade exchange 2000 to 2003 before upgrading the base OS. Not quite sure which comes first. Thanks Dave "Leitman, Ken" <ken.leitman@xxxxxxxx> wrote: @font-face { font-family: Wingdings;}@font-face { font-family: Tahoma;}@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }P.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"}LI.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"}DIV.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"}A:link { COLOR: blue; TEXT-DECORATION: underline}SPAN.MsoHyperlink { COLOR: blue; TEXT-DECORATION: underline}A:visited { COLOR: blue; TEXT-DECORATION: underline}SPAN.MsoHyperlinkFollowed { COLOR: blue; TEXT-DECORATION: underline}P { FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: "Times New Roman"}SPAN.EmailStyle18 { COLOR: navy; FONT-FAMILY: Arial}SPAN.EmailStyle19 { COLOR: navy; FONT-FAMILY: Arial}DIV.Section1 { page: Section1}OL { MARGIN-BOTTOM: 0in}UL { MARGIN-BOTTOM: 0in} 1) you must go to Windows 2003 SP1 for your DCs. 2) If you have remote offices with DCs check rpc settings for timeouts, we did have some issues with this setting being changed with SP1 3) Verify all hardware drivers with SP1 before you roll it out, some video and other drivers MUST be upgraded, this was our biggest issue and we had issues with SCSI, video and network cards 4) Start simple with local FSMO servers and make sure you have a plan in place to move roles around We did all of our 54 DCs in about three weeks. Without SP1 we ran into all sorts of crazy issues, even with all of our testing. We use HP servers, but we have seen the same driver problems on eval IBM and Dell servers when applying SP1 Remove any third party software you can before any server upgrades, by removing the monitoring, AV and backup software, we were able to script an in place upgrade from W2K to W2K3. Plan, test, plan some more and good luck, thankfully this is less complex than Nt4 à W2K, or initial AD design/implementation, kl --------------------------------- From: windows2000-bounce@xxxxxxxxxxxxx [mailto:windows2000-bounce@xxxxxxxxxxxxx] On Behalf Of Joanne Determann Sent: Wednesday, November 09, 2005 12:00 PM To: windows2000@xxxxxxxxxxxxx Subject: [windows2000] Re: Windows 2000 domain upgrade First thing I did was determine the compatibly of all my apps and programs. (Although my Websense DC agent doesn?t work now even though their support insisted it was 2003 compatible.) Then I made a spread sheet ?server plan? . what server does what and how it was gonna move things around during the upgrade. Now it?s in MS project timeline. My DC?s are done, Terminal Servers ( licensing is a biggy),backup and one webserver are complete Doing Exchange next week. --------------------------------- From: Dave stevens [mailto:london31uk@xxxxxxxxx] Sent: Wednesday, November 09, 2005 11:53 AM To: windows2000@xxxxxxxxxxxxx Subject: [windows2000] Windows 2000 domain upgrade Hi Guys, I have just been tasked with comming up with a detailed plan for our 2000 domain upgrade to 2003. Does anyone have any tips / whitepapers that would help. Currently it is a single domain, multiple sites setup we have. Any suggestions would be helpful. Thanks Dave --------------------------------- Yahoo! FareChase - Search multiple travel sites in one click. ----------------------------------------- The information contained in this transmission may be privileged and confidential and is intended only for the use of the person(s) named above. If you are not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, any review, dissemination, distribution or duplication of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender immediately by reply e-mail and destroy all copies of the original message. Please note that we do not accept account orders an d/or instructions by e-mail, and therefore will not be responsible for carrying out such orders and/or instructions. If you, as the intended recipient of this message, the purpose of which is to inform and update our clients, prospects and consultants of developments relating to our services and products, would not like to receive further e-mail correspondence from the sender, please "reply" to the sender indicating your wishes. In the U.S.: 1345 Avenue of the Americas, New York, NY 10105. --------------------------------- Yahoo! FareChase - Search multiple travel sites in one click. --------------------------------- Yahoo! FareChase - Search multiple travel sites in one click.