Re: Idiot.... named new domain same as old nt4 domain (netbios)
From: Joe Wu [MSFT] (joewu_at_online.microsoft.com)
Date: 03/16/04
- Next message: Joe Wu [MSFT]: "RE: NT4 client access to W2K Member server in NT4 Domain"
- Previous message: Herb Martin: "Re: Idiot.... named new domain same as old nt4 domain (netbios)"
- In reply to: Peter: "Re: Idiot.... named new domain same as old nt4 domain (netbios)"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 16 Mar 2004 06:41:11 GMT
Hello Peter,
Thank you for your reply.
I think that you do not need ADMT in this situation. Actually we do not
need to build a new domain from scratch. Instead, I perfer an in-place
upgrade.
To do so, you can perform the following steps:
1) Make a full back up for the current Windows NT domain.
2) Install Windows NT 4.0 BDC on the sever which will be the PDC in the
Windows Server 2003 AD domain. Apply Windows NT SP6a.
3) Promote it to PDC. (Then the original Windows NT PDC will be demoted to
be a BDC automatically.)
4) Make the new PDC and a BDC online, and offline other domain controllers
for recovery purposes.
5) Upgrade the new PDC to Windows Server 2003 domain controller and promote
the domain.
6) Ensure everything works well, you can then make other DCs online, and
consider the migration of other services.
I hope this helps. Thanks and have a great day!
Regards,
Joe Wu
Product Support Services
Microsoft Corporation
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.
--------------------
|From: "Peter" <deadrattie@hotmail.com>
|References: <OptNd6cCEHA.1588@tk2msftngp13.phx.gbl>
<aPZ3L1mCEHA.3552@cpmsftngxa06.phx.gbl>
|Subject: Re: Idiot.... named new domain same as old nt4 domain (netbios)
|Date: Mon, 15 Mar 2004 14:38:12 -0500
|Lines: 106
|X-Priority: 3
|X-MSMail-Priority: Normal
|X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
|X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
|Message-ID: <u$AdLUsCEHA.3256@TK2MSFTNGP09.phx.gbl>
|Newsgroups: microsoft.public.windows.server.migration
|NNTP-Posting-Host: cpe000d880164db-cm014240008905.cpe.net.cable.rogers.com
24.156.150.43
|Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09.phx.gbl
|Xref: cpmsftngxa06.phx.gbl microsoft.public.windows.server.migration:8782
|X-Tomcat-NG: microsoft.public.windows.server.migration
|
|Hi Joe,
|thanks for the reply
|see my posting to Herb, i think i was confused on "when" to use ADMT
|i think i need to run in mixed mode because of an exchange 5.5 server
that's
|not ready to go to w3k. i just want to introduce the new w3k servers and
|start pointing the office users to it for ISA/SUS/anti-virus/print/file
|services etc. then install a new E3k server and then say goodby to nt4.
|
|Peter
|
|
|"Joe Wu [MSFT]" <joewu@online.microsoft.com> wrote in message
|news:aPZ3L1mCEHA.3552@cpmsftngxa06.phx.gbl...
|> Hello Peter,
|>
|> Thank you for your post.
|>
|> I think you do not need to reinstall the NT domain.
|>
|> The underscore "_" character is not a standard character for domain DNS
|> names. Please refer to the following Knowledge Base article:
|>
|> Description of Valid Labels for Domain Name System
|> http://support.microsoft.com/?id=241980
|>
|> However, I think that you can keep the domain with the existing NetBIOS
|> domain name (My_Domain) as NetBIOS name is for legancy applications. In
|> conclusion, it should be OK to use a qualified DNS domain name of
|> my.domain.toronto.local while the domain NetBIOS name is DOMAIN_NAME.
|>
|> Please try the upgrade in your test environment and check all the
|necessary
|> applications in the upgraded test systems to ensure everything will work.
|>
|> If the my.domain.toronto.local (Windows Server 2003 domain) is a separate
|> domain from the current Windows NT domain (my_domain), I think that using
|> ADMT to migrate the domain data is also a good idea. However, you need to
|> upgrade the target domain to native mode first.
|>
|> Thank you for your time and cooperation. If you have any questions or
|> concerns, don't hesitate to let me know. I am standing by to help you.
|Have
|> a great day!
|>
|> Regards,
|> Joe Wu
|> Product Support Services
|> Microsoft Corporation
|>
|> 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.
|>
|> --------------------
|> |From: "Peter" <deadrattie@hotmail.com>
|> |Subject: Idiot.... named new domain same as old nt4 domain (netbios)
|> |Date: Sun, 14 Mar 2004 09:14:09 -0500
|> |Lines: 23
|> |X-Priority: 3
|> |X-MSMail-Priority: Normal
|> |X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
|> |X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
|> |Message-ID: <OptNd6cCEHA.1588@tk2msftngp13.phx.gbl>
|> |Newsgroups: microsoft.public.windows.server.migration
|> |NNTP-Posting-Host:
|cpe000d880164db-cm014240008905.cpe.net.cable.rogers.com
|> 24.156.150.43
|> |Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
|> |Xref: cpmsftngxa06.phx.gbl
microsoft.public.windows.server.migration:8748
|> |X-Tomcat-NG: microsoft.public.windows.server.migration
|> |
|> |Hi all,
|> |
|> |setting up a test evironment for testing migration and setup to new w3k
|> |environment. the nt4 boxes had underscores in the server names and
domain
|> |name.
|> |
|> |i setup my new w3k DC in mixed mode change the server name to my-server,
|> but
|> |left the domain name as my_domain as shown in the netbios name, but the
|w3k
|> |domain name is my.domain.toronto.local
|> |
|> |will ADMT2 work, or is there an easy way to change the netbios name form
|> |my_domain to my-domain
|> |please tell me i don't have to re-install.
|> |
|> |don't care about the old drive mappings and share names using the old
|> |my_server\share method, will write a login script to blow all client
|shares
|> |and printers away and re-setup to new my-server\share format
|> |just want to suck over the accounts and groups
|> |
|> |thanks in advance
|> |Peter
|> |
|> |
|> |
|>
|
|
|
- Next message: Joe Wu [MSFT]: "RE: NT4 client access to W2K Member server in NT4 Domain"
- Previous message: Herb Martin: "Re: Idiot.... named new domain same as old nt4 domain (netbios)"
- In reply to: Peter: "Re: Idiot.... named new domain same as old nt4 domain (netbios)"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
