Re: NT 4.0 to windows 2003 AD in place upgrade.

Thanks for the suggestion, I have that here in my notes. The original
PDC that I make a BDC is the one I will take offline before I do the
upgrade.

However, I think I have a small problem.

I cannot get any of my servers, or Desktops to install WINNT 4.0. So
what I think I am going to do is make my current BDC which is my
Exchange server the PDC, allow to SYNC. After that completes I'll
switch them back take my exchange server offline and do the inplace
upgrade of my PDC. Unless I can get one of these servers or desktops to
install WINNT... not looking promising.


Vincent Xu [MSFT] wrote:
Hi,

The plan is OK. Just one thing. After you bring the new server to PDC
before you upgrade it, you can bring one BDC offline in case the upgrade
failed and you can use it to roll back.

thanks.


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 this issue.
======================================================
This posting is provided "AS IS" with no warranties,and confers no rights.
======================================================



--------------------
From: groff.matthew@xxxxxxxxx
Newsgroups: microsoft.public.windows.server.migration
Subject: NT 4.0 to windows 2003 AD in place upgrade.
Date: 7 Nov 2006 12:14:51 -0800
Organization: http://groups.google.com
Lines: 31
Message-ID: <1162930491.680849.176730@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
NNTP-Posting-Host: 146.145.79.7
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-Trace: posting.google.com 1162930496 27573 127.0.0.1 (7 Nov 2006
20:14:56 GMT)
X-Complaints-To: groups-abuse@xxxxxxxxxx
NNTP-Posting-Date: Tue, 7 Nov 2006 20:14:56 +0000 (UTC)
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET
CLR 1.1.4322; .NET CLR 2.0.50727),gzip(gfe),gzip(gfe)
Complaints-To: groups-abuse@xxxxxxxxxx
Injection-Info: h48g2000cwc.googlegroups.com; posting-host=146.145.79.7;
posting-account=Scr5hg0AAACUi95G5KrueUCVM0AMyUgJ
Path:
TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTFEEDS01.phx.gbl!news-out.c
wix.com!newsfeed.cwix.com!newscon02.news.prodigy.net!prodigy.net!border1.nnt
p.dca.giganews.com!nntp.giganews.com!postnews.google.com!h48g2000cwc.googleg
roups.com!not-for-mail
Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.migration:25396
X-Tomcat-NG: microsoft.public.windows.server.migration

Currently I have an NT 4.0 Domain, PDC and BDC, Exchange 5.5 is running
on my BDC. It is an inherited domain and I have ben charged with the
task of upgrading the Domain to Windows 2003 AD and Exchange 2003. I am
not worried about Exchange right now, I believe that I can handle that
I have everyone's mailboxes backing up to .PSTs nightly.

From what I have read so far here is what I think I should do,
suggestions are welcomed, actually I want lots of suggestions.

1. Build a new NT 4.0 Server using NT4.0 and Windows 2003 compatible
hardware.
2. Make this server a BDC let it sync, made it the PDC again syncing.
3. Upgrade this server to Windows 2003 use windows 2003 interim mode.
4. I have a brand new server ready to be my PDC. Make it a Windows 2003
server, join to domain, DCPROMO and make it the Primary DC.
5. Setup DNS make it AD integrated and do Zone Transfer from Current
DNS server.
6. Remove DNS from old DNS server.
7. We use Script Logic Desktop Authority, so I'll now install this on
new DC and move database from old DC.
8. Use ADMT to move all user accounts, pritners, etc to new DC.
9. DCPromo Interim DC(Desktop machine) from DC role and remove from
domain.
10. After domain is operating smoothly under W2K3, DCPromo other dcs
out.

Next I would start the Exchange migration by building my Exchange 2003
server.

Is there anything I'm missing, any details that might need added?



.

Relevant Pages

  • Re: Splitting Domain Controller & Exchange 2003 from a single server
    ... watch out for this that you keep the "BDC" (Running both Exchange and AD) ... It is also a GC, EXCHANGE 2003 server, File Server, VPN ... XENA - This is just a second domain controller for redundancy. ...
    (microsoft.public.win2000.active_directory)
  • Re: Dringend: Exchange Server durch AD Fehler? ausgefallen ...
    ... aber für Exchange ungemein wichtig ist der Globale ... Ein Server lebt noch, der andere nicht mehr? ... Computer den "BDC" per Hand verbinden? ... > PDC bringt unter anderem einen LDAP Error 31, ...
    (microsoft.public.de.german.exchange2000.general)
  • Migrating from Win 2000 AD and Ex 2000 to Ex 2003 and Win 2003 AD
    ... DC’s and a PDC in five different physical locations. ... are located in the same branch where the core of the network is located (a DC ... We are running Exchange 2000 on the PDC. ... My plan was to install Win 2003 on the new serves and promote that server to ...
    (microsoft.public.exchange.setup)
  • Re: Second Trust
    ... Will the Trust be there when I change my current PDC and make my new ... server a PDC? ... you'll have AD with the NT4 server as a BDC" Why would it be a BDC and ...
    (microsoft.public.win2000.active_directory)
  • Re: FSMO roles and BDC.
    ... It isn't a BDC unless it is running NT rather than Win2000+. ... I know I was using wrong terminology but the DC that has the FSMO roles is a win2k server and the other DC is win2k server and it also has exchange2003. ... To reiterate what herb said, Exchange on a DC, while supported, is NOT considered a best practice. ... Now I've seen some people recommend no more than one GC and others recommend every DC is a GC. ...
    (microsoft.public.windows.server.general)