Rename Global Catalog Server?

[tjdd1]

Anyone know if the following is possible:

Using Windows 2000 Server Standard edition OS.

We have an office in Boston that is exceeding it's ISP's
MTU packet size. Therefore, Microsoft is recommending we
create an Active Directory (AD) Global Catalog server and
physically place it in our Boston office. This supposedly
will resolve exceeding the MTU packet size while
authenticating to our AD domain controller in St Louis.

However, there is a server already in Boston titled
Boston01 and we wish to use that name for our new AD
Global Catalog server we are creating for them so we do
not have to reconfigure all of their workstations.

Since we wish to create this new AD Global Catalog server
and bring it up for testing on the same network as the
existing server with the same name in Boston, we want to
temporarily name the new server something like
Bostontemp. After we are certain the new AD Global
Catalog server titled Bostontemp is working, we want to
down the old server and rename the new AD Global Catalog
server to Boston01.

Can an AD Global Catalog server be renamed after being
created? Or, will this not work for reasons we have not
though of?

 

[Tomasz Onyszko]

Anyone know if the following is possible:

Using Windows 2000 Server Standard edition OS.
(...)

Can an AD Global Catalog server be renamed after being
created? Or, will this not work for reasons we have not
though of?

Domain Controller in windows 2003 can be ranemd using Domain rename
tool. Here You will find short description of this process:
http://www.petri.co.il/windows_2003_domain_controller_rename.htm

More information You will find in the Domain rename tool documentation

 

[tjdd1]

Are you saying that I may mix Windows 2003 with my
existing Windows 2000 AD controllers? In other words, my
original (and only 2) Windows Active Directory domain
controllers are currently Windows 2000. I may now add a
Windows 2003 Active Directory Global Catalog server at an
offsite location and it will not matter to the two
original Active Directory domain controllers that a
Windows 2003 server has now joined the mix in an offsite
location in a Global Catalog roll?

Thank you for your reply.

 

[Tomasz Onyszko]

Are you saying that I may mix Windows 2003 with my
existing Windows 2000 AD controllers? In other words, my
original (and only 2) Windows Active Directory domain
controllers are currently Windows 2000. I may now add a
Windows 2003 Active Directory Global Catalog server at an
offsite location and it will not matter to the two
original Active Directory domain controllers that a
Windows 2003 server has now joined the mix in an offsite
location in a Global Catalog roll?

Thank you for your reply.

No, You can;t use rename tool in mixed environment - I missed that You
have WIndows 2000 in Your first post

In thath case the only way to rename the DC is to demote it, rename and
then promote again

 

[Enkidu]

Anyone know if the following is possible:

Using Windows 2000 Server Standard edition OS.

We have an office in Boston that is exceeding it's ISP's
MTU packet size. Therefore, Microsoft is recommending we
create an Active Directory (AD) Global Catalog server and
physically place it in our Boston office. This supposedly
will resolve exceeding the MTU packet size while
authenticating to our AD domain controller in St Louis.

However, there is a server already in Boston titled
Boston01 and we wish to use that name for our new AD
Global Catalog server we are creating for them so we do
not have to reconfigure all of their workstations.

Since we wish to create this new AD Global Catalog server
and bring it up for testing on the same network as the
existing server with the same name in Boston, we want to
temporarily name the new server something like
Bostontemp. After we are certain the new AD Global
Catalog server titled Bostontemp is working, we want to
down the old server and rename the new AD Global Catalog
server to Boston01.

Can an AD Global Catalog server be renamed after being
created? Or, will this not work for reasons we have not
though of?

If the server in Boston is a member server (ie no AD) then why not
rename IT first?

Cheers,

Cliff