RE: 2000 -> 2003 Upgrade

Tech-Archive recommends: Fix windows errors by optimizing your registry



Amanda,

Thank you for your help, We have had issues with all 4 domain controllers
with nic teaming, I have uninstalled it on all 4, but 2 of them it wasn't
clean, but thank you for your advice we will start with the PDC first and do
an upgrade vs a fresh install, I will leave the fresh install for the last to
be completed. My thought is to do one a week, since we have a large
enviorment, (28,000 users & 40,000 Wkstations) I don't want to stir up to
much activity.

Regards and Thank you for your help,
Bob Smith

"Amanda Wang [MSFT]" wrote:

> Hello,
>
> Thanks for your post.
>
> I understand you are planning on moving the 4 Domain controllers to Windows
> 2003 and you still have the following two concerns:
>
> 1. Does it matter with DC I start with: ex. PDC emulator, my thought was to
> start with the server with the least roles.
>
> Please upgrade PDC first.
>
> 2. I am doing a fresh install due to issues I have experienced with the DC,
> a previous admin install nic teaming which seemed to causing problems with
> AD & DNS and the uninstall was not clean so I have had problems with this
> and other DC's, so a fresh build will help clean problems up with the
> server, any issues with my planned rebuild that anyone may have experienced.
>
>
> Based on this question, first, please help me to confirm do you mean there
> is one Win2k DC is corrupted and you want to do a fresh install?
>
> If so, of course you can first demote this DC, remove it from network and
> perform a fresh install of Win2k3 Server system. After all the other DCs
> have finished upgrade, you can add new Win2k3 machine into new Win2k3
> domain and promote it to be a DC.
>
> For more references related how to upgrade from Win2k to Win2k3:
>
> 325379 How to Upgrade Windows 2000 Domain Controllers to Windows Server 2003
> http://support.microsoft.com/?id=325379
>
> Upgrading from Windows 2000 Server to Windows Server 2003
> http://www.microsoft.com/windowsserver2003/evaluation/whyupgrade/win2k/w2kto
> ws03-2.mspx
>
> HTH!
>
> Thanks & Regards
>
> Amanda Wang [MSFT]
>
> Microsoft Online Partner Support
>
> Get Secure! - www.microsoft.com/security
>
> ====================================================================
>
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
>
> =====================================================================
>
> --------------------
> >Thread-Topic: 2000 -> 2003 Upgrade
> >thread-index: AcVw9s8YqxVmTFgsSLOoUboIjRa8fw==
> >X-WBNR-Posting-Host: 136.167.17.94
> >From: =?Utf-8?B?Qm9iIFNtaXRo?= <BobSmith@xxxxxxxxxxxxxxxxxxxxxxxxx>
> >Subject: 2000 -> 2003 Upgrade
> >Date: Tue, 14 Jun 2005 08:36:18 -0700
> >Lines: 17
> >Message-ID: <BFAF95F7-7903-4C6A-A638-D45B9E96DF8C@xxxxxxxxxxxxx>
> >MIME-Version: 1.0
> >Content-Type: text/plain;
> > charset="Utf-8"
> >Content-Transfer-Encoding: 7bit
> >X-Newsreader: Microsoft CDO for Windows 2000
> >Content-Class: urn:content-classes:message
> >Importance: normal
> >Priority: normal
> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> >Newsgroups: microsoft.public.windows.server.migration
> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> >Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> >Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.migration:10648
> >X-Tomcat-NG: microsoft.public.windows.server.migration
> >
> >I am planning on moving my 4 Domain controllers to Windows 2003 start next
> >week, I have read most of the posts concerning upgrading/new installing so
> I
> >feel I am all set, but I wanted to double check on a couple of items;
> >
> >My plan was to demote a domain controller and do a fresh build then re-add
> >
> >1. Does it matter with DC I start with: ex. PDC emulator, my thought was
> to
> >start with the server with the least roles.
> >
> >2. I am doing a fresh install due to issues I have experienced with the
> the
> >DC, a previous admin install nic teaming which seemed to causing problems
> >with AD & DNS and the uninstall was not clean so I have had problems with
> >this and other DC's, so a fresh build will help clean problems up with the
> >server, any issues with my planned rebuild that anyone may have
> experienced.
> >
> >Thank you for any assistance,
> >Bob Smith
> >
>
>
.



Relevant Pages

  • RE: 2000 -> 2003 Upgrade
    ... Microsoft CDO for Windows 2000 ... >an upgrade vs a fresh install, I will leave the fresh install for the last ... >> start with the server with the least roles. ... >> Please upgrade PDC first. ...
    (microsoft.public.windows.server.migration)
  • Re: Windows 2000 and 2003 DC in one environment
    ... don't have to upgrade both Domain Controllers, ... Exchange 2000 can't run at Windows Server 2003. ... have a mix of Windows2000 Domain Controllers and Windows Server 2003 are not ...
    (microsoft.public.windows.server.active_directory)
  • RE: In-place upgrade from NT to 2003, member server question
    ... I understand you after in place upgrade from WinNT to Win2k3, ... use Windows Server 2003 interim Functional Level. ... sufficient Windows 2k3 domain controllers, ...
    (microsoft.public.windows.server.migration)
  • Re: AD Upgrade
    ... domain controllers do have read and write copy of .DIT database meaning they ... install all fresh drives and the windows 2003, patch it and DCpromo in, one ... Security+, Project +, Server + ... dc server and choose upgrade. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Replacing Win2000 Domain controllers
    ... -Even if you have removed exchange, the Schema upgrade can be a problem, that can be fixed/checked: ... should be moved to computers container if correctly done and you can delete it there (ONLY in computers container NOT in Domain controllers OU) and remove it from the network ... now you can use name and ip from old dc1 for new server and if it is promoted move the 5 FSMO roles, ... On the old server open DNS management console and check that you ...
    (microsoft.public.windows.server.migration)