Transfer to a new computer

  • Thread starter Thread starter Ian_Liu
  • Start date Start date
I

Ian_Liu

In my network, there have already been a computer as DC, I want to use
a new computer instead of the original computer now. And the original
computer will be shut down.

I’ve seen so many articals about how to do it, but there are some
problems to puzzle me still.

How could I do to accomplish to it?
 
Ian_Liu said:
In my network, there have already been a computer as DC, I want to use
a new computer instead of the original computer now. And the original
computer will be shut down.

I've seen so many articals about how to do it, but there are some
problems to puzzle me still.

How could I do to accomplish to it?

Install the new computer with Win2000 or Win2003 server.

DCPromo (you will have to follow some special and well-
documented steps if you used a Win2003 server) on the new
server to make it a DC.

Transfer all of the "single master roles" (aka: FSMO) to
the new server -- the easiest tool for this is NTDSUtil.exe,
using the ROLES sub-section.

Make sure the new DC is also a GC:
AD Sites and Services->properties for NTDS on the server
(it's a simple check box.)

Make sure you have a DNS server holding your zone (likely
you used the original DC as the DNS server).

Make sure all of the clients are set to use the NEW DNS server
(NIC->IP properties) -- and remember that even the DC(s)
and other servers are also DNS clients and need these changes.




--
Herb Martin

--
http://www.WindowsForumz.com/ This article was posted by author's request
Articles individually checked for conformance to usenet standards
Topic URL: http://www.WindowsForumz.com/Active-Directory-Transfer-computer-ftopict234234.html
Visit Topic URL to contact author (reg. req'd). Report abuse:
http://www.WindowsForumz.com/eform.php?p=706406
 
First of all the computer should have the windows server product
installed onto it (2000 or 2003)

Then you promote that server to become a domain controller by
START>RUN>DCPROMO

If this is the only domain controller that will be left then you must
have dns running on that server otherwise you will find that your
active directory setup will not work when you shut down the first
server. I can only assume that the current server that is a dc has dns
already running on it.
 
Herb are you sure that you have to transfer the roles manually? Surely
when you demote the second from last server all the roles will be
automatically transfered onto the last server?
Same with the GC side of things.

Agreed, make sure all the clients on your network (again assuming they
are windows2000/NT or above) are pointing to the new server.
Sry Herb just trying to keep it as simple as possible for him :)
 
Herb are you sure that you have to transfer the roles manually? Surely
when you demote the second from last server all the roles will be
automatically transfered onto the last server?
Same with the GC side of things.

No, I am not sure you have to transfer them manually - but
doing so ALWAYS works while depending on the system
to get it right is not 100% certain.
Agreed, make sure all the clients on your network (again assuming they
are windows2000/NT or above) are pointing to the new server.
Sry Herb just trying to keep it as simple as possible for him :)

That's fine. I was trying to make it as complete as possible
without going into the details of using the tools until he asks.

He can read both and ask questions if he doesn't understand.

I personally would (do) transfer the roles and insure the GC
is copied.
[/QUOTE]
 
If this is a upgrade from a 2000 AD to 2003 don't forget to run the ADPREP
for the forest and domain as well.

Todd Myrick

Herb Martin said:
No, I am not sure you have to transfer them manually - but
doing so ALWAYS works while depending on the system
to get it right is not 100% certain.


That's fine. I was trying to make it as complete as possible
without going into the details of using the tools until he asks.

He can read both and ask questions if he doesn't understand.

I personally would (do) transfer the roles and insure the GC
is copied.
[/QUOTE]
 
Are you saying that MS would not have tested this? How dare you! :-)

Yes you're right, if you wanna be sure then do it manually.
Incidentally how long would it take for the GC to copy over once you've
ticked that box? The standard 90min replication time or do you reckon
it'll happen asap?

Ian_Liu, got any more questions?
 
Are you saying that MS would not have tested this? How dare you! :-)

Actually not -- that wasn't my worry.

My worry is that if everything isn't configured correctly,
likely DNS, anything that would prevent authentication
or replication might just prevent them from even finding
each other to switch the roles.

By moving the roles first, you guarantee it gets done.
Yes you're right, if you wanna be sure then do it manually.
Incidentally how long would it take for the GC to copy over once you've
ticked that box? The standard 90min replication time or do you reckon
it'll happen asap?

Darn if I know -- same site it will start right now.

Different sites SHOULD follow the replication schedule.

It will take as long as it takes: giant forest might take a
long time depending on where the copy originates (WANS
and stuff.)

GCs are really a forest (wide) job.
 
Herb Martin said:
Install the new computer with Win2000 or Win2003 server.

DCPromo (you will have to follow some special and well-
documented steps if you used a Win2003 server) on the new
server to make it a DC.

Transfer all of the "single master roles" (aka: FSMO) to
the new server -- the easiest tool for this is NTDSUtil.exe,
using the ROLES sub-section.

