Networking Forums

Networking Forums > Computer Networking > Windows Networking > migration of windows network

Reply
Thread Tools Display Modes

migration of windows network

 
 
xiaomei
Guest
Posts: n/a

 
      08-30-2005, 09:08 AM
Hi, currently we only have a NT4.0 server with SP6 to serve as DC and mail
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
 
Reply With Quote
 
 
 
 
Danny Sanders
Guest
Posts: n/a

 
      08-30-2005, 05:08 PM
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" <(E-Mail Removed)> wrote in message
news:7E754FB0-BE3E-463C-ABE4-(E-Mail Removed)...
> Hi, currently we only have a NT4.0 server with SP6 to serve as DC and
> mail
> 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



 
Reply With Quote
 
xiaomei
Guest
Posts: n/a

 
      08-31-2005, 06:49 AM
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" <(E-Mail Removed)> wrote in message
> news:7E754FB0-BE3E-463C-ABE4-(E-Mail Removed)...
> > Hi, currently we only have a NT4.0 server with SP6 to serve as DC and
> > mail
> > 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

>
>
>

 
Reply With Quote
 
Danny Sanders
Guest
Posts: n/a

 
      08-31-2005, 05:23 PM
> 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" <(E-Mail Removed)> wrote in message
news:C0024B02-017E-48A3-905C-(E-Mail Removed)...
> 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" <(E-Mail Removed)> wrote in message
>> news:7E754FB0-BE3E-463C-ABE4-(E-Mail Removed)...
>> > Hi, currently we only have a NT4.0 server with SP6 to serve as DC and
>> > mail
>> > 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

>>
>>
>>



 
Reply With Quote
 
xiaomei
Guest
Posts: n/a

 
      09-01-2005, 11:01 AM
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" <(E-Mail Removed)> wrote in message
> news:C0024B02-017E-48A3-905C-(E-Mail Removed)...
> > 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" <(E-Mail Removed)> wrote in message
> >> news:7E754FB0-BE3E-463C-ABE4-(E-Mail Removed)...
> >> > Hi, currently we only have a NT4.0 server with SP6 to serve as DC and
> >> > mail
> >> > 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
> >>
> >>
> >>

>
>
>

 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Req: Windows System Administrator / Domain Migration Specialist Mike Linux Networking 0 01-04-2008 02:47 PM
DHCP Migration from windows server 2000 to windows server 2003 Amr Salah Windows Networking 3 02-04-2007 12:01 PM
Do i need to send gratuitous ARP request after restarting network service after online migration. will_u_tellmemore Linux Networking 3 12-21-2006 10:32 PM
Windows Migration George Schneider Windows Networking 3 05-01-2006 10:59 AM
Windows 2000 Server ->Windows 2003 migration ping Windows Networking 3 09-10-2005 02:01 PM



1 2 3 4 5 6 7 8 9 10 11