Re: Migrating NT4 to Windows 2003
- From: Luiz <Luiz@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 6 Sep 2006 06:34:02 -0700
Thank you again, Jorge.
Best Regards.
Luiz
"Jorge Silva" wrote:
Read:.
Migrating Policy-Enabled Clients from Windows NT 4.0 to Windows 2000 or
Windows Server 2003
http://technet2.microsoft.com/WindowsServer/en/library/e773b47b-df32-44ba-9673-e484684fb68d1033.mspx?mfr=true
--
I hope that the information above helps you
Good Luck
Jorge Silva
MCSA
Systems Administrator
"Luiz" <Luiz@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:56470CFB-E472-4658-BAEA-A7E7F3BC9093@xxxxxxxxxxxxxxxx
Hi Jorge,
one another question: in NT 4 environment (PDC with 2000 and XP) I can not
apply policy, is that correct?
Thank you again.
Regads.
Luiz
"Jorge Silva" wrote:
Glad to help.
--
I hope that the information above helps you
Good Luck
Jorge Silva
MCSA
Systems Administrator
"Luiz" <Luiz@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:55A003DF-3180-406F-8D66-4432A9648E29@xxxxxxxxxxxxxxxx
Hi Jorge,
thank you.
Best Regards.
Luiz
"Jorge Silva" wrote:
Hi
Informative Sites:
Migrating from Windows NT Server 4.0 to Windows Server 2003
http://www.microsoft.com/downloads/details.aspx?FamilyID=e92cf6a0-76f0-4e25-8de0-19544062a6e6&DisplayLang=en
Upgrading from Windows NT Server 4.0
http://www.microsoft.com/windowsserver2003/upgrading/nt4/default.mspx
How to Upgrade from Windows NT Server 4.0
http://www.microsoft.com/windowsserver2003/upgrading/nt4/howto/default.mspx
Best Practice Active Directory Design for Managing Windows Networks
http://www.microsoft.com/technet/prodtechnol/windows2000serv/technologies/activedirectory/plan/bpaddsgn.mspx#E1AAG
Microsoft File Server Migration Toolkit
http://www.microsoft.com/windowsserver2003/upgrading/nt4/tooldocs/msfsc.mspx
Considerations:
- Install the latest service pack.
http://www.microsoft.com/downloads
- Check Hardware.
Windows Catalog and HCL
http://www.microsoft.com/whdc/hcl/default.mspx
Active Directory Sizer
http://www.microsoft.com/windows2000/techinfo/reskit/tools/new/adsizer-o.asp
- Windows Application Compatibility
http://www.microsoft.com/technet/prodtechnol/windows/appcompatibility/default.mspx
- Document everything network related (users, groups, permissions,
printers,etc).
Upgrade or migrate?
Reasons to Upgrade
Especially for small organizations, the ease of an upgrade rather than
a
new
installation can make sense. Generally, with an upgrade, configuration
is
simpler, and your existing users, settings, groups, rights, and
permissions
are retained. Also, with an upgrade, you do not need to re-install
files
and
applications.
Reasons to Migrate
There are good reasons to migrate rather than upgrade-especially when
dealing with large organizations. If you want to practice careful
configuration management, for example, for a server where high
availability
is important, you might want to perform a new installation on that
server
instead of an upgrade. This is especially true for servers on which
the
operating system has been upgraded several times in the past.
Upgrading Windows NT 4.0 Domains to Windows Server 2003 Active
Directory
http://technet2.microsoft.com/WindowsServer/en/Library/b170bdc5-ba55-4184-8a8f-acb7705ff04a1033.mspx
Migrating Windows NT Server 4.0 Domains to Windows Server 2003 Active
Directory
http://www.microsoft.com/windowsserver2003/evaluation/whyupgrade/nt4/nt4domtoad.mspx
Active Directory Migration Tool v.2.0
http://www.microsoft.com/downloads/details.aspx?FamilyID=788975b1-5849-4707-9817-8c9773c25c6c&DisplayLang=en
Planning:
- Failover.
* Backup the Servers.
* Take at least one BDC Offline (In case of UPGRADE FAILURE you always
can
promote it to a PDC). The only drawback to this method is that all
changes
that were made while the safe BDC was offline are lost. To minimize
this
loss, you could periodically turn the safe BDC on and off (when the
domain
is in a stable state) during the upgrade process, to update its safe
copy
of
the directory.
To convert the BDC to a PDC: Start -> Programs -> Administrative
Tools ->
Server Manager -> Select the BDC, then go to the Computer Menu ->
choose
Promote to primary Domain Controller.
* Make sure that the Hardware and apps meets the requirements.
* Make sure that all Apps installed are compatible with W2K3 and don't
cause
problems with the upgrade process or pos upgrade process.
* Run from command prompt:
Cdsource\I386\winnt32.exe /checkupgradeonly
- Before Upgrade:
* You can install a new computer (more powerful) make it a BDC,
SYNCRONIZE
and promote it to PDC and them perform the upgrade on the new PDC.
* Windows 2000/XP always prefer Kerberos authentication, so if the
newly
upgraded NT4 to Windows 2003 goes down (Offline), the client machines
won't
be able to authenticate in the domain.
* If this is the case, before upgrade the NT.4 PDC, make the necessary
changes on the registry (NT4Emulator). If the NT4Emulator is
configured
on
the newly PDC, and you want o upgrade the Existent BDCs, you also need
to
create a registry entry on the BDCs (NeutralizeNT4Emulator) before the
upgrade.
Check:
Windows 2000-based clients connect only to the domain controller that
was
upgraded from Windows NT 4.0 in a mixed-mode domain
http://support.microsoft.com/?kbid=284937
How to prevent overloading on the first domain controller during
domain
upgrade
http://support.microsoft.com/kb/298713/
Once that all domain controllers are upgraded, remove the registry
settings
created in the previous steps.
Note: This sometimes may not need: E.g - if all existent BDCs will be
sun
upgraded to Windows 2003.
- Dns Planning:
Prior to beginning the upgrade from Windows NT Server 4.0 to the
Windows
Server 2003 Active Directory service, ensure that you have designed a
DNS
and Active Directory namespace and have either configured DNS servers
or
are
planning to have the Active Directory Installation Wizard
automatically
install the DNS service on the domain controller.
Active Directory is integrated with DNS in the following ways:
Active Directory and DNS have the same hierarchical structure.
Although
separate and implemented differently for different purposes, an
organization's namespace for DNS and Active Directory have an
identical
structure. For example, microsoft.com is both a DNS domain and an
Active
Directory domain.
DNS zones can be stored in Active Directory. If you are using the
Windows
Server DNS service, primary zone files can be stored in Active
Directory
for
replication to other Active Directory domain controllers.
Active Directory uses DNS as a locator service, resolving Active
Directory
domain, site, and service names to an IP address. To log on to an
Active
Directory domain, an Active Directory client queries its configured
DNS
server for the IP address of the Lightweight Directory Access Protocol
(LDAP) service running on a domain controller for a specified domain.
While Active Directory is integrated with DNS and they share the same
namespace structure, it is important to distinguish the basic
difference
between them:
DNS is a name resolution service. DNS clients send DNS name queries to
their
configured DNS server. The DNS server receives the name query and
either
resolves the name query through locally stored files or consults
another
DNS
server for resolution. DNS does not require Active Directory to
function.
Active Directory is a directory service. Active Directory provides an
information repository and services to make information available to
users
and applications. Active Directory clients send queries to Active
Directory
servers using LDAP. In order to locate an Active Directory server, an
Active
Directory client queries DNS. Active Directory requires DNS to
function.
If use BIND DNS servers Make sure that you have BIND 8.1.2
- Supports: Srv records, Dynamic Updates, Doesn't Support
Secure
Dynamic Updates (this is one disadvantage over the MS Dns server
Servers,
and represents security issues).
- Create Primary Zone
If Use 2003 DNS
* Create Primary Zone
- References:
- Re: Migrating NT4 to Windows 2003
- From: Jorge Silva
- Re: Migrating NT4 to Windows 2003
- From: Luiz
- Re: Migrating NT4 to Windows 2003
- From: Jorge Silva
- Re: Migrating NT4 to Windows 2003
- From: Luiz
- Re: Migrating NT4 to Windows 2003
- From: Jorge Silva
- Re: Migrating NT4 to Windows 2003
- Prev by Date: deploy sofware using GP
- Next by Date: Re: deploy sofware using GP
- Previous by thread: Re: Migrating NT4 to Windows 2003
- Next by thread: Re: Password must meet complexity requirements
- Index(es):
Relevant Pages
|
