How to move the main server (win2003) on another computer?

  • Thread starter Thread starter p. Th.
  • Start date Start date
P

p. Th.

Hi,

We have a computer with Windows 2003 as PDC and we want to move this
main server on another computer with a completely different hardware
components. Can someone explain us step by step how to do this? We want
also to "move" the name of the old server and its IP address on the new
machine.

TIA,

p. Th.
 
No, you don't want to do this. REALLY you don't. Not unless you also want
to run a good risk of completely screwing the domain up, that is; certainly
you'll have problem with Active Directory and server replication after
you're done with it.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm
 
Richard said:
No, you don't want to do this. REALLY you don't. Not unless you also want
to run a good risk of completely screwing the domain up, that is; certainly
you'll have problem with Active Directory and server replication after
you're done with it.
Click to expand...

So, IOW, we'll be stuck with the old hardware?
Because all our applications, shortcuts, settings a.s.o. are pointing on
the server "A". We only wanted to do, let's say, create a server "B",
see if everything is ok and after that get rid of "A" (format and put
winXP on it) and after that rename the "B" to "A" and change its IP.
Nothing of these things is possible?

TIA,

p. Th.
 
Is it possible? Yes.

Is it wise? No!

You would be better advised to bring up a new domain controller, migrate the
Global Catalog and all FSMO/DNS/DHCP/etc functions to it, then demote the
original domain controller to a member server. Once that's done you can
migrate applications off it and onto the new server, then re-configure the
applications to see the new server rather than the old one. Then the old
server may be retired and rust (or rest?) in peace.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm
 
Richard said:
Is it possible? Yes.

Aha!

Is it wise? No!
Click to expand...

Ouch...
Can we keep at least (without problems) the same name?
Or, better, the same IP?
(but if this thing will cause problems in your opinion, please tell us)

You would be better advised to bring up a new domain controller, migrate the
Global Catalog and all FSMO/DNS/DHCP/etc functions to it, then demote the
original domain controller to a member server. Once that's done you can
migrate applications off it and onto the new server, then re-configure the
applications to see the new server rather than the old one. Then the old
server may be retired and rust (or rest?) in peace.
Click to expand...

How _exactly_ can we do this? (ie. the steps). We use Win2003 Enterprise
no Excange, only Active Directory, Shares, Mail server, news server
(if isn't possible to migrate this isn't such a problem).

TIA,

f. Th.
 
As I mentioned earlier, trying to recycle either the name or the IP address
will likely lead to problems with the domain, DNS and Active Directory. If
you ever brought up a second domain controller for redundancy you'd surely
have massive problems at that point.

This is how I'd handle it:

1. Bring up the new domain controller as a member server in the current
domain
2. Install DNS on the new server and bring up an AD-integrated DNS zone
3. Transfer DHCP from the old server to the new one
(http://support.microsoft.com/default.aspx?scid=kb;en-us;325473)
4. Ensure that all clients are using the new DHCP before proceeding
5. Use DCPROMO to promote the new server to a domain controller
6. Transfer a copy of the Global Catalog to the new server
(http://support.microsoft.com/kb/313994/)
7. Transfer all FSMO roles from the old server to the new one
(http://support.microsoft.com/default.aspx?scid=kb;en-us;324801)
8. Use DCPROMO to demote the old domain controller to a member server
9. Plan for and implement share and application migration

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm
 
You could use a temporary DC first,...remove the original,...then build up
the new one and reuse the Name and IP# since the old original no longer
exists.

You would simply use the steps you gave two times:

First from original DC to Temp DC
Then from Temp DC to New DC

That is how I did it with our DC's here. I used a similar process to
replace Exchange with a newer version with a clean install,..yet in the end
it is on the same hardware, same IP#, and same name. With Exchange it is
called the "swing server" method. The temporary server is the "swing
server".


--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
http://www.microsoft.com/isaserver/techinfo/Guidance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
-----------------------------------------------------



Richard G. Harper said:
As I mentioned earlier, trying to recycle either the name or the IP address
will likely lead to problems with the domain, DNS and Active Directory. If
you ever brought up a second domain controller for redundancy you'd surely
have massive problems at that point.

This is how I'd handle it:

1. Bring up the new domain controller as a member server in the current
domain
2. Install DNS on the new server and bring up an AD-integrated DNS zone
3. Transfer DHCP from the old server to the new one
(http://support.microsoft.com/default.aspx?scid=kb;en-us;325473)
4. Ensure that all clients are using the new DHCP before proceeding
5. Use DCPROMO to promote the new server to a domain controller
6. Transfer a copy of the Global Catalog to the new server
(http://support.microsoft.com/kb/313994/)
7. Transfer all FSMO roles from the old server to the new one
(http://support.microsoft.com/default.aspx?scid=kb;en-us;324801)
8. Use DCPROMO to demote the old domain controller to a member server
9. Plan for and implement share and application migration

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


p. Th. said:
Ouch...
Can we keep at least (without problems) the same name?
Or, better, the same IP?
(but if this thing will cause problems in your opinion, please tell us)



How _exactly_ can we do this? (ie. the steps). We use Win2003 Enterprise
no Excange, only Active Directory, Shares, Mail server, news server (if
isn't possible to migrate this isn't such a problem).

TIA,

f. Th.
Click to expand...
Click to expand...
 
First of all thank you for your support. Also, I find the Phillip's
ideea very attractive. Please see bellow...
As I mentioned earlier, trying to recycle either the name or the IP address
will likely lead to problems with the domain, DNS and Active Directory. If
you ever brought up a second domain controller for redundancy you'd surely
have massive problems at that point.

This is how I'd handle it:

1. Bring up the new domain controller as a member server in the current
domain
2. Install DNS on the new server and bring up an AD-integrated DNS zone
How?

3. Transfer DHCP from the old server to the new one
(http://support.microsoft.com/default.aspx?scid=kb;en-us;325473)
4. Ensure that all clients are using the new DHCP before proceeding
Click to expand...

IOW, go on all workstations (WinXP) and manually change on CPanel/LAN
Connection | Properties | TCP/IP the preffered DNS server? (we don't
have DHCP enabled its a static IP network).

I think to use as swing server our backup DNS server which has already
its IP address in the Alternate DNS server so we can do this without
changing the settings on all the workstations minimizing in this way the
downtime. What do you think?

Or perhaps is better to use as a swing server a clean install of Win2003?
5. Use DCPROMO to promote the new server to a domain controller
6. Transfer a copy of the Global Catalog to the new server
(http://support.microsoft.com/kb/313994/)
7. Transfer all FSMO roles from the old server to the new one
(http://support.microsoft.com/default.aspx?scid=kb;en-us;324801)
8. Use DCPROMO to demote the old domain controller to a member server
9. Plan for and implement share and application migration
Click to expand...

Tanks anyway for your support,

f. Th.
 
p. Th. said:
I think to use as swing server our backup DNS server which has already
its IP address in the Alternate DNS server so we can do this without
changing the settings on all the workstations minimizing in this way the
downtime. What do you think?
Click to expand...

Sounds fine to me. Demote it when you are done to force the FSMO Role to
transfer to the new permanent DC. But the Global Catalog setting is a manual
one you have to do yourself.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
http://www.microsoft.com/isaserver/techinfo/Guidance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
-----------------------------------------------------
 
Ouch...
Can we keep at least (without problems) the same name?
Or, better, the same IP?
(but if this thing will cause problems in your opinion, please tell us)
Click to expand...

Heh heh easy way to do this would be to take the hard drive from the old
machine and move it to another. Or better still, use a program like
Norton Ghost to make a ghost image of the current system and the reimage
the new server with the Ghost CD or DVD set.
 
Back
Top