Re: nt4.5 to w2003

Hi Vanilla,

keep in mind that there basically is two different things you can do to move from an NT 4 (SAM Database) domain to an Active Directory Domain.

1. You can choose to upgrade the domain from NT 4 to Windows 200x Active Directory.

This option is great if you like the name of your NetBIOS domain name and you just want to upgrade the NT 4 domain to Active directory. The thing to keep in mind here is that you have to Upgrade an NT 4 PDC to Windows 200x. Since most new hardware manufacturers no longer make drivers for Windows NT 4. You could download and install Virtual Server 2005 if you needed to upgrade an NT 4 machine to Windows 200x and your real hardware either does not support NT 4, or the NT 4 hardware you have does not really support Windows 200x.

2. You can Migrate the users and resources from the NT 4 domain to an Active Directory Domain.

This option you create a New Active Directory domain. Then migrate the users over using something like ADMT V3. Basically the only reason to Migrate is that you want to make a fresh break from the old domain structure (i.e. Old NetBIOS Domain Name). If you are happy with the current configuration then you would really want to just Upgrade one of your Windows NT 4 domain controllers to Windows 200x.



You cannot run DCPromo on a 2003 member server in an NT 4 domain to install Active Directory. You will actually be removing yourself from the NT 4 domain and creating a new domain entirely.




--

Rob Greene
Microsoft Enterprise Platforms Support

All postings on this newsgroup are provided "AS IS" with no warranties, and
confer no rights.
For more information please visit
http://www.microsoft.com/info/cpyright.mspx to find terms of use.

"vanilla" <espaul@xxxxxxxxxxxxxx> wrote in message news:1154699972.846644.104830@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I have a very similar situation. Only my database resides on the nt4
domain controller and it uses the Netbios names to authenticate. If I
change the netbios name of the domain; it will break the proprietary
database.
I had planned on adding a new 2003 server as a member server on the NT4
domain and then doing a DCPromo on the the server that I added. Then I
would use the ADMT to migrate the accounts. Will this method work?

Vincent Xu [MSFT] wrote:
Hi George ,

Thanks for posting.

For your situation, it is a good option to perform a restructure of current
domain. That is mean, you should migrate all objects in current domain to a
new settled domain. Please refer to following link for some concept:

<ttp://technet2.microsoft.com/WindowsServer/en/library/7c829c8b-e944-49f2-9f
20-004685aa86321033.mspx?mfr=true>

For detail, you can use a tool called ADMT which is included in Windows
server 2003. Please check following article:

How to set up ADMT for Windows NT 4.0 to Windows 2000 migration
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q260871

Let me know if you still have any concerns.

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: George Applegate <gappleg8@xxxxxxxxxx>
>>Subject: nt4.5 to w2003
>>Date: Thu, 03 Aug 2006 07:40:50 -0500
>>Message-ID: <e7r3d2pm4qjdb82ktboe2tshtv1akpfr58@xxxxxxx>
>>X-Newsreader: Forte Agent 1.91/32.564
>>MIME-Version: 1.0
>>Content-Type: text/plain; charset=us-ascii
>>Content-Transfer-Encoding: 7bit
>>Newsgroups: microsoft.public.windows.server.migration
>>NNTP-Posting-Host: cmodem51.harlannet.com 207.177.43.51
>>Lines: 1
>>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP06.phx.gbl
>>Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.migration:24705
>>X-Tomcat-NG: microsoft.public.windows.server.migration
>>
>>I'm sure this has probably been covered before, but I'll pray that
>>someone is kind enough to read this and make some suggestions.
>>
>>I am replacing an nt4.5 server with a new windows 2003 server. The
>>server is modest, only 10-15 users, mostly file serving in function.
>>It does have a database in sql on the nt 4.5 box.
>>
>>The domain on the old server is for illustration purposes, "JOE".
>>Since I am replacing old server with new, I was going to leave the
>>domain name the same but someone told me that would be a mistake, and
>>said the new domain should use the real email domain (we don't host
>>our own email) anyway, the new server is going to be, for illustration
>>purposes, "JOHN".
>>
>>As I understand it, all my pc's will have to be rejoined to the new
>>domain and have desktops, etc all migrated and printers reinstalled.
>>No problem, I can handle that.
>>
>>However, here is my issue, I think. On the old NT box we have a
>>database. I want to migrate that database from the JOE domain to the
>>JOHN domain. Can I do that, and if so, how do I do that??? Should I
>>have named my new server domain the same as the old one, JOE, to have
>>simplified the process??
>>
>>As I understand it, even had I done that, I'd still ahve to migrate
>>desktops and settings on each individual pc anyway, because it doesn't
>>really recognize the domain "JOE" because the servers are different
>>systems??
>>
>>Anyway, we have a few places that use this database that's on the old
>>server and I am wondering how I get it to the new server and
>>functioning. If the database was called "BOB" on the old server, can
>>I call it "BOB" on the new server and simply migrate it somehow???
>>
>>I can make everything else work I think as I said, I created the users
>>over again, since only 10-15 users...but I am stumped on how I have to
>>handle the sql and database "BOB". I would appreciate any
>>suggestions, tips, references to material I could read that deal with
>>this, etc.
>>
>>Thanks in advance,
>>ga
>>George Applegate
>>gappleg8@xxxxxxxxx
>>


.

Relevant Pages

  • Re: 2003 Migration
    ... Best Practice Active Directory Design for Managing Windows Networks ... Windows Server 2003 Tools ... ensure that you have designed a DNS and Active ...
    (microsoft.public.windows.server.active_directory)
  • Re: i got 6 server in company which contains NT4 , windows 2000 , windowser 2003
    ... Best Practice Active Directory Design for Managing Windows Networks ... Windows Server 2003 Tools ... ensure that you have designed a DNS and Active ...
    (microsoft.public.windows.server.active_directory)
  • Re: Urgent Advise - [WildPacket]
    ... Best Practice Active Directory Design for Managing Windows Networks ... Windows Server 2003 Tools ... ensure that you have designed a DNS and Active ...
    (microsoft.public.windows.server.active_directory)
  • Re: NTDS ISAM DataBase Corruption
    ... Did you tried the recover the corrupted Active Directory process that a gave ... This is brand new IBM Server. ... using symantec livestate recovery. ... Active Directory database is unavailable because it is damaged, ...
    (microsoft.public.windows.server.active_directory)
  • Re: NT to W2K3 Migration
    ... How to Upgrade from Windows NT Server 4.0 ... Best Practice Active Directory Design for Managing Windows Networks ...
    (microsoft.public.windows.server.active_directory)