Re: migration of windows network
- From: "xiaomei" <xiaomei@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 1 Sep 2005 04:01:03 -0700
Hi, Danny,
Thanks for good sugguestion. However I already implement a new domain on the
2003 server, so want the user to logon to the new domain.
In this case, I need build the trust and site relation shipment between the
NT4.0 DC and my new 2003 dc, right?
Since now they are in different domain, I am worry the two server can see
each other, and the user can continue use their email on the NT4.0 server.
Very appreciated your detailed explaination!
Rgds and have a nice day
Shermaine
"Danny Sanders" wrote:
> > 1. Build the 2003 server as DC and DNS server, and create the existing
> > username and password.
>
> When installing AD you will be asked by setup if this is the first DC in the
> domain if you say yes you will be creating a NEW DOMAIN. If you say no you
> will be required to point this DC to the first AD DC in the domain. Since
> you don't have an AD DC in your NT 4.0 domain this will fail.
>
> An NT 4.0 domain can essentially be boiled down to the SAM. The NT 4.0 PDC
> is the ONLY DC in the NT 4.0 domain that holds a writeable copy of the SAM.
> In order to carry that SAM into the AD domain you MUST upgrade your NT 4.0
> PDC first. Upgrading any other DC on the domain or creating a new domain
> from scratch with the same domain name will not work because the SAM is
> different.
> After step 1 you will have 2 domains. The NT 4.0 domain and the AD domain,
> probably these two domains will now have the same domain name. You will have
> backed your self into a corner that will take a format and reinstall to
> recover from.
>
>
> Consider installing NT 4.0 on the "new server" as a BDC while connected to
> your existing NT 4.0 domain. Promote to PDC then upgrade this NEW server to
> Win 2k3 and AD. You will have carried the NT 4.0 SAM into the AD domain,
> your clients will not see the AD domain as a different domain and you will
> not have to re set up their profiles. The existing NT 4.0 PDC will be
> demoted to a NT 4.0 BDC. You will not have to jump through all kinds of
> hoops to get Exchange into the AD domain. Least impact on your clients also.
>
>
> hth
> DDS W 2k MVP MCSE
>
> "xiaomei" <xiaomei@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:C0024B02-017E-48A3-905C-65F3535D3545@xxxxxxxxxxxxxxxx
> > Hi, Danny,
> > Thanks for reply.
> > I mean the NT4.0 server will only work as Mail server, no long take care
> > of
> > user logon, although I don't proceed a demote on the server. what I
> > planned
> > are:
> > 1. Build the 2003 server as DC and DNS server, and create the existing
> > username and password.
> > 2. Change the LAN seting for all user to refer the DNS to point to new
> > 2003
> > server, so when user logon, the DNS server will tell the user to logon
> > using
> > 2003 server instead of NT4.0.
> > 3. Install DSClient.exe for Win98 user to make them can logon to 2003
> > domain.
> >
> > Maybe my plan is a little bit stupid, but I know I don't have much time on
> > this since the customer is so demanding and I just start touching on
> > windows,
> > now there is only have 1 day left.
> >
> > Just want know whether this planning is workable.
> >
> > Thanks and regards
> > Shermaine
> >
> > "Danny Sanders" wrote:
> >
> >> There is no way that I know of to have a NT 4.0 PDC and a Win 2k3 DC in
> >> the
> >> same domain.
> >>
> >> Either upgrade your NT 4.0 domain by upgrading the existing PDC first or
> >> set
> >> up the Win 2k3 domain side by side on the same wire and use ADMT to
> >> migrate
> >> users from the NT domain to the AD domain.
> >>
> >> hth
> >> DDS W 2k MVP MCSE
> >>
> >> "xiaomei" <xiaomei@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> >> news:7E754FB0-BE3E-463C-ABE4-A8F8ECB93BCE@xxxxxxxxxxxxxxxx
> >> > Hi, currently we only have a NT4.0 server with SP6 to serve as DC and
> >> > server for 25 user to logon domain, clients are using win98, xp or 2k.
> >> > Now
> >> > will implement a new 2003 server as DC to take care of user logon, and
> >> > keep
> >> > the existing NT4.0 serve as sole mail server for user, need do as less
> >> > change
> >> > as possible to make everything running correctly. so planned as below:
> >> >
> >> > 1. New 2003 serve will act as domain controller, and all users and the
> >> > existing NT4.0 mail server need logon to the 2003 server.
> >> > 2. Some user using win98 OS, need install DSclient utility to make them
> >> > can
> >> > logon 2003 server, right?
> >> > 3. Need I also implement WINS server on the 2003 server to serve win98
> >> > user
> >> > to logon and access the shared folder on 2003?
> >> > 4. The NT4.0 will serve only mail server, make user can receive and
> >> > send
> >> > email as before, what changes need be done on this server after new
> >> > 2003
> >> > take
> >> > over domain controller function. No need demote as memeber server, can
> >> > work
> >> > is ok.
> >> >
> >> > Any suggestion or advise will be greatly appreciated.
> >> >
> >> > Thanks and regards
> >> > Shermaine
> >>
> >>
> >>
>
>
>
.
- References:
- Re: migration of windows network
- From: Danny Sanders
- Re: migration of windows network
- Prev by Date: RE: Remote Desktop Administration
- Next by Date: Problem with User Level Access on W98 PC
- Previous by thread: Re: migration of windows network
- Next by thread: Unable to See Windows Servers
- Index(es):
Relevant Pages
|
