RE: Single NT4 Domain to W2K3 AD Structure



Hi,

Your plan sounds good.

Please also refer to:
<http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/DepK
it/b170bdc5-ba55-4184-8a8f-acb7705ff04a.mspx>


Best regards,

Vincent Xu
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.

This posting is provided "AS IS" with no warranties, and confers no rights.


--------------------
>>Thread-Topic: Single NT4 Domain to W2K3 AD Structure
>>thread-index: AcX2zFwr2R7E0gA3TYmn2dEn5bIKqQ==
>>X-WBNR-Posting-Host: 80.195.94.102
>>From: "=?Utf-8?B?R2FyeVdyaWdodA==?=" <gwright@xxxxxxxxxxxx>
>>Subject: Single NT4 Domain to W2K3 AD Structure
>>Date: Thu, 1 Dec 2005 15:10:03 -0800
>>Lines: 31
>>Message-ID: <1BAEE1F4-8C9B-4BFA-AE7A-3681D7F23DDE@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: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
>>Xref: TK2MSFTNGXA02.phx.gbl
microsoft.public.windows.server.migration:21542
>>X-Tomcat-NG: microsoft.public.windows.server.migration
>>
>>Hia,
>>
>>Just wanted to run a question passed anyone who has any comments on this.
>>
>>We are currently running a single Windows NT4 domain, with a PDC and two
>>BDC's, two DHCP/DNS/WINS Servers running Windows 2000, several Windows
2K3
>>member servers and approx 300 Windows 2K Pro workstations.
>>
>>We plan to upgrade to a Windows 2003 active directory this weekend (!),
have
>>managed to schedule a whole two days down-time for the entire LAN (which
is
>>all on the same site).
>>
>>I just wanted to check I was doing everything in the correct order, I
plan
>>on taking one of the DHCP/DNS/WINS servers off-line (the one that runs as
a
>>secondary server), then upgrading the primary one to W2K3. Then, once
>>verified that all is OK, adding a BDC to the domain, syncing it, then
>>removing it. After that, upgrading the PDC to W2K3 and running the AD
wizard.
>>Once done, upgrading the two BDC machines. And last of all, putting the
>>DHCP/DNS/WINS secondary server back on-line and upgrading it to Windows
2K3.
>>
>>Does that sound an OK way to do it?
>>
>>Also, I want to make the 2 x DHCP / DNS / WINS server's domain
controllers,
>>therefor reducing the server requirements by two DC's.
>>
>>Any experts got a view on all the above, sorry about the long winded'ness!
>>
>>Thanks in advance for any comments.
>>
>>--
>>Gary
>>

.



Relevant Pages

  • RE: Upgrade Problem
    ... How to Gather Information After a Memory Dump in Windows XP ... If the suggestions do not help, please contact Microsoft Product Support ... | During the final installation stages of upgrading a DC I ... | BSOD for less than one second and then reboots the server ...
    (microsoft.public.windows.server.migration)
  • Re: Migrating Windows 2000 domain to Windows 2003
    ... between 'upgrading' and 'migrating'. ... Upgrading is performed just on the same server. ... and now you want to upgrade this server to Windows 2003 DC. ...
    (microsoft.public.windows.server.migration)
  • RE: Upgrading W2K DC to W2003
    ... Windows Server 2003 DC and keep other Windows 2000 DCs untouched. ... Upgrading W2K DC to W2003 ...
    (microsoft.public.windows.server.migration)
  • Setting up AD - upgrading from NT4 Domain
    ... I have been reading up on the process of upgrading and have found some ... clients 50 n all are running Windows XP. ... installation I have setup a new server as BDC and installed DNS on it. ...
    (microsoft.public.win2000.active_directory)
  • RE: Confirmation of an upgrade plan
    ... If you wound like to upgrade the NT PDC, it will be better that you demote ... it to member server or reinstall it as member server. ... Windows 2003 so that you can join it to the new Windows 2003 domain as DC. ... > I think your plan is valid. ...
    (microsoft.public.windows.server.migration)