RE: NT4 server and W2K3
From: Joe Wu [MSFT] (joewu_at_online.microsoft.com)
Date: 03/01/04
- Next message: Joe Wu [MSFT]: "RE: Migration tools question"
- Previous message: Joe Wu [MSFT]: "RE: NT to W2k3 fears and questions"
- Next in thread: Lance: "RE: NT4 server and W2K3"
- Reply: Lance: "RE: NT4 server and W2K3"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 01 Mar 2004 15:01:13 GMT
Hello Lance,
Thank you for your post.
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 upgrade the domain with the existing NetBIOS
domain name ("ABC_domain") as NetBIOS name is for legancy applications.
When promoting the AD-based domain, please choose a qualified DNS domain
name that does not contain an underscore.
In conclusion, it should be OK to set DNS domain name to DOMAINNAME.LOCAL
while the domain NetBIOS
name is "ABC_domain".
A good idea is to try the upgrade in your test environment and check all
the necessary applications in the new domain environment to ensure
everything will work correctly.
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.
--------------------
|Content-Class: urn:content-classes:message
|From: "Lance" <fuel451@hotmail.com>
|Sender: "Lance" <fuel451@hotmail.com>
|References: <017301c3fcd0$674d6b70$a601280a@phx.gbl>
<jI8PmvQ$DHA.3712@cpmsftngxa06.phx.gbl>
|Subject: RE: NT4 server and W2K3
|Date: Fri, 27 Feb 2004 07:01:40 -0800
|Lines: 257
|Message-ID: <317501c3fd42$9b3449f0$a501280a@phx.gbl>
|MIME-Version: 1.0
|Content-Type: text/plain;
| charset="iso-8859-1"
|Content-Transfer-Encoding: 7bit
|X-Newsreader: Microsoft CDO for Windows 2000
|X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
|Thread-Index: AcP9QpsxJb67MK1TTeOYFkgiEC4IRA==
|Newsgroups: microsoft.public.windows.server.migration
|Path: cpmsftngxa06.phx.gbl
|Xref: cpmsftngxa06.phx.gbl microsoft.public.windows.server.migration:8317
|NNTP-Posting-Host: tk2msftngxa13.phx.gbl 10.40.1.165
|X-Tomcat-NG: microsoft.public.windows.server.migration
|
|Joe,
|
|First, thank you. The response was very to the point and
|informative. I have a very similar situation. Only one
|Windows NT 4.0 server (PDC) on the network and about six
|to eight Windows XP Pro clients. The client would like to
|purchase a new Windows 2003 server and make it the DC.
|
|My question is this. The domain name is "ABC_domain".
|Will this pose a problem? Also, they are pushing to
|purchase a Dell srever with Windows 2003 Server
|preinstalled. What can you recommend for that scenario?
|
|Thanks,
|
|Lance
|>-----Original Message-----
|>Hello John,
|>
|>Thank you for your post.
|>
|>My name is Joe Wu, and it is my pleasure to work with you
|on this issue.
|>
|>I would like to confirm my understanding of the issue:
|You would like to
|>upgrade the domain and replace the current Windows NT 4.0
|PDC with a
|>Windows Server 2003 DC.
|>
|>I would like to suggest that you perform an upgrade
|instead of a migration.
|>In this way, we do not need to migrate the domain
|accounts and client
|>machines, so it is a more simple and efficient solution.
|>
|>Analysis and Suggestions:
|>-----------------------------
|>
|>1. I would like to suggest that you use the following
|upgrade steps:
|>
|>1.1) Make a full back up for the current Windows NT
|domain.
|>
|>1.2) Install Windows NT 4.0 BDC on the sever which will
|be the PDC in the
|>Windows 2003 AD domain.
|>
|>1.3) Promote the BDC to PDC. (Then the original PDC will
|be demoted to be a
|>BDC automatically.)
|>
|>1.4) If possible, make a BDC offline for recovery
|purposes.
|>
|>1.5) Upgrade the new PDC to Windows 2003 domain
|controller and promote the
|>domain.
|>
|>1.6) Ensure everything works well, you can then make the
|BDC online, and
|>move files and services to the new server.
|>
|>Actually this are the commonly used method for upgrade
|from a Windows NT
|>domain to Windows 2000/2003 domain.
|>
|>In addition, Windows NT domains are quite different from
|Windows 2000/2003
|>AD-based domain, I would like to provide more documents
|and suggestion
|>below for your reference:
|>
|>2. Useful information for upgrade from Windows NT domain
|to Windows 2000
|>domain:
|>
|>Restructuring Windows NT 4.0 Domains to an Active
|Directory Forest
|>http://www.microsoft.com/technet/treeview/default.asp?
|url=/technet/prodtechn
|>ol/windowsserver2003/proddocs/deployguide/dssbh_rera_usbf.
|asp
|>
|>Microsoft Windows Server 2003 Deployment Kit
|>http://www.microsoft.com/technet/treeview/default.asp?
|url=/technet/prodtechn
|>ol/windowsserver2003/proddocs/deployguide/default.asp
|>
|>Migrating Windows NT Server 4.0 Domains to Windows Server
|2003 Active
|>Directory
|>http://www.microsoft.com/windowsserver2003/evaluation/whyu
|pgrade/nt4/nt4domt
|>oad.mspx
|>
|>Domain Migration Cookbook
|>http://www.microsoft.com/technet/treeview/default.asp?
|url=/technet/prodtechn
|>ol/windows2000serv/deploy/cookbook/cookintr.asp
|>
|>Upgrading from Windows NT Server 4.0 to Windows Server
|2003
|>http://www.microsoft.com/windowsserver2003/evaluation/whyu
|pgrade/nt4/nt4tows
|>03-2.mspx
|>
|>Windows NT Server 4.0 Upgrade Guide
|>http://www.microsoft.com/windowsserver2003/partners/isvs/n
|tmigrate.mspx
|>
|>326209 HOW TO: Upgrade a Windows NT 4.0-Based PDC to a
|Windows Server 2003
|>http://support.microsoft.com/?id=326209
|>
|>3. Two more suggestions:
|>
|>3.1) Pay Attention To DNS:
|>
|>Windows 2000/2003 AD domains need DNS for name
|resolution. We have
|>encountered many problems which were finally proved to be
|DNS issues. It is
|>important that we pay more attention to DNS when
|upgrading from Windows NT
|>domain.
|>
|>Reference:
|>
|>291382 Frequently Asked Questions About Windows 2000 DNS
|and Windows Server
|>http://support.microsoft.com/?id=291382
|>
|>Troubleshooting Common Active Directory Setup Issues in
|Windows 2000
|>http://support.microsoft.com/default.aspx?scid=kb;EN-
|US;260371
|>
|>How Domain Controllers Are Located in Windows
|>http://support.microsoft.com/default.aspx?scid=kb;EN-
|US;260371
|>
|>3.2) Pay Attention To Domain DNS Name Choosing
|>
|>3.2.1) Never Use Single Label Domain DNS Name
|>
|>During the upgrade, you will be prompted to choose a DNS
|name for the
|>domain. Please keep it in mind that we should NOT use a
|Single-Lable DNS
|>name (no "." in the domain DNS name). For example,
|using "MYDOMAIN" as the
|>new domain's DNS name is not a good idea.
|>
|>Reference:
|>
|>300684 Information About Configuring Windows 2000 for
|Domains With
|>Single-Label
|>http://support.microsoft.com/default.aspx?scid=kb;EN-
|US;300684
|>
|>3.2.2) Use Different Internal and External Domain Names
|>
|>It is recommended that we use different internal and
|external domain names.
|>This creates a barrier between your internal resources
|and the Internet,
|>and you will gain the following advantages:
|>
|>- The internal namespace is not registered with Internic.
|Internal
|>resources are not exposed.
|>- Proxy clients need to exclude only the external
|namespace, which allows
|>any external DNS queries to the Internet to proceed
|through the Proxy
|>Server.
|>
|>Reference:
|>
|>285983 Considerations for Designing Namespaces in Windows
|2000-Based Domain
|>http://support.microsoft.com/?id=285983
|>
|>Thank you for reading this long post. I hope it helps you
|smoothly upgrade
|>your domain. If you encounter any upgrade issue on the
|system side, please
|>do not hesitate to let us know here. I will be happy to
|be of further
|>assistance. Thanks!
|>
|>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.
|>
|>--------------------
|>|Content-Class: urn:content-classes:message
|>|From: "John" <anonymous@discussions.microsoft.com>
|>|Sender: "John" <anonymous@discussions.microsoft.com>
|>|Subject: NT4 server and W2K3
|>|Date: Thu, 26 Feb 2004 17:24:11 -0800
|>|Lines: 18
|>|Message-ID: <017301c3fcd0$674d6b70$a601280a@phx.gbl>
|>|MIME-Version: 1.0
|>|Content-Type: text/plain;
|>| charset="iso-8859-1"
|>|Content-Transfer-Encoding: 7bit
|>|X-Newsreader: Microsoft CDO for Windows 2000
|>|X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
|>|Thread-Index: AcP80GdNHbYGcUL4RKOFuEbGkUiwHQ==
|>|Newsgroups: microsoft.public.windows.server.migration
|>|Path: cpmsftngxa06.phx.gbl
|>|Xref: cpmsftngxa06.phx.gbl
|microsoft.public.windows.server.migration:8301
|>|NNTP-Posting-Host: tk2msftngxa14.phx.gbl 10.40.1.166
|>|X-Tomcat-NG: microsoft.public.windows.server.migration
|>|
|>|Hello.
|>|
|>|I will be physically replacing a PDC NT server with a
|new
|>|machine running W2K3 in a company with 20 users. What
|is
|>|the best practice to tranfer the users and security from
|>|the old to the new? Once I logon to the domain as a
|>|domain admin with the W2K3 machine I can tranfer the
|data
|>|from old to new, but when do I install active directory
|>|and upgrade the W2K3 machine to the new PDC and finally
|>|take the NT server off the network? I've read the posts
|>|regarding the ADMT and the problems run into, but this
|>|network seems much simpler at first glance. Obviously I
|>|will keep the directory structure of the data the same.
|>|All 20 workstations are running W2K professional and I
|>|would like to keep work on each individual workstaion at
|a
|>|minimum, if at all.
|>|
|>|Thank You.
|>|
|>
|>.
|>
|
- Next message: Joe Wu [MSFT]: "RE: Migration tools question"
- Previous message: Joe Wu [MSFT]: "RE: NT to W2k3 fears and questions"
- Next in thread: Lance: "RE: NT4 server and W2K3"
- Reply: Lance: "RE: NT4 server and W2K3"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