Make sure the new DC is also a GC:
AD Sites and Services->properties for NTDS on the
server
(it's a simple check box.)

Make sure you have a DNS server holding your zone (likely
you used the original DC as the DNS server).

Make sure all of the clients are set to use the NEW DNS server
(NIC->IP properties) -- and remember that even the
DC(s)
and other servers are also DNS clients and need these
changes.




--
Herb Martin


abuse:
http://www.WindowsForumz.com/eform.php?p=706406

I followed what you descripted to set up my new DC but I met a problem
that is it display a failed message when i run netdiag/test:dns on the
new computer.

I don’t know whether it is a fatal problem to stop setting up the new
DC
---------------------------------------------------
The failed message:
DNS test . . . . . . . . . . . . . : Failed
[WARNING] Cannot find a primary authoritative DNS server for
the name
’bj-svr.miracle.’. [RCODE_SERVER_FAILURE]
The name ’bj-svr.miracle.’ may not be registered in DNS.
[WARNING] The DNS entries for this DC are not registered correctly
on DNS se
rver ’192.168.2.2’. Please wait for 30 minutes for DNS server
replication.
[FATAL] No DNS servers have the DNS records for this DC
registered.
 
Ian_Liu said:
I followed what you descripted to set up my new DC but I met a
problem that is it display a failed message when i run
netdiag/test:dns on the new computer.

I don't know whether it is a fatal problem to stop setting up
the new DC
---------------------------------------------------
The failed message:
DNS test . . . . . . . . . . . . . : Failed
[WARNING] Cannot find a primary authoritative DNS
server for the name
'bj-svr.miracle.'. [RCODE_SERVER_FAILURE]
The name 'bj-svr.miracle.' may not be registered
in DNS.
[WARNING] The DNS entries for this DC are not registered
correctly on DNS se
rver '192.168.2.2'. Please wait for 30 minutes for DNS server
replication.
[FATAL] No DNS servers have the DNS records for this DC
registered.

If i set up the new DC sucessful, I want to know the DNS information
could be transferred to the new DC automately or need i transfer them
manually.

Thx a lot
 
I don't know whether it is a fatal problem to stop setting up the new
DC
---------------------------------------------------
The failed message:
DNS test . . . . . . . . . . . . . : Failed
[WARNING] Cannot find a primary authoritative DNS server for
the name
'bj-svr.miracle.'. [RCODE_SERVER_FAILURE]
The name 'bj-svr.miracle.' may not be registered in DNS.

I would prefer the test DCDiag, but it looks like you have
a problem with you domain name:

It seems to have only "one-label", e.g., DOMAIN rather than Domain.somthing

That's bad but not fatal (usually).

There are KB article for dealing with the problem.
http://support.microsoft.com/?kbid=826743

I actually consider this a bug -- Microsoft doesn't recommend
single label domain names but DCPromo will happily let you
create a domain this way with not warnings.

It ought to just STOP you from doing this, unless you press about
10 "Ok, I accept the consequences buttons"


--
Herb Martin


Ian_Liu said:
Herb Martin said:
Install the new computer with Win2000 or Win2003 server.

DCPromo (you will have to follow some special and well-
documented steps if you used a Win2003 server) on the new
server to make it a DC.

Transfer all of the "single master roles" (aka: FSMO) to
the new server -- the easiest tool for this is NTDSUtil.exe,
using the ROLES sub-section.

Make sure the new DC is also a GC:
AD Sites and Services->properties for NTDS on the
server
(it's a simple check box.)

Make sure you have a DNS server holding your zone (likely
you used the original DC as the DNS server).

Make sure all of the clients are set to use the NEW DNS server
(NIC->IP properties) -- and remember that even the
DC(s)
and other servers are also DNS clients and need these
changes.




--
Herb Martin


http://www.WindowsForumz.com/Active-Directory-Transfer-computer-ftopict234234.html
abuse:
http://www.WindowsForumz.com/eform.php?p=706406

I followed what you descripted to set up my new DC but I met a problem
that is it display a failed message when i run netdiag/test:dns on the
new computer.

I don't know whether it is a fatal problem to stop setting up the new
DC
---------------------------------------------------
The failed message:
DNS test . . . . . . . . . . . . . : Failed
[WARNING] Cannot find a primary authoritative DNS server for
the name
'bj-svr.miracle.'. [RCODE_SERVER_FAILURE]
The name 'bj-svr.miracle.' may not be registered in DNS.
[WARNING] The DNS entries for this DC are not registered correctly
on DNS se
rver '192.168.2.2'. Please wait for 30 minutes for DNS server
replication.
[FATAL] No DNS servers have the DNS records for this DC
registered.

--
http://www.WindowsForumz.com/ This article was posted by author's request
Articles individually checked for conformance to usenet standards
Topic URL: http://www.WindowsForumz.com/Active-Directory-Transfer-computer-ftopict234234.html
Visit Topic URL to contact author (reg. req'd). Report abuse:
http://www.WindowsForumz.com/eform.php?p=706528
 
Back
Top