windows 2003 adv server

[antonykoraya]

We have a existint windows NT 4.0 server and we would
like to migrate to windows 2003 server and exchange 2003.
Our network setup is with one pdc act as file server and
exchange 5.5 running on the bdc.we have almost 500 users
in our organisation. we had brouht all new servers. My
question is which the best way to move to 2003 with least
configuration changes. Also we don't want to loose any
file permission,security setting and mails.

 

[SaltPeter]

We have a existint windows NT 4.0 server and we would
like to migrate to windows 2003 server and exchange 2003.
Our network setup is with one pdc act as file server and
exchange 5.5 running on the bdc.we have almost 500 users
in our organisation. we had brouht all new servers. My
question is which the best way to move to 2003 with least
configuration changes. Also we don't want to loose any
file permission,security setting and mails.

Since you are planning to migrate from a netbios domain to a hierarchical
DNS domain, i'ld strongly suggest installing an NT4 PDC on one of the new
servers while isolated from your private network. Then run an upgrade to
W2K3 on it. Naming your domain's fqdn will be your first task. Is domain.com
or domain.local appropriate for your network? How strong is your knowledge
of DNS? What knowledge have you accumulated about administering a W2K3
domain? Since a BDC doesn't exist in W2K3, what are the implications of
running a DC with Exchange?

Once you've settled with your domain architecture, start gathering info on
the Exchange migration. You can't upgrade from Exchange 5.5 to Exchange
2003. An Exchange 2003 server must be introduced to an Exchange 5.5 site
first. Then you can use W2K3 deployment tools to move resources from 5.5 to
E2003. Lastly, its not recommended to run E2003 on a DC because of resource
intensive apps and security. Perhaps a third server might be a better
solution. A rootDC(PDC emulator) + DC(for backup) + a member server running
E2003.

Upgrading from Exchange Server 5.5
http://www.microsoft.com/exchange/techinfo/interop/55.asp

Migrating from Exchange 5.5 to Exchange 2003: Scenarios and Solutions
(WebCast)
http://www.microsoft.com/usa/webcasts/ondemand/2340.asp

 

[antony]

Dear peter
Thanks for your reply.I did a pilot test like,installed
nt 4.0 bdc on a new server and join to the existing
PDC.Once synchronise user and computer acoounts,Isolate
the BDC and upgrade to PDC.Then Upgrade the PDC agin to
windows 2003 server DC. And change the DC name by using
Rendom tool(our exiting domain name is company_nt our
feuture Domain name must be ug.company.com.
Now I am trying to pilot migration of the exchange.I am
trying to impliment as like u said A root dc+dc+member
e2003

Please letme know any other precuation I have to take
before going for acctual migration


Thank you

Antony

 

[SaltPeter]

Dear peter
Thanks for your reply.I did a pilot test like,installed
nt 4.0 bdc on a new server and join to the existing
PDC.Once synchronise user and computer acoounts,Isolate
the BDC and upgrade to PDC.Then Upgrade the PDC agin to
windows 2003 server DC. And change the DC name by using
Rendom tool(our exiting domain name is company_nt our
feuture Domain name must be ug.company.com.
Now I am trying to pilot migration of the exchange.I am
trying to impliment as like u said A root dc+dc+member
e2003

Please letme know any other precuation I have to take
before going for acctual migration


Thank you

Your wellcome. You need to consider a few issues before proceding in this
manner. The first involves the domain name based on "ug.company.com"
strategy. This is why i suggested looking more closely into DNS.
http://www.microsoft.com/windows2000/techinfo/howitworks/communications/name
adrmgmt/w2kdns.asp

This dns name says: the internet root recognizes that the second-level
domain called "com" knows about a zone "company.com" which is authoritative
for a child domain called "ug.company.com". This may (or may not) have
implications as far as name resolution in a namespace if no parent domain
"company.com" exists.

The next problem lies with disecting a BDC from an NT4 domain and then
isolating and promoting it. In the NT4 or W2K world, names mean nothing. Its
the SIDs that matter. This is critical for nt-based clients which rely on
SIDs, not domain names to be authenticated. So if you attempt to join a
different domain that has the same SID as another, guess what?

The recommended approach is to disable a BDC (for a recovery plan) and then
to upgrade the PDC of your existing NT4 domain. Needless to say, a thorough
compatibility check (software and hardware) is part of the upgrade procedure
(run winnt32 /checkupgradeonly).