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

You have a laptop with a floppy drive? Congratulations! :-)

The admin tools should be there... kinda strange that you're not seeing
them. I believe (can't remember NT4.0 either) you will need Server
Manager (svrmgr.exe from cmd line) to make it the PDC. You shouldn't
need anything else.

I would verify you have Server Manager then shutdown your PDC and
promote the BDC.
Once that is done, upgrade the OS and go with the rest of the steps
mentioned earlier.

You're getting there...


On Nov 9, 2:45 pm, "kemics" <groff.matt...@xxxxxxxxx> wrote:
Ok Just an update, I was able to get NT 4.0 onto my Desktop PC that is
going to be the upgraded PDC for the 2003 AD domain. I was able to make
it a BDC as well... For some reason I couldn't get the NIC drivers to
copy off of a CD that I copied them too, but when I copied them to a
Floppy (barely fit) I was able to install them during the OS install.
So I now have a 3rd NT 4.0 DC which is my second Backup DC. I can see
it listed in Server manager as well...

I have NT 4.0 SP 6.0a on it. That is it, it has nothing installed on
it, no Server Manager, No user manager, Nothing. Do I need to put
anything else on it before I make it the PDC? And if so, where can I
find that stuff online. I've not worked with NT much in my past, I've
done about a dozen 2000 - 2003 upgrades, and those were easy, but NT
4.0 and I don't get along.... I cannot seem to find any kind of extra
service pack disks or anything lying here.

Any help is greatly appreciated.

Thanks!

On Nov 9, 1:30 pm, "Sean Murphy" <s...@xxxxxxxxxx> wrote:



I completely understand.

Obviously if you are having problems getting Windows NT 4.0 Server
installed, you are stuck.

Have you considered Microsoft Virtual Server / Virtual PC or VMWare? I
have found NT install's pretty easily in each of these platforms. It
should afford you at least a temporary solution for your upgrade. As
soon as you have it upgraded and promoted, you could then build and
configure a new Windows Server 2003 DC, transfer the FSMO Roles and
shutdown the VM.

Just a thought...

On Nov 9, 11:13 am, "kemics" <groff.matt...@xxxxxxxxx> wrote:

I understand your point of starting clean, and that would be my
preferred method of action... However, as I said I have inhereted this
domain, the former Network Admin is no longer with the company. Being
that I just stepped in it may take a bit of time before I am 100%
familiar with the domain to know what everyone needs. However, I am
operating on a strict time limit. We currently have Exchange 5.5
Standard, which has a brick wall limit of 16 GIGS for the email
database, currently our database is 14.1 gigs, I estimate at the
current rate of growth the data base will reach a level of 15.9 gigs
BEFORE March.

Also, we have licenses for Citrx MPS 4.0 and have until March to
download this without extending them. So I have a limited amount of
time to get familiar with the environment before upgrading, which is
why INPLACE seemed the best option for me.

However, I have run into problems, I cannot find a PC or Server that
will allow me to install WINNT and join it to the domain. I have one PC
that I am able to get Winnt onto. Unfortunately with this PC the NIC
drivers have to be loaded POST install of the OS. I've been working
with this for a few days. As you may or may not know, during OS install
is the only way to make a Server a DC...

So I have to find a way to get these drivers loaded during the install
so I can immediately have it on the domain.

On Nov 8, 7:28 pm, "Sean Murphy" <s...@xxxxxxxxxx> wrote:

Hi,

First, there is a small problem with your plan. If I understand you
correctly, you are doing an in-place upgrade. Correct? Very simple
and has a lot of advantages.

Personally, I almost never do in-place upgrades. I prefer to build a
nice new pristine environment and migrate to it.

Regardless, if your plan is to upgrade, you need not mention ADMT at
all.

Your plan should be as follows.

1. Build a new NT4.0 BDC (on your Windows Server 2003 compliant
hardware)
2. Shutdown your PDC and stick it somewhere safe.
3. Promote your new BDC to a PDC
4. Upgrade the OS to Windows Server 2003
5. DCPROMO will launch automatically. Step through the wizard to
install AD. Reboot.

** At this point you will now have successfully upgraded your NT4.0
domain to Active Directory

Now all you need to do is retire your NT4.0 domain controllers. You
may want to build additional Windows Server 2003 Domain Controllers
first for redundancy.

Distribute your FSMO roles according to best practices, configure DNS
and you're done!

I think you will find this to be much easier than you expect.

Sean Murphy
Technical Architect
Ensynch, Inc.
Whatever IT Takes

kemics wrote:
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.matt...@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.176...@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-ab...@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-ab...@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.nn­­­­t
p.dca.giganews.com!nntp.giganews.com!postnews.google.com!h48g2000cwc.google­­­­g
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?- Hide quoted text -- Show quoted text -- Hide quoted text -- Show quoted text -- Hide quoted text -- Show quoted text -- Hide quoted text -- Show quoted text -

.

Relevant Pages

  • Re: NT 4.0 to windows 2003 AD in place upgrade.
    ... going to be the upgraded PDC for the 2003 AD domain. ... Floppy I was able to install them during the OS install. ... it, no Server Manager, No user manager, Nothing. ... should afford you at least a temporary solution for your upgrade. ...
    (microsoft.public.windows.server.migration)
  • Re: Upgrade method
    ... you need to upgrade your existing PDC ... To move the PDC to another box, you need to install NT4 ... > Do the two existing Win2k server currently in the domain ...
    (microsoft.public.exchange.setup)
  • Re: Upgrade NT4.0 to 2003
    ... upgrade is to upgrade the NT4 PDC. ... Install Windows Server 2003 on the new box. ...
    (microsoft.public.windows.server.setup)
  • Re: Windows NT4 to Windows 2003 on new box with same domain name
    ... To upgrade you MUST upgrade the PDC of your existing domain first. ... Do you have another "box" that you can install NT 4.0 on it as a BDC, ... Then you can add the "new" Win 2k3 server to the AD domain and transfer the ...
    (microsoft.public.windows.server.migration)
  • Defect in installer for Antivirus Corp Ed 9.0.1.1000 when upgrading from 9.0.0.x
    ... antivirus solution and have Windows XP desktops you'd like to upgrade to XP ... SP2 and wish to have the most recent build of SAV 9 that is XP SP2 compatible. ... to install to servers & PCs to provide XP SP 2 compatibility. ... Once you upgrade your Primary Server to 9.0.1.1000 and attempt to ...
    (NT-Bugtraq)
Loading